Statuspage: Service Disruption due to Excessive Load
Timeline of updates
- unknown
At 7:56PM MST due to high load on our web nodes we experienced a two minute service disruption. During the period of high load we had a process whose purpose is to reap processes that meet a certain criteria. Once those processes came back online service was restored to normal. We have added additional logging and monitoring around this area and we’re evaluating changes to how we reap these processes when the service is under load.
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 2015-02-24 19:40 UTC, not resolved, 1 update(s).
- Title
- Service Disruption due to Excessive Load
- Vendor
- Statuspage
- Date
- URL
- https://rewindex.com/company/statuspage/incidents/6n21xvzgzdx7
Statuspage profileRecent Statuspage incidentsAll outages on February 24, 2015Statuspage in February 2015MarkdownJSON