User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Social
postman.com · Social
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Tests postman.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.
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 271 ms · 8 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:00 | 0 | 0.0 | 369 ms | 0 |
| 03:15 | 0 | 0.0 | 512 ms | 0 |
| 03:30 | 0 | 0.0 | 693 ms | 0 |
| 03:45 | 0 | 0.0 | 510 ms | 0 |
| 04:00 | 0 | 0.0 | 454 ms | 0 |
| 04:15 | 0 | 0.0 | 386 ms | 0 |
| 04:30 | 0 | 0.0 | 320 ms | 0 |
| 04:45 | 0 | 0.0 | 1057 ms | 0 |
| 05:00 | 0 | 0.0 | 320 ms | 0 |
| 05:15 | 0 | 0.0 | 291 ms | 0 |
| 05:30 | 0 | 0.0 | 206 ms | 0 |
| 05:45 | 0 | 0.0 | 323 ms | 0 |
| 06:00 | 0 | 0.0 | 408 ms | 0 |
| 06:15 | 0 | 0.0 | 463 ms | 0 |
| 06:30 | 0 | 0.0 | 123 ms | 0 |
| 06:45 | 0 | 0.0 | 141 ms | 0 |
| 07:00 | 0 | 0.0 | 77 ms | 0 |
| 07:15 | 0 | 0.0 | 169 ms | 0 |
| 07:30 | 0 | 0.0 | 800 ms | 0 |
| 07:45 | 0 | 0.0 | 493 ms | 0 |
| 08:00 | 0 | 0.0 | 346 ms | 0 |
| 08:15 | 0 | 0.0 | 485 ms | 0 |
| 08:30 | 0 | 0.0 | 478 ms | 0 |
| 08:45 | 0 | 0.0 | 374 ms | 0 |
| 09:00 | 0 | 0.0 | 276 ms | 0 |
| 09:15 | 0 | 0.0 | 556 ms | 0 |
| 09:30 | 0 | 0.0 | 372 ms | 0 |
| 09:45 | 0 | 0.0 | 301 ms | 0 |
| 10:00 | 0 | 0.0 | 379 ms | 0 |
| 10:15 | 0 | 0.0 | 577 ms | 0 |
| 10:30 | 0 | 0.0 | 631 ms | 0 |
| 10:45 | 0 | 0.0 | 423 ms | 0 |
| 11:00 | 0 | 0.0 | 718 ms | 0 |
| 11:15 | 0 | 0.0 | 624 ms | 0 |
| 11:30 | 0 | 0.0 | 579 ms | 0 |
| 11:45 | 0 | 0.0 | 606 ms | 0 |
| 12:00 | 0 | 0.0 | 609 ms | 0 |
| 12:15 | 0 | 0.0 | 616 ms | 0 |
| 12:30 | 0 | 0.0 | 307 ms | 0 |
| 12:45 | 0 | 0.0 | 449 ms | 0 |
| 13:00 | 0 | 0.0 | 271 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 Postman 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 Postman goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Postman 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 Postman 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 Postman'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.