Amplitude: Increase in HTTP 500 response codes to US data center data collection endpoints
Timeline of updates
- resolved
On May 20th, between 1:07 and 1:17 AM UTC, Amplitude customers sending data to the US data center data collection endpoints experienced a significant spike in HTTP 500 response codes. This was quickly resolved after addressing an issue within our internal systems. For requests that received an HTTP 200 response, no data has been lost.
From Amplitude’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 status.amplitude.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Amplitude, started 2025-05-20 01:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Increase in HTTP 500 response codes to US data center data collection endpoints
- Vendor
- Amplitude
- Date
- URL
- https://rewindex.com/company/amplitude/incidents/sv8q291bgq1y
Amplitude profileRecent Amplitude incidentsAll outages on May 20, 2025Amplitude in May 2025MarkdownJSON