Postman · Operational
Observed by INTERNETMON
← All status pages
Vendor-reported status observed by INTERNETMON

Postman status

Postman · Atlassian Statuspage
Operational
Atlassian Statuspage reports All Systems Operational.
Official service health, components and incident updates
Checked Poll cadence every 60 seconds Feed state fresh
Official signal: this is the provider's own report, collected and retained inside INTERNETMON. Compare it with independent regional monitoring when troubleshooting.

Active incidents

No active incidents were included in this vendor report.

Maintenance

No active or upcoming maintenance was included in this vendor report.

Component health

Reported
29
Retained
29
Affected retained
0
Projection scope: complete · 29 retained of 29 reported components across 2 source groups.
Postman Platform on Desktop Group: US Operational
Postman Platform on Desktop Group: Europe Operational
Postman Platform on Browser Group: US Operational
Postman Platform on Browser Group: Europe Operational
Postman Login Group: US Operational
Postman Login Group: Europe Operational
Postman Monitors Group: US Operational
Postman Mocks Group: Europe Operational
Postman Mocks Group: US Operational
Postman API Group: Europe Operational
Postman API Group: US Operational
Postman Search Group: Europe Operational
Postman API Network (API Explore) Group: US Operational
Run Button Group: US Operational
Postman Search Group: US Operational
Public Collection Documentation Group: US Operational
Newman Group: US Operational
Postman Learning Center and Documentation Group: US Operational
Postman Support and Community Forum Group: US Operational
Postman Integrations Group: US Operational
Showing 20 of 29 retained components in the compact HTML summary. The JSON projection and interactive view contain the full bounded sample.

Recent observed status changes and checkpoints

These are sparse stored checkpoints—state changes plus hourly samples—not an uptime calculation or an exact incident duration.

Operational
HTTP 200 · 214.56 ms feed latency
Operational
HTTP 200 · 306.95 ms feed latency
Operational
HTTP 200 · 272.51 ms feed latency
Operational
HTTP 200 · 255.56 ms feed latency
Operational
HTTP 200 · 76.79 ms feed latency
Operational
HTTP 200 · 201.69 ms feed latency
Operational
HTTP 200 · 108.21 ms feed latency
Operational
HTTP 200 · 151.76 ms feed latency
Operational
HTTP 200 · 71.85 ms feed latency
Operational
HTTP 200 · 163.88 ms feed latency

Collection details

Provider adapter
Atlassian Statuspage
Feed response
HTTP 200
Feed latency
384.79 ms