Skip to content

Outage tracker

Postman: the full evidence record

The last 24 hours in detail, 15 days of measured availability, a 12-month summary, our own incident log, Postman's declared record, and how the two compare.

← Back to Postman's live status

We started measuring Postman on August 22, 2026, which is 15 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

The last 24 hours

What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Postman's own status page declared. Below it, any public chatter we saw about Postman and the extra probe it triggered.

The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Postman's own status page declared. Three records side by side; none of them changes another.

Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Postman in the last 24 hours, which is not evidence that nothing is wrong.
Postman's status pageNo incident declared in the last 24 hours.

Each probe cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused probe is not an outage. Report bars count unverified reports, not people we verified; they never change our reading. The status-page lane is Postman's own declaration, shown as they made it.

Third-party chatter, labeled

Public posts from the last hour that mention Postman next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.

No matching public posts in the last hour from the sources we watch.

Availability by region

Availability is measured probes that succeeded, divided by every probe we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionAvailabilityProbes recorded
US-East100.00%1841
US-West100.00%1829
Europe100.00%1760
Asia-Pacific100.00%1551
US-Central100.00%175
Canada100.00%175
UK100.00%174
Southeast Asia100.00%143
Australia100.00%140
South America100.00%165

Monthly summary

Tracking Postman since Aug 22, 2026. In that time our probes detected no outage. Months before that date are not tracked and carry no figure.

MonthUptimeOutagesDowntime
Oct 2025not tracked
Nov 2025not tracked
Dec 2025not tracked
Jan 2026not tracked
Feb 2026not tracked
Mar 2026not tracked
Apr 2026not tracked
May 2026not tracked
Jun 2026not tracked
Jul 2026not tracked
Aug 2026 from Aug 22, 2026100%00 min
Sep 2026100%00 min

Uptime here is the share of each month in which our probes had no outage open for Postman: two consecutive failed readings from a region opens one, the first clean reading closes it. Any detected outage counts, including one seen from a single region, and an outage that crosses midnight on the first of a month is counted in both months with its minutes split. User reports, public posts and Postman's own status page contribute nothing to these figures.

Our incident log

Every outage our own probes detected for Postman in the last 90 days, or since we started measuring it if that is more recent. This list is probe-only: Postman's own declared incidents appear further down this page in their own attributed section, never merged with what we measured here. User reports live on the live page, in their own labeled block.

No outages detected for Postman since we started measuring it on August 22, 2026. We show nothing from before that date.

Their declared record

Postman's own incident history, taken from their public status feed. This is their account of what happened, not our measurement, and it never changes the incident log above or the other way around.

postman site is having issuesMinor incident
Aug 13, 2026, 9:04 PM UTC to Aug 13, 2026, 9:27 PM UTC (23 min)resolved
their latest update (Aug 13, 2026, 9:27 PM UTC): The incident is resolved and the site is operational
Marketing websiteAll systems operational
Jul 22, 2026, 4:42 PM UTC to Jul 22, 2026, 5:12 PM UTC (30 min)resolved
their latest update (Jul 22, 2026, 5:12 PM UTC): DNS corrected. Engineers analyzing / auditing change events.
Collections and Environments view scenarios are degradedMinor incident
Jul 17, 2026, 12:33 PM UTC to Jul 17, 2026, 2:50 PM UTC (2h 16m)resolved
their latest update (Jul 17, 2026, 2:50 PM UTC): We have monitored stats and service has been stable.
Infrastructural issues for Flows running in the cloudAll systems operational
Jul 6, 2026, 7:41 PM UTC to Jul 6, 2026, 8:18 PM UTC (37 min)resolved
their latest update (Jul 6, 2026, 8:18 PM UTC): This incident has been resolved.
Elevated error rates for Agent ModePartial outage
Jun 19, 2026, 12:17 PM UTC to Jun 19, 2026, 12:48 PM UTC (30 min)resolved
their latest update (Jun 19, 2026, 12:48 PM UTC): This incident has been resolved.
Error in downloading unclaimed account reportsAll systems operational
Jun 10, 2026, 5:52 PM UTC to Jun 11, 2026, 12:32 AM UTC (6h 40m)resolved
their latest update (Jun 11, 2026, 12:32 AM UTC): This incident has been resolved.
Flows logic blocks report an error when running locally in the appAll systems operational
Apr 25, 2026, 4:44 PM UTC to Apr 25, 2026, 7:29 PM UTC (2h 45m)resolved
their latest update (Apr 25, 2026, 7:29 PM UTC): This incident has been resolved.
Proxy layer issues identifiedAll systems operational
Apr 8, 2026, 5:26 PM UTC to Apr 8, 2026, 5:46 PM UTC (20 min)resolved
their latest update (Apr 8, 2026, 5:46 PM UTC): This incident has been resolved.
App Launch & Web Failures ResolvedMinor incident
Mar 24, 2026, 3:51 PM UTC to Mar 24, 2026, 8:30 AM UTC (0 min)resolved
their latest update (Mar 24, 2026, 8:30 AM UTC): New 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.
Flows are slow to load in the appAll systems operational
Mar 23, 2026, 10:20 AM UTC to Mar 23, 2026, 7:09 PM UTC (8h 49m)resolved
their latest update (Mar 23, 2026, 7:09 PM UTC): This incident has been resolved.

Showing the 10 most recent of 50 incidents Postman has declared in the history we hold.

These entries are Postman's own declarations, taken from their public status feed, shown separately from the outages we detected ourselves. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.

The scorecard

How Postman's status page compared with what we measured, for every outage above that falls inside the window we have been capturing their claims.

We started recording Postman's own status page on August 22, 2026, 13 days ago. This comparison covers that period only, we do not reconstruct what they said before it, and we compare only inside outages we measured ourselves.

We have not measured an outage for Postman since we started recording their status page, so there is nothing to compare. That is a short measurement window, not a track record.

Postman decides what their status page covers, and it may report per component while our check reaches one surface from ten regions. We state what each side measured and leave the conclusion to you. If Postman believes a figure here is wrong, we publish corrections as prominently as the original.

Full detail on what a probe does and does not prove is in the methodology page.