Statuspage: 500 errors to public pages from malicious traffic
Timeline of updates
- resolved
Due to a network DDoS affecting our load balancing layer in the us-east region, we experienced a surge in HTTP 500 responses from our public pages between 8:32 AM - 09:02AM and 10:30am - 10:50am PDT. This impacted 16-20% of the total traffic to public pages during these windows. We have gone ahead and made some updates to our edge compute services to prevent similar problems from arising.
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-07-08 17:12 UTC, resolved after 0 min, 1 update(s).
- Title
- 500 errors to public pages from malicious traffic
- Vendor
- Statuspage
- Date
- URL
- https://rewindex.com/company/statuspage/incidents/lvtf2xr3ndm9
Statuspage profileRecent Statuspage incidentsAll outages on July 8, 2019Statuspage in July 2019MarkdownJSON