User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Travel
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 5 min ago. Last stored result reached it in 721 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 01 | 0 | 0.0 | 657 ms | 0 |
| Tue 03 | 0 | 0.0 | 696 ms | 0 |
| Tue 05 | 0 | 0.0 | 655 ms | 0 |
| Tue 07 | 0 | 0.0 | 658 ms | 0 |
| Tue 09 | 0 | 0.0 | 710 ms | 0 |
| Tue 11 | 0 | 0.0 | 588 ms | 0 |
| Tue 14 | 0 | 0.0 | 694 ms | 0 |
| Tue 16 | 0 | 0.0 | 560 ms | 0 |
| Tue 18 | 0 | 0.0 | 693 ms | 0 |
| Tue 20 | 0 | 0.0 | 694 ms | 0 |
| Tue 23 | 0 | 0.0 | 688 ms | 0 |
| Wed 01 | 0 | 0.0 | 710 ms | 0 |
| Wed 03 | 0 | 0.0 | 629 ms | 0 |
| Wed 05 | 0 | 0.0 | 656 ms | 0 |
| Wed 08 | 0 | 0.0 | 497 ms | 0 |
| Wed 10 | 0 | 0.0 | 739 ms | 0 |
| Wed 12 | 0 | 0.0 | 568 ms | 0 |
| Wed 14 | 0 | 0.0 | 670 ms | 0 |
| Wed 16 | 0 | 0.0 | 691 ms | 0 |
| Wed 18 | 0 | 0.0 | 706 ms | 0 |
| Wed 21 | 0 | 0.0 | 699 ms | 0 |
| Wed 23 | 0 | 0.0 | 694 ms | 0 |
| Thu 01 | 0 | 0.0 | 588 ms | 0 |
| Thu 03 | 0 | 0.0 | 483 ms | 0 |
| Thu 05 | 0 | 0.0 | 688 ms | 0 |
| Thu 07 | 0 | 0.0 | 537 ms | 0 |
| Thu 09 | 0 | 0.0 | 503 ms | 0 |
| Thu 11 | 0 | 0.0 | 677 ms | 0 |
| Thu 13 | 0 | 0.0 | 578 ms | 0 |
| Thu 16 | 0 | 0.0 | 687 ms | 0 |
| Thu 18 | 0 | 0.0 | 734 ms | 0 |
| Thu 20 | 0 | 0.0 | 691 ms | 0 |
| Thu 22 | 0 | 0.0 | 653 ms | 0 |
| Fri 00 | 0 | 0.0 | 646 ms | 0 |
| Fri 02 | 0 | 0.0 | 728 ms | 0 |
| Fri 04 | 0 | 0.0 | 716 ms | 0 |
| Fri 06 | 0 | 0.0 | 543 ms | 0 |
| Fri 08 | 0 | 0.0 | 610 ms | 0 |
| Fri 10 | 0 | 0.0 | 645 ms | 0 |
| Fri 12 | 0 | 0.0 | 192 ms | 0 |
| Fri 14 | 0 | 0.0 | 670 ms | 0 |
| Fri 16 | 0 | 0.0 | 640 ms | 0 |
| Fri 18 | 0 | 0.0 | 678 ms | 0 |
| Fri 19 | 0 | 0.0 | 669 ms | 0 |
| Fri 21 | 0 | 0.0 | 700 ms | 0 |
| Fri 23 | 0 | 0.0 | 591 ms | 0 |
| Sat 00 | 0 | 0.0 | 592 ms | 0 |
| Sat 03 | 0 | 0.0 | 721 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Shippingbo 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 Shippingbo goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Shippingbo alerts to Slack, Discord or a webhook — free.
We track Shippingbo (shippingbo.com) as part of the Travel group. +90 millions de commandes gérées. Centralisez vos commandes, vos stocks, automatisez vos expéditions. Un seul logiciel logistique e-commerce.
Shippingbo publishes an official status page at status.shippingbo.com; when we can read it, its incident level is folded into the status shown here.
Common problems for travel services: booking and check-in failures, flight-status pages not loading, and app errors.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 613 ms average, 192–721 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Shippingbo incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
613 ms on average over the last 24 hours (192–721 ms).
Yes, at https://status.shippingbo.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For travel services, watch for booking and check-in failures, flight-status pages not loading, and app errors. If many people report Shippingbo here at once, the problem is on Shippingbo'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 Shippingbo. 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.