Amplitude Incident History

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are investigating a delay in real time data processing. No data is lost

This incident has been resolved.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

We are actively investigating a delay in our pipeline processing. No data is lost.

Between approximately 2026-07-24 03:39–05:00 PT (10:39–12:00 UTC), some customers may have experienced intermittent connectivity issues while accessing Amplitude or sending data, including connection timeouts. This was caused by an AWS networking disruption in the us-west-2 region affecting multiple upstream AWS services. The issue originated outside of Amplitude's infrastructure and was resolved by AWS. Services: - Our SDKs queue undelivered events on-device and automatically retry sending them, so we expect minimal to no data loss from this incident. No ingested data was lost and no action is required. - Experiment/Flag evaluations failed and return 503s due to service unavailability. There is no data loss.

This incident has been resolved.

The jobs waiting on google's end have started recovering and we are seeing jobs making progress within Amplitude too

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are actively investigating a delay in real time data processing. No data is lost.

We identified the source of the issue and rolled back the responsible change at 12:06 PM PT (19:06 UTC). Error rates have returned to normal, and we are actively monitoring to confirm full stability. There is no data loss. No customer action is needed at this time.