Postman: Monitors incorrectly paused by system
Timeline of updates
- resolved
A small fraction of our userbase experienced an unexpected "paused by system" of their monitors on April 18, 8:00 AM UTC. As of April 19 11:30am UTC, all such erroneously paused monitors have been resumed and are functioning as expected. We suspect that this happened because of the monitoring system misrepresenting one of our maintenance activities as unavailability of the underlying data. We are working towards applying additional guardrails to prevent this from happening in future. We understand that this was a disruptive event and we take this very seriously. The activity logs for your monitors should show the relevant "pause" events, and will soon show the "resume" system event as well to reflect the incident window.
From Postman’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.postman.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Postman, started 2021-04-18 08:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Monitors incorrectly paused by system
- Vendor
- Postman
- Date
- URL
- https://rewindex.com/company/postman/incidents/0w22p6007vs6
Postman profileRecent Postman incidentsAll outages on April 18, 2021Postman in April 2021MarkdownJSON