Statuspage: Temporary Statuspage service disruption.
Timeline of updates
- resolved
Between 1:26 and 1:30PM PT, Statuspage service was degraded for a significant portion of our customers. During this timeframe, the management portal, manage API, and notifications were performing as expected. This incident was due to an unplanned redeploy of our caching layer. Given that this redeploy was performed during peak hours, a large influx of requests on the new cluster caused the backend to get overwhelmed and stop responding momentarily.
From Statuspage’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 metastatuspage.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Statuspage, started 2019-02-25 21:26 UTC, resolved after 0 min, 1 update(s).
- Title
- Temporary Statuspage service disruption.
- Vendor
- Statuspage
- Date
- URL
- https://rewindex.com/company/statuspage/incidents/bnd3rrdm1y9c
Statuspage profileRecent Statuspage incidentsAll outages on February 25, 2019Statuspage in February 2019MarkdownJSON