Postman Outage History
31 incidents recorded over the last 365 days, 26 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Postman Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Aug 15, 2026 | Planned database maintenance with possible service disruption in US regionVerification is currently underway for the maintenance items. | 2h 0m | Scheduled |
| Aug 13, 2026 | postman site is having issuesThe incident is resolved and the site is operational | 22 min | Resolved |
| Jul 22, 2026 | Marketing websiteDNS corrected. Engineers analyzing / auditing change events. | 30 min | Resolved |
| Jul 17, 2026 | Collections and Environments view scenarios are degradedWe have monitored stats and service has been stable. | 2h 16m | Resolved |
| Jul 6, 2026 | Infrastructural issues for Flows running in the cloudThis incident has been resolved. | 37 min | Resolved |
| Jun 19, 2026 | Elevated error rates for Agent ModeThis incident has been resolved. | 30 min | Resolved |
| Jun 10, 2026 | Error in downloading unclaimed account reportsThis incident has been resolved. | 6h 40m | Resolved |
| Apr 25, 2026 | Flows logic blocks report an error when running locally in the appThis incident has been resolved. | 2h 45m | Resolved |
| Apr 8, 2026 | Proxy layer issues identifiedThis incident has been resolved. | 19 min | Resolved |
| Mar 24, 2026 | App Launch & Web Failures ResolvedNew app launches and web requests were failing due to a dependency issue. Existing sessions remained unaffected. The issue has been fixed and systems are fully operational. | -441 min | Resolved |
| Mar 23, 2026 | Flows are slow to load in the appThis incident has been resolved. | 8h 48m | Resolved |
| Mar 13, 2026 | Existing gRPC responses are unavailable for usersThis incident has been resolved. | 2h 23m | Resolved |
| Mar 7, 2026 | Flows are slow to loadThis incident has been resolved. | 1h 7m | Resolved |
| Mar 6, 2026 | Postman MCP Server OAuth login failingThis incident has been resolved. | 25 min | Resolved |
| Feb 20, 2026 | Postman Collections not working in EU regionCollections in EU are fully working now. | 13 min | Resolved |
| Feb 16, 2026 | Postman application got affected due to the issue in backend servicesThe issue occured due to the failures in the backend services. It has been fixed and the team is monitoring the health of the application. | -37 min | Resolved |
| Feb 12, 2026 | Agent Mode unavailableThis incident has been resolved. | 1h 13m | Resolved |
| Jan 12, 2026 | Postman Flows modules are not running via cloud automations.This incident has been resolved. | 2h 46m | Resolved |
| Dec 17, 2025 | Postman Flows actions fail when triggered via webhook or scheduleThis incident has been resolved. | 3h 38m | Resolved |
| Dec 5, 2025 | Postman is not loadingThis incident has been resolved. | 23 min | Resolved |
| Nov 26, 2025 | Landing page issue discovered.Recent service deployment reverted | 2h 32m | Resolved |
| Nov 20, 2025 | Postman network issues in EUReverting the maintenance operation has resolved the connectivity issues. | 37 min | Resolved |
| Nov 6, 2025 | Networking incidentNetwork connectivity issues resolved. | 51 min | Resolved |
| Oct 28, 2025 | Workspace load issueThis incident has been resolved. | 44 min | Resolved |
| Oct 20, 2025 | Users may encounter issues with accessing or using PostmanThis incident has been resolved. | 15h 12m | Resolved |
| Oct 12, 2025 | Planned database maintenance with possible service disruption in US regionThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Oct 11, 2025 | Planned database maintenance with possible service disruption of collection runs.Scheduled database maintenance has been successfully completed. | 2h 0m | Scheduled |
| Oct 4, 2025 | Planned database maintenance with possible service disruption of collection runsThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Sep 27, 2025 | Planned database maintenance with possible service disruption in EU regionThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Sep 26, 2025 | Collection, Request, Example, Documentation creation/updations are not working.This incident has been resolved. We are currently investigating the root cause of the issue. | 51 min | Resolved |
| Aug 25, 2025 | Degraded services in Postman are causing slowness in ApplicationThis incident has been resolved. | 58 min | Resolved |
How to Read This Postman Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Postman acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Postman outage in this window ran 15h 12m, against a mean recovery of 2h 18m. If you depend on Postman in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.