Intermittent Connectivity Issues

What to do

• Check whether you use Amplitude Web Application, Data Processing, Data Reception in us, us-west-2. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-07-24 17:05 UTC and 2026-07-24 17:05 UTC may need a replay.

• Subscribe to Amplitude's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=amplitude works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Amplitude 1

1. resolvedJul 24, 2026, 5:05 PM UTC

   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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.