Postman reported "Api Builder flows are affected for US customers" on its status page at 2026-09-10 18:01 UTC.

Postman lists these components: API Builder, US - API Builder.

When did the incident start and end?

It started at 2026-09-10 18:01 UTC and ended at 2026-09-10 18:26 UTC. It lasted 25 min.

How do I get alerts for Postman?

Subscribe to the Postman live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Postman. outages.live reads it every few minutes and keeps every update.

PostmanIncident · 2026-09-10 18:01 UTC

Api Builder flows are affected for US customers

ResolvedOfficial update

All scenarios have recovered and the issue is mitigated.

The latest update from Postman.

State

Resolved

Started

52 d ago

2026-09-10 18:01 UTC

Lasted

25 min

until 2026-09-10 18:26 UTC

Worst impact

Partial outage

Timeline

5 updates

18:0118:0718:1318:2018:26

Partial outageUpdate postedTimes in UTC

Investigating

16 min 62%

Identified

1 min 3%

Monitoring

9 min 35%

Updates

Times in UTC

As posted by Postman

Resolved2026-09-10 18:26 UTC

All scenarios have recovered and the issue is mitigated.

Monitoring2026-09-10 18:17 UTC

A fix for the db resources has been applied and team is monitoring the service health

Identified2026-09-10 18:17 UTC

The issue has been identified and a fix is being implemented.

Investigating2026-09-10 18:16 UTC

The team has identified an issue with the database and is working on a fix.

Investigating2026-09-10 18:01 UTC

We are currently investigating this issue.

Affected components

API BuilderUS - API Builder

Postman in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

24 min

This incident

About the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

25 min

median 24 min

90 days agoToday

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane