Is Postman Down?

No — Postman is up

Reachable from all 8 checked regions

Average response time: 830ms

Last checked 2 hours ago · checks run every 6 hours

Official status page: https://status.postman.com

Postman uptime

100%

Last 7 days

99.89%

Last 30 days

99.94%

Last 90 days

520ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 55 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

27-day clean streak

Aug 22 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams

524ms

DNS 117ms TCP 2ms TLS 15ms TTFB 509ms

arn

668ms

DNS 127ms TCP 1ms TLS 10ms TTFB 653ms

bom

680ms

DNS 146ms TCP 3ms TLS 15ms TTFB 632ms

cdg

515ms

DNS 50ms TCP 1ms TLS 9ms TTFB 501ms

sin

1119ms

DNS 265ms TCP 1ms TLS 17ms TTFB 1099ms

sjc

609ms

DNS 77ms TCP 1ms TLS 10ms TTFB 597ms

syd

2082ms

DNS 260ms TCP 1ms TLS 15ms TTFB 1876ms

yyz

445ms

DNS 198ms TCP 1ms TLS 10ms TTFB 432ms

What Postman does

Postman is an API platform where developers build, test and document requests, share collections across a team and run scheduled monitors against live endpoints. Collections sync through Postman's cloud rather than living purely on disk, so an outage can block access to work that feels local.

What an outage looks like

The desktop and web clients fail to sign in, or open showing collections that will not sync. Shared collections appear stale, and edits made by colleagues do not arrive. Scheduled monitors stop running and report no results, which reads as healthy endpoints rather than as missing checks. Mock servers and published documentation return errors to their consumers.

What to do about it

Check status.postman.com, which reports the desktop and browser platforms, Login, Monitors, Mocks, the Postman API and published documentation separately, and splits them by US and Europe regions. Requests against your own APIs still work if you are already signed in, since those calls leave your machine directly. Treat a silent monitor as unverified rather than as a passing check.

Is it down for everyone, or just you?

If this page says Postman is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

Postman outage FAQ

Is Postman down or am I just signed out?

Login is a separate component, and a failure there logs people out or blocks sign-in while the rest of the platform is healthy. If the client opens but rejects your credentials, check that component specifically. Repeatedly re-entering credentials during a Login incident does nothing useful and occasionally trips rate limiting on top of it.

Can I still send requests while Postman is down?

Yes, if you are already signed in and the collection is loaded. Requests go from your machine to the API you are testing and do not route through Postman, so testing continues. What fails is syncing, sharing, and anything server-side such as monitors and mocks. Avoid signing out mid-incident, since signing back in may not work.

Do scheduled monitors run after the outage?

Missed runs are generally not replayed, so a gap in monitor history is a gap in coverage rather than a delayed result. This matters because a monitor that did not run looks the same as one that found nothing wrong. After an incident, treat the silent window as unmonitored and check the endpoints it covers directly.

Will I lose unsynced collection changes?

Changes made in the client while sync was failing are held locally and usually upload when the connection returns. The risk is editing the same collection from a second machine in the meantime, which produces a conflict someone has to resolve. Work from one client until sync recovers rather than switching devices during an incident.

Does a Postman outage break my published API documentation?

Published documentation and mock servers are served by Postman and are listed as their own components, so consumers of your public docs see errors during an incident. Your actual API is unaffected. If partners depend on those docs, saying so somewhere else during a long outage saves them debugging an integration that was never broken.

How we measure this

We request Postman's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Postman publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Postman goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required