Minor impactResolvedDevOps

Postman incident: Collections and Environments view scenarios are degraded

Postman reported this minor-impact incident on its official status page on Jul 17, 2026, 12:33 UTC. It was resolved after 2h 16m.

Right now Postman is operational. Live Postman status →

🔔 Get alerted when Postman has issuesFree · email alerts · no credit card
Jul 17, 2026, 12:33 UTC
started
Jul 17, 2026, 14:50 UTC
resolved
2h 16m
duration
Minor
impact

Affected components

  • Postman Platform on Browser
  • Postman Platform on Desktop
  1. resolvedJul 17, 2026, 14:50 UTC

    We have monitored stats and service has been stable.

  2. monitoringJul 17, 2026, 13:35 UTC

    A fix has been deployed and we are monitoring the health of the service

  3. identifiedJul 17, 2026, 13:32 UTC

    The team has identified an issue with the service probe endpoint and deploying a fix.

  4. investigatingJul 17, 2026, 12:33 UTC

    Collections fetch flows are facing failures and increased latencies. Team is investigating the issue

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Postman's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Postman have incidents?

Postman reported 3 incidents in the last 90 days, 1 of them major or critical. A typical incident lasted 25 min. See Postman's uptime and incident history

Postman incident on Jul 17, 2026: Collections and Environments view scenarios are degraded · APIStatus.watch