Vendor Status Watch

← all vendors

Postman status history

Current state: operational — “All Systems Operational” per https://status.postman.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

1incidents, last 30 days
6incidents, last 90 days
27incidents on record
Incidents per week, last 12 weeks:

How long do Postman incidents last?

51 minmedian incident duration27 measured
3.6 h90th percentile1 in 10 ran longer
30 minmedian, major/critical only7 incidents

From 27 incidents with a vendor-posted start and resolve time. Longest on record: Users may encounter issues with accessing or using Postman — 15.2 h (2025-10-20 12:39 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (27)

StartedIncidentStatusImpactDuration
2026-09-10 18:01 UTCApi Builder flows are affected for US customersresolvedmajor25 min
2026-08-13 21:04 UTCpostman site is having issuesresolvedminor22 min
2026-07-22 16:42 UTCMarketing websiteresolvednone30 min
2026-07-17 12:33 UTCCollections and Environments view scenarios are degradedresolvedminor2 h 16 min
2026-07-06 19:41 UTCInfrastructural issues for Flows running in the cloudresolvednone37 min
2026-06-19 12:17 UTCElevated error rates for Agent Moderesolvedmajor30 min
2026-06-10 17:52 UTCError in downloading unclaimed account reportsresolvednone6 h 40 min
2026-04-25 16:44 UTCFlows logic blocks report an error when running locally in the appresolvednone2 h 45 min
2026-04-08 17:26 UTCProxy layer issues identifiedresolvednone19 min
2026-03-24 08:30 UTCApp Launch & Web Failures Resolvedresolvedminor0 min
2026-03-23 10:20 UTCFlows are slow to load in the appresolvednone8 h 48 min
2026-03-13 09:17 UTCExisting gRPC responses are unavailable for usersresolvedminor2 h 23 min
2026-03-07 00:44 UTCFlows are slow to loadresolvednone1 h 07 min
2026-03-06 17:18 UTCPostman MCP Server OAuth login failingresolvedminor25 min
2026-02-20 12:59 UTCPostman Collections not working in EU regionresolvedmajor13 min
2026-02-16 09:00 UTCPostman application got affected due to the issue in backend servicesresolvednone0 min
2026-02-12 16:51 UTCAgent Mode unavailableresolvedcritical1 h 13 min
2026-01-12 16:51 UTCPostman Flows modules are not running via cloud automations.resolvednone2 h 46 min
2025-12-17 14:14 UTCPostman Flows actions fail when triggered via webhook or scheduleresolvednone3 h 38 min
2025-12-05 09:03 UTCPostman is not loadingresolvedcritical23 min
2025-11-26 17:25 UTCLanding page issue discovered.resolvednone2 h 32 min
2025-11-20 16:40 UTCPostman network issues in EUresolvedmajor37 min
2025-11-06 21:46 UTCNetworking incidentresolvednone51 min
2025-10-28 17:42 UTCWorkspace load issueresolvednone44 min
2025-10-20 12:39 UTCUsers may encounter issues with accessing or using Postmanresolvednone15 h 12 min
2025-09-26 14:52 UTCCollection, Request, Example, Documentation creation/updations are not working.resolvedmajor51 min
2025-08-25 06:35 UTCDegraded services in Postman are causing slowness in Applicationresolvedminor58 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Postman with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "postman"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}