outages.live
Live

Postman

Postman is operational

Checked 1 min ago Operational

History

90 days agoToday

Incidents in 90 days

2

Days with an incident

2

Median duration

24 min

Longest incident

25 min

Components

31

US

Postman Platform on Desktop Operational
90 days agoNo incidentsToday
Postman Platform on Browser Operational
90 days agoNo incidentsToday
Postman Login Operational
90 days agoNo incidentsToday
Postman Monitors Operational
90 days agoNo incidentsToday
Postman Mocks Operational
90 days agoNo incidentsToday
Postman API Operational
90 days agoNo incidentsToday
Postman API Network (API Explore) Operational
90 days agoNo incidentsToday
Run Button Operational
90 days agoNo incidentsToday
Postman Search Operational
90 days agoNo incidentsToday
Public Collection Documentation Operational
90 days agoNo incidentsToday
Newman Operational
90 days agoNo incidentsToday
Postman Learning Center and Documentation Operational
90 days agoNo incidentsToday
Postman Support and Community Forum Operational
90 days agoNo incidentsToday
Postman Integrations Operational
90 days agoNo incidentsToday
Postman Interceptor Operational
90 days agoNo incidentsToday
Marketing Website Operational
90 days ago1 day with an incidentToday
Postbot Operational
90 days agoNo incidentsToday
Postman VS Code extension Operational
90 days agoNo incidentsToday
API Builder Operational
90 days ago1 day with an incidentToday
API Specifications Operational
90 days agoNo incidentsToday
Collection Runner Operational
90 days agoNo incidentsToday
Postman CLI Operational
90 days agoNo incidentsToday
Agent Mode Operational
90 days agoNo incidentsToday
Performance Testing Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Sep 10, 2026

Duration25 min18:01 to 18:26Api Builder flows are affected for US customersPartial outage

All scenarios have recovered and the issue is mitigated.

Aug 13, 2026

Duration23 min21:04 to 21:27postman site is having issuesDegraded

The incident is resolved and the site is operational

Follow 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.

Prompt
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.

RSS
https://outages.cc/feed.xml?providers=postman
Slack
/feed subscribe https://outages.cc/feed.xml?providers=postman

Go from tracking outages to fixing production issues with Polylane.

Try Polylane