Statuspage: 500 errors to public pages
Timeline of updates
- resolved
A deploy to our caching layer caused a brief increase in HTTP 500 responses between 1:55 PM and 2:00 PM Pacific Time, impacting 30% of traffic to public status pages. This has since been remedied and the service is now operating normally.
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-10-03 20:55 UTC, resolved after 0 min, 1 update(s).
- Title
- 500 errors to public pages
- Vendor
- Statuspage
- Date
- URL
- https://rewindex.com/company/statuspage/incidents/27s4hx8p5k98
Statuspage profileRecent Statuspage incidentsAll outages on October 3, 2019Statuspage in October 2019MarkdownJSON