User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Shopping
usps.com · Shopping
Checks are succeeding and user reports are near the baseline.
Live diagnosis
Tests usps.com from your browser and compares it with our checks, the official status, and user reports.
Press Run testNothing leaves your browser except a request to the site and to us.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 54 ms · 1 min ago.
No status feed
USPS does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 11:30 | 0 | 0.0 | 40 ms | 0 |
| 11:45 | 0 | 0.0 | 122 ms | 0 |
| 12:00 | 0 | 0.0 | 61 ms | 0 |
| 12:15 | 0 | 0.0 | 79 ms | 0 |
| 12:30 | 0 | 0.0 | 63 ms | 0 |
| 12:45 | 0 | 0.0 | 132 ms | 0 |
| 13:00 | 0 | 0.0 | 65 ms | 0 |
| 13:15 | 0 | 0.0 | 75 ms | 0 |
| 13:30 | 0 | 0.0 | 90 ms | 0 |
| 13:45 | 0 | 0.0 | 49 ms | 0 |
| 14:00 | 0 | 0.0 | 71 ms | 0 |
| 14:15 | 0 | 0.0 | 74 ms | 0 |
| 14:30 | 0 | 0.0 | 233 ms | 0 |
| 14:45 | 0 | 0.0 | 58 ms | 0 |
| 15:00 | 0 | 0.0 | 77 ms | 0 |
| 15:15 | 0 | 0.0 | 72 ms | 0 |
| 15:30 | 0 | 0.0 | 63 ms | 0 |
| 15:45 | 0 | 0.0 | 98 ms | 0 |
| 16:00 | 0 | 0.0 | 296 ms | 0 |
| 16:15 | 0 | 0.0 | 110 ms | 0 |
| 16:30 | 0 | 0.0 | 139 ms | 0 |
| 16:45 | 0 | 0.0 | 253 ms | 0 |
| 17:00 | 0 | 0.0 | 107 ms | 0 |
| 17:15 | 0 | 0.0 | 74 ms | 0 |
| 17:30 | 0 | 0.0 | 185 ms | 0 |
| 17:45 | 0 | 0.0 | 162 ms | 0 |
| 18:00 | 0 | 0.0 | 113 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
Embed this status badge · JSON
No outages on record for USPS 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 USPS goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Checks are succeeding and user reports are near the baseline.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.