Postman Outage History

29 incidents recorded over the last 365 days, 25 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.

Live Postman status100.00% uptime history

Every Recorded Postman Incident

Postman incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Sep 26, 2026Planned database maintenance with possible service disruption in US, EU regionScheduled maintenance is currently in progress. We will provide updates as necessary.1h 0mScheduled
Sep 10, 2026Api Builder flows are affected for US customersAll scenarios have recovered and the issue is mitigated.25 minResolved
Aug 15, 2026Planned database maintenance with possible service disruption in US regionThe scheduled maintenance has been completed.2h 0mScheduled
Aug 13, 2026postman site is having issuesThe incident is resolved and the site is operational22 minResolved
Jul 22, 2026Marketing websiteDNS corrected. Engineers analyzing / auditing change events.30 minResolved
Jul 17, 2026Collections and Environments view scenarios are degradedWe have monitored stats and service has been stable.2h 16mResolved
Jul 6, 2026Infrastructural issues for Flows running in the cloudThis incident has been resolved.37 minResolved
Jun 19, 2026Elevated error rates for Agent ModeThis incident has been resolved.30 minResolved
Jun 10, 2026Error in downloading unclaimed account reportsThis incident has been resolved.6h 40mResolved
Apr 25, 2026Flows logic blocks report an error when running locally in the appThis incident has been resolved.2h 45mResolved
Apr 8, 2026Proxy layer issues identifiedThis incident has been resolved.19 minResolved
Mar 24, 2026App 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 minResolved
Mar 23, 2026Flows are slow to load in the appThis incident has been resolved.8h 48mResolved
Mar 13, 2026Existing gRPC responses are unavailable for usersThis incident has been resolved.2h 23mResolved
Mar 7, 2026Flows are slow to loadThis incident has been resolved.1h 7mResolved
Mar 6, 2026Postman MCP Server OAuth login failingThis incident has been resolved.25 minResolved
Feb 20, 2026Postman Collections not working in EU regionCollections in EU are fully working now.13 minResolved
Feb 16, 2026Postman 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 minResolved
Feb 12, 2026Agent Mode unavailableThis incident has been resolved.1h 13mResolved
Jan 12, 2026Postman Flows modules are not running via cloud automations.This incident has been resolved.2h 46mResolved
Dec 17, 2025Postman Flows actions fail when triggered via webhook or scheduleThis incident has been resolved.3h 38mResolved
Dec 5, 2025Postman is not loadingThis incident has been resolved.23 minResolved
Nov 26, 2025Landing page issue discovered.Recent service deployment reverted2h 32mResolved
Nov 20, 2025Postman network issues in EUReverting the maintenance operation has resolved the connectivity issues.37 minResolved
Nov 6, 2025Networking incidentNetwork connectivity issues resolved.51 minResolved
Oct 28, 2025Workspace load issueThis incident has been resolved.44 minResolved
Oct 20, 2025Users may encounter issues with accessing or using PostmanThis incident has been resolved.15h 12mResolved
Oct 12, 2025Planned database maintenance with possible service disruption in US regionThe scheduled maintenance has been completed.2h 0mScheduled
Oct 11, 2025Planned database maintenance with possible service disruption of collection runs.Scheduled database maintenance has been successfully completed.2h 0mScheduled

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Postman incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

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.