User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
Is Shipup down?
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Some components degraded (no active incident posted)
Source: the vendor's status page · We are not affiliated with Shipup.
What to try while Shipup is having problems
Estimated fix: Not enough Shipup history yet; similar Cloud & developer outages lasted 2 h (median, typically 48 min–9.5 h; 82 outages).
- Hold off on deploys and config changes; check which regions or products are affected and retry with backoff.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → shipup.co—
Your browser → us—
Our checksReaching it
Official · ReportsMinor incident · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 9 min ago. Last stored result reached it in 213 ms.
Official status
Minor incident
Some components degraded (no active incident posted) Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 17 | 0 | 0.0 | 184 ms | 0 |
| Mon 19 | 0 | 0.0 | 189 ms | 0 |
| Mon 21 | 0 | 0.0 | 211 ms | 0 |
| Mon 23 | 0 | 0.0 | 228 ms | 0 |
| Tue 01 | 0 | 0.0 | 190 ms | 0 |
| Tue 04 | 0 | 0.0 | 180 ms | 0 |
| Tue 06 | 0 | 0.0 | 237 ms | 0 |
| Tue 08 | 0 | 0.0 | 206 ms | 0 |
| Tue 10 | 0 | 0.0 | 156 ms | 0 |
| Tue 12 | 0 | 0.0 | 156 ms | 0 |
| Tue 14 | 0 | 0.0 | 143 ms | 0 |
| Tue 17 | 0 | 0.0 | 207 ms | 0 |
| Tue 19 | 0 | 0.0 | 316 ms | 0 |
| Tue 21 | 0 | 0.0 | 209 ms | 0 |
| Tue 23 | 0 | 0.0 | 227 ms | 0 |
| Wed 02 | 0 | 0.0 | 261 ms | 0 |
| Wed 04 | 0 | 0.0 | 239 ms | 0 |
| Wed 06 | 0 | 0.0 | 190 ms | 0 |
| Wed 08 | 0 | 0.0 | 147 ms | 0 |
| Wed 11 | 0 | 0.0 | 201 ms | 0 |
| Wed 13 | 0 | 0.0 | 164 ms | 0 |
| Wed 15 | 0 | 0.0 | 187 ms | 0 |
| Wed 17 | 0 | 0.0 | 275 ms | 0 |
| Wed 19 | 0 | 0.0 | 169 ms | 0 |
| Wed 21 | 0 | 0.0 | 275 ms | 0 |
| Thu 00 | 0 | 0.0 | 252 ms | 0 |
| Thu 02 | 0 | 0.0 | 246 ms | 0 |
| Thu 04 | 0 | 0.0 | 271 ms | 0 |
| Thu 06 | 0 | 0.0 | 258 ms | 0 |
| Thu 08 | 0 | 0.0 | 168 ms | 0 |
| Thu 10 | 0 | 0.0 | 133 ms | 0 |
| Thu 12 | 0 | 0.0 | 141 ms | 0 |
| Thu 14 | 0 | 0.0 | 237 ms | 0 |
| Thu 16 | 0 | 0.0 | 203 ms | 0 |
| Thu 18 | 0 | 0.0 | 206 ms | 0 |
| Thu 20 | 0 | 0.0 | 230 ms | 0 |
| Thu 22 | 0 | 0.0 | 187 ms | 0 |
| Fri 00 | 0 | 0.0 | 208 ms | 0 |
| Fri 02 | 0 | 0.0 | 245 ms | 0 |
| Fri 04 | 0 | 0.0 | 232 ms | 0 |
| Fri 06 | 0 | 0.0 | 170 ms | 0 |
| Fri 08 | 0 | 0.0 | 163 ms | 0 |
| Fri 11 | 0 | 0.0 | 345 ms | 0 |
| Fri 13 | 0 | 0.0 | 276 ms | 0 |
| Fri 15 | 0 | 0.0 | 322 ms | 0 |
| Fri 17 | 0 | 0.0 | 228 ms | 0 |
| Fri 19 | 0 | 0.0 | 160 ms | 0 |
| Fri 20 | 0 | 0.0 | 195 ms | 0 |
Reliability
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.
Embed this status: free live Shipup badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
Having trouble with Shipup?
One report per service every 10 minutes from this network. No account.
Follow Shipup
Get an email when Shipup goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Shipup alerts to Slack, Discord or a webhook — free.
About Shipup
Shipup is listed in our Cloud & developer category and checked at shipup.co. Pilotez toutes les étapes post-achat au même endroit pour réduire vos coûts logistiques, améliorer la performance transporteurs et maîtriser l’expérience client.
Shipup publishes an official status page at status.shipup.co; 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 8 days of checks. We logged 1 public incident since monitoring began 8 days ago.
Response time over the last 24 hours: 229 ms average, 160–345 ms range across 16 successful checks.
Questions
Is Shipup down right now?
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Some components degraded (no active incident posted)
When was Shipup last down?
The most recent public incident we recorded started 2026-11-06 and lasted 3 days 15 h. 1 incident since monitoring began 8 days ago.
What is Shipup's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Shipup respond?
229 ms on average over the last 24 hours (160–345 ms).
Does Shipup have an official status page?
Yes, at https://status.shipup.co.
Shipup not working for me but the status is fine. What now?
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 Shipup here at once, the problem is on Shipup'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 Shipup. 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.