User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Money
easypost.com · Money
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what 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, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 67 ms · 2 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 04:30 | 0 | 0.0 | 63 ms | 0 |
| 04:45 | 0 | 0.0 | 87 ms | 0 |
| 05:00 | 0 | 0.0 | 119 ms | 0 |
| 05:15 | 0 | 0.0 | 289 ms | 0 |
| 05:30 | 0 | 0.0 | 374 ms | 0 |
| 05:45 | 0 | 0.0 | 81 ms | 0 |
| 06:00 | 0 | 0.0 | 371 ms | 0 |
| 06:15 | 0 | 0.0 | 172 ms | 0 |
| 06:30 | 0 | 0.0 | 77 ms | 0 |
| 06:45 | 0 | 0.0 | 369 ms | 0 |
| 07:00 | 0 | 0.0 | 169 ms | 0 |
| 07:15 | 0 | 0.0 | 201 ms | 0 |
| 07:30 | 0 | 0.0 | 51 ms | 0 |
| 07:45 | 0 | 0.0 | 176 ms | 0 |
| 08:00 | 0 | 0.0 | 256 ms | 0 |
| 08:15 | 0 | 0.0 | 122 ms | 0 |
| 08:30 | 0 | 0.0 | 298 ms | 0 |
| 08:45 | 0 | 0.0 | 148 ms | 0 |
| 09:00 | 0 | 0.0 | 61 ms | 0 |
| 09:15 | 0 | 0.0 | 128 ms | 0 |
| 09:30 | 0 | 0.0 | 65 ms | 0 |
| 09:45 | 0 | 0.0 | 355 ms | 0 |
| 10:00 | 0 | 0.0 | 189 ms | 0 |
| 10:15 | 0 | 0.0 | 85 ms | 0 |
| 10:30 | 0 | 0.0 | 343 ms | 0 |
| 10:45 | 0 | 0.0 | 190 ms | 0 |
| 11:00 | 0 | 0.0 | 182 ms | 0 |
| 11:15 | 0 | 0.0 | 121 ms | 0 |
| 11:30 | 0 | 0.0 | 59 ms | 0 |
| 11:45 | 0 | 0.0 | 350 ms | 0 |
| 12:00 | 0 | 0.0 | 198 ms | 0 |
| 12:15 | 0 | 0.0 | 251 ms | 0 |
| 12:30 | 0 | 0.0 | 267 ms | 0 |
| 12:45 | 0 | 0.0 | 120 ms | 0 |
| 13:00 | 0 | 0.0 | 74 ms | 0 |
| 13:15 | 0 | 0.0 | 100 ms | 0 |
| 13:30 | 0 | 0.0 | 205 ms | 0 |
| 13:45 | 0 | 0.0 | 97 ms | 0 |
| 14:00 | 0 | 0.0 | 196 ms | 0 |
| 14:15 | 0 | 0.0 | 298 ms | 0 |
| 14:30 | 0 | 0.0 | 204 ms | 0 |
| 14:45 | 0 | 0.0 | 294 ms | 0 |
| 15:00 | 0 | 0.0 | 114 ms | 0 |
| 15:15 | 0 | 0.0 | 292 ms | 0 |
| 15:30 | 0 | 0.0 | 227 ms | 0 |
| 15:45 | 0 | 0.0 | 155 ms | 0 |
| 16:00 | 0 | 0.0 | 265 ms | 0 |
| 16:15 | 0 | 0.0 | 67 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.
No outages on record for Easypost 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 Easypost goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Easypost alerts to Slack, Discord or a webhook — free.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
If Easypost is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Easypost's side.
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.