postman site is having issues
The incident is resolved and the site is operational
The latest update from Postman.
State
Resolved
Started
80 d ago
2026-08-13 21:04 UTC
Lasted
23 min
until 2026-08-13 21:27 UTC
Worst impact
Degraded
Timeline
4 updatesInvestigating
23 min 100%
Updates
Times in UTCAs posted by Postman
The incident is resolved and the site is operational
We are continuing to investigate this issue.
We are continuing to investigate this issue.
we are currently investigating the issue
Affected components
2Postman in the last 90 days
Full historyIncidents in 90 days
2
Days with an incident
2
Median duration
24 min
This incident
About the median
Other Postman incidents
All incidentsFollow Postman
Your coding agent knows when Postman is down, and tells you when a failure is theirs, not yours. You can also get Postman incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "postman" and tell me if Postman has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=postman/feed subscribe https://outages.cc/feed.xml?providers=postmanFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane