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 15 min ago. Last stored result reached it in 363 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 223 ms | 0 |
| Nov 7 | 0 | 0.0 | 351 ms | 0 |
| Nov 7 | 0 | 0.0 | 196 ms | 0 |
| Nov 7 | 0 | 0.0 | 530 ms | 0 |
| Nov 7 | 0 | 0.0 | 366 ms | 0 |
| Nov 8 | 0 | 0.0 | 450 ms | 0 |
| Nov 8 | 0 | 0.0 | 454 ms | 0 |
| Nov 8 | 0 | 0.0 | 244 ms | 0 |
| Nov 8 | 0 | 0.0 | 285 ms | 0 |
| Nov 9 | 0 | 0.0 | 310 ms | 0 |
| Nov 9 | 0 | 0.0 | 400 ms | 0 |
| Nov 9 | 0 | 0.0 | 495 ms | 0 |
| Nov 9 | 0 | 0.0 | 525 ms | 0 |
| Nov 10 | 0 | 0.0 | 622 ms | 0 |
| Nov 10 | 0 | 0.0 | 449 ms | 0 |
| Nov 10 | 0 | 0.0 | 640 ms | 0 |
| Nov 10 | 0 | 0.0 | 428 ms | 0 |
| Nov 11 | 0 | 0.0 | 559 ms | 0 |
| Nov 11 | 0 | 0.0 | 514 ms | 0 |
| Nov 11 | 0 | 0.0 | 529 ms | 0 |
| Nov 11 | 0 | 0.0 | 748 ms | 0 |
| Nov 12 | 0 | 0.0 | 243 ms | 0 |
| Nov 12 | 0 | 0.0 | 371 ms | 0 |
| Nov 12 | 0 | 0.0 | 573 ms | 0 |
| Nov 12 | 0 | 0.0 | 514 ms | 0 |
| Nov 13 | 0 | 0.0 | 404 ms | 0 |
| Nov 13 | 0 | 0.0 | 480 ms | 0 |
| Nov 13 | 0 | 0.0 | 314 ms | 0 |
| Nov 13 | 0 | 0.0 | 518 ms | 0 |
| Nov 14 | 0 | 0.0 | 275 ms | 0 |
| Nov 14 | 0 | 0.0 | 436 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: 415 ms average, 176–716 ms range across 21 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.
415 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.