[Scheduled] Planned database maintenance with possible service disruption in US
We will be undergoing scheduled maintenance during this time.
The latest update from Postman.
State
Scheduled
Starts
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by Postman
We will be undergoing scheduled maintenance during this time.
Planned database upgrade in the US data center We will be performing a planned database migration in the US data center . During this time, users with data in the US region may experience temporary service disruptions while using Postman across all platforms. Some or more operations will be temporarily impacted, including: - Creating a workspace, team, or partnership group - Creating a collection, API, environment, mock, or monitor - Moving collections or other items between workspaces - Deleting workspaces, collections, APIs, environments, mocks, or monitors - Deleting or restoring items from Trash These actions will be temporarily unavailable during the maintenance freeze. Please retry them after the maintenance window has ended. Existing data remains safe and unaffected. We appreciate your patience and understanding during this maintenance window.
Affected components
20Postman in the last 90 days
Full historyIncidents in 90 days
1
Days with an incident
1
Median duration
25 min
This incident
Not comparable
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.live/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.live/feed.xml?providers=postman/feed subscribe https://outages.live/feed.xml?providers=postmanFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane