Vendor reports: operationalResolved · vendor status “resolved”Official status API

Users may encounter issues with accessing or using Postman

Reported by Postman · Developer Tools & CI/CD · source last read 2 min ago

Official source (opens in a new tab)
Vendor start
Oct 20, 2025, 12:39 UTC
Vendor's clock
Resolved
Oct 21, 2025, 03:51 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
15 h 12 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Postman reports operational: "Users may encounter issues with accessing or using Postman".[E1, E2]
  • The vendor marked it resolved at 2025-10-21 03:51 UTC.[E3, E7]

Affected products and regions

  • Components: Postman Platform on Desktop, Postman Platform on Browser, Postman Login, Postman Monitors, Postman Mocks, Postman API, Postman API Network (API Explore), Run Button, Postman Search, Public Collection Documentation, Newman, Postman Learning Center and Documentation, Postman Support and Community Forum, Postman Integrations, Postman Interceptor, Marketing Website, Postbot, Postman VS Code extension, API Builder, API Specifications, Collection Runner, Postman CLI.[E6]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2025-10-21 03:51 UTC · summary s1, evidence fb678701ee2134d7

Evidence (7)
  1. E1Postman reports operational. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Users may encounter issues with accessing or using Postman". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2025-10-20 12:39 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Postman Platform on Desktop, Postman Platform on Browser, Postman Login, Postman Monitors, Postman Mocks, Postman API, Postman API Network (API Explore), Run Button, Postman Search, Public Collection Documentation, Newman, Postman Learning Center and Documentation, Postman Support and Community Forum, Postman Integrations, Postman Interceptor, Marketing Website, Postbot, Postman VS Code extension, API Builder, API Specifications, Collection Runner, Postman CLI. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2025-10-21 03:51 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: Postman Platform on Desktop, Postman Platform on Browser, Postman Login, Postman Monitors, Postman Mocks, Postman API, Postman API Network (API Explore), Run Button, Postman Search, Public Collection Documentation, Newman, Postman Learning Center and Documentation, Postman Support and Community Forum, Postman Integrations, Postman Interceptor, Marketing Website, Postbot, Postman VS Code extension, API Builder, API Specifications, Collection Runner, Postman CLI

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

Potential relevance

Postman is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Oct 20, 2025, 12:39 UTCVendor-reported startVendor time
  2. Oct 21, 2025, 03:51 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.