User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
tradeshift.com · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 59 min ago. Last stored result reached it in 461 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 04 | 0 | 0.0 | 183 ms | 0 |
| Tue 06 | 0 | 0.0 | 272 ms | 0 |
| Tue 08 | 0 | 0.0 | 597 ms | 0 |
| Tue 10 | 0 | 0.0 | 449 ms | 0 |
| Tue 13 | 0 | 0.0 | 640 ms | 0 |
| Tue 15 | 0 | 0.0 | 623 ms | 0 |
| Tue 17 | 0 | 0.0 | 701 ms | 0 |
| Tue 19 | 0 | 0.0 | 502 ms | 0 |
| Tue 22 | 0 | 0.0 | 391 ms | 0 |
| Wed 00 | 0 | 0.0 | 512 ms | 0 |
| Wed 02 | 0 | 0.0 | 440 ms | 0 |
| Wed 04 | 0 | 0.0 | 640 ms | 0 |
| Wed 07 | 0 | 0.0 | 385 ms | 0 |
| Wed 09 | 0 | 0.0 | 593 ms | 0 |
| Wed 11 | 0 | 0.0 | 514 ms | 0 |
| Wed 13 | 0 | 0.0 | 568 ms | 0 |
| Wed 15 | 0 | 0.0 | 320 ms | 0 |
| Wed 17 | 0 | 0.0 | 529 ms | 0 |
| Wed 20 | 0 | 0.0 | 769 ms | 0 |
| Wed 22 | 0 | 0.0 | 727 ms | 0 |
| Thu 00 | 0 | 0.0 | 243 ms | 0 |
| Thu 02 | 0 | 0.0 | 631 ms | 0 |
| Thu 04 | 0 | 0.0 | 155 ms | 0 |
| Thu 06 | 0 | 0.0 | 591 ms | 0 |
| Thu 08 | 0 | 0.0 | 371 ms | 0 |
| Thu 10 | 0 | 0.0 | 274 ms | 0 |
| Thu 13 | 0 | 0.0 | 204 ms | 0 |
| Thu 15 | 0 | 0.0 | 573 ms | 0 |
| Thu 17 | 0 | 0.0 | 724 ms | 0 |
| Thu 19 | 0 | 0.0 | 748 ms | 0 |
| Thu 21 | 0 | 0.0 | 514 ms | 0 |
| Thu 23 | 0 | 0.0 | 271 ms | 0 |
| Fri 02 | 0 | 0.0 | 258 ms | 0 |
| Fri 04 | 0 | 0.0 | 550 ms | 0 |
| Fri 06 | 0 | 0.0 | 556 ms | 0 |
| Fri 08 | 0 | 0.0 | 535 ms | 0 |
| Fri 10 | 0 | 0.0 | 408 ms | 0 |
| Fri 12 | 0 | 0.0 | 716 ms | 0 |
| Fri 14 | 0 | 0.0 | 314 ms | 0 |
| Fri 16 | 0 | 0.0 | 221 ms | 0 |
| Fri 18 | 0 | 0.0 | 516 ms | 0 |
| Fri 19 | 0 | 0.0 | 490 ms | 0 |
| Fri 21 | 0 | 0.0 | 382 ms | 0 |
| Fri 23 | 0 | 0.0 | 594 ms | 0 |
| Sat 00 | 0 | 0.0 | 588 ms | 0 |
| Sat 01 | 0 | 0.0 | 318 ms | 0 |
| Sat 02 | 0 | 0.0 | 176 ms | 0 |
| Sat 04 | 0 | 0.0 | 231 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Tradeshift yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Tradeshift goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Tradeshift alerts to Slack, Discord or a webhook — free.
Tradeshift, at tradeshift.com, is one of the Cloud & developer services we monitor. e-Invoicing software and accounts payables automation platform that ensures compliance in 69 countries, including in France and Belgium.
Tradeshift publishes an official status page at status.tradeshift.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 420 ms average, 176–716 ms range across 20 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Tradeshift incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
420 ms on average over the last 24 hours (176–716 ms).
Yes, at https://status.tradeshift.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Tradeshift here at once, the problem is on Tradeshift's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Tradeshift. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.