Statuspage: 500 errors to public pages
Timeline of updates
- resolved
There was a small increase in HTTP 500 responses between 05:06AM and 5:12AM Pacific Time, impacting about 10% of the traffic to public pages. This happened due to a spike in network traffic. This behavior was sporadic and may have impacted only some customers. As part of a remediation plan, we went through a round of capacity adjustment on our edge nodes, and we are also planning to enhance some functionalities to handle this type of bursty traffic.
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-05-29 12:06 UTC, resolved after 0 min, 1 update(s).
- Title
- 500 errors to public pages
- Vendor
- Statuspage
- Date
- URL
- https://rewindex.com/company/statuspage/incidents/v9g0gfd97jp4
Statuspage profileRecent Statuspage incidentsAll outages on May 29, 2019Statuspage in May 2019MarkdownJSON