Minor impactResolvedDevOps

Postman incident: Existing gRPC responses are unavailable for users

Postman reported this minor-impact incident on its official status page on Mar 13, 2026, 09:17 UTC. It was resolved after 2h 23m.

Right now Postman is operational. Live Postman status →

🔔 Get alerted when Postman has issuesFree · email alerts · no credit card
Mar 13, 2026, 09:17 UTC
started
Mar 13, 2026, 11:40 UTC
resolved
2h 23m
duration
Minor
impact

Affected components

  • Postman Platform on Browser
  • Postman Platform on Desktop
  1. resolvedMar 13, 2026, 11:40 UTC

    This incident has been resolved.

  2. monitoringMar 13, 2026, 11:37 UTC

    A fix has been implemented and we are monitoring the results.

  3. identifiedMar 13, 2026, 09:21 UTC

    The issue has been identified and a fix is being implemented.

  4. investigatingMar 13, 2026, 09:17 UTC

    The issue happened during an infrastructure upgrade. The team is working on fixing the issue. Until the issue gets mitigated, existing gRPC responses wont be visible. New gRPC responses will continue to work.

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 Mar 13, 2026: Existing gRPC responses are unavailable for users · APIStatus.watch