Postman

Operational

2components tracked.· Official status page

US Operational

oldest now

Europe Operational

oldest now

Recent Incidents

Proxy layer issues identifiednone

Apr 8, 17:26 UTC — resolved 17:46

Postman Platform on DesktopPostman Platform on BrowserPostman Login

resolved Apr 8, 17:46 UTC

This incident has been resolved.

identified Apr 8, 17:36 UTC

The issue has been identified and mitigation is being implemented

investigating Apr 8, 17:26 UTC

We have identified an issue with our EU proxy layer. Teams are investigating

App Launch & Web Failures Resolvedminor

Mar 24, 15:51 UTC — resolved 08:30

resolved Mar 24, 15:51 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 appnone

Mar 23, 10:20 UTC — resolved 19:09

resolved Mar 23, 19:09 UTC

This incident has been resolved.

monitoring Mar 23, 16:35 UTC

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

investigating Mar 23, 15:00 UTC

We are continuing to investigate this issue.

investigating Mar 23, 14:59 UTC

We are currently investigating this issue.

monitoring Mar 23, 11:28 UTC

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

investigating Mar 23, 10:20 UTC

We are currently investigating this issue.

Existing gRPC responses are unavailable for usersminor

Mar 13, 09:17 UTC — resolved 11:40

Postman Platform on DesktopPostman Platform on Browser

resolved Mar 13, 12:08 UTC

This incident has been resolved.

monitoring Mar 13, 12:07 UTC

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

identified Mar 13, 09:21 UTC

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

investigating Mar 13, 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.

Flows are slow to loadnone

Mar 7, 00:44 UTC — resolved 01:52

resolved Mar 7, 01:52 UTC

This incident has been resolved.

monitoring Mar 7, 01:42 UTC

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

identified Mar 7, 01:28 UTC

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

investigating Mar 7, 00:44 UTC

We are currently investigating this issue.

Refreshes every 30s. Last updated: 16:02:54