Is Postman Down?

No — Postman is up

Postman's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 500 ms

Right now

The verdict is the worse of these two. How we decide

Postman's status page

status.postman.com · read 3 minutes ago · checked every 3 minutes

Operational

“All Systems Operational”: no open incidents and no component reported in trouble.

31 locations All operational

Open their status page

FlareWarden checks

postman.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 500 ms
Checked: 52 minutes ago

By region

Amsterdam reachable, 459 ms
Dallas reachable, 283 ms
Newark reachable, 227 ms
Paris reachable, 390 ms
San Jose reachable, 526 ms
Stockholm reachable, 352 ms
Sydney reachable, 1431 ms
Toronto reachable, 338 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Amsterdam	50 ms	4 ms	17 ms	445 ms
Dallas	111 ms	2 ms	12 ms	267 ms
Newark	99 ms	2 ms	13 ms	219 ms
Paris	31 ms	2 ms	9 ms	379 ms
San Jose	109 ms	3 ms	14 ms	466 ms
Stockholm	92 ms	2 ms	9 ms	340 ms
Sydney	237 ms	1 ms	8 ms	1215 ms
Toronto	173 ms	1 ms	10 ms	324 ms

We check that postman.com loads, not every feature behind it. Test it yourself

History

Incidents Postman reported

Since Oct 22, 15 days · from status.postman.com

Incidents: 0
Major or critical: 0
Median to resolve: —

No incidents reported in this window.

Postman website availability

Measured by FlareWarden · postman.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 628ms

Last 30 days

91-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of postman.com from multiple regions every 6 hours. Postman's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 90 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 17 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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
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. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Postman itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Postman goes down

We check Postman every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required