Postman: Existing gRPC responses are unavailable for users

What to do

Check whether you use Postman Postman Platform on Desktop, Postman Platform on Browser. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
Confirm your retries, queues and scheduled jobs caught up after the 2h 23m it lasted.
Anything that failed between 2026-03-13 09:17 UTC and 2026-03-13 11:40 UTC may need a replay.
Subscribe to Postman's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=postman works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

investigatingMar 13, 2026, 9:17 AM 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.
provider
identifiedMar 13, 2026, 9:21 AM UTC
The issue has been identified and a fix is being implemented.
provider
monitoringMar 13, 2026, 11:37 AM UTC
A fix has been implemented and we are monitoring the results.
provider
resolvedMar 13, 2026, 11:40 AM UTC
This incident has been resolved.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Postman still down?

No, this incident was resolved 2026-03-13 11:40 UTC. For Postman's live state, see https://down.guide/postman.

How long did it last?

2h 23m, from 2026-03-13 09:17 UTC to 2026-03-13 11:40 UTC, by the times Postman posted.

What was affected?

Postman named Postman Platform on Desktop, Postman Platform on Browser.

What caused it?

Postman hasn't published a root cause. If it does, it shows here.

Where does this come from?

Postman's official status page, https://status.postman.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.