Intermittent Connectivity Issues
Final update
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.
Timeline
- Resolved · Jul 24, 17:05 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.
More from Amplitude
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 2419:47 UTC | Export Destinations data delivery issue | minor | 1h 34m |
| Sep 2308:02 UTC | Export Destinations data delivery issue | major | 6h 5m |
| Sep 2218:49 UTC | Snowflake Data Share export delivery issue | major | 6h 4m |
| Sep 1720:05 UTC | Realtime Data Pipeline Delay | minor | 1h 11m |
| Sep 1100:19 UTC | S3 export delivery permissions - Resolved | none | 0m |
| Sep 1003:07 UTC | We are actively investigating an issue with our realtime ingestion pipelines. | minor | 54m |
Also caused by network
All| Started | Vendor | Incident | Impact | Duration |
|---|---|---|---|---|
| Sep 1901:36 UTC |  Cloudflare | Elevated errors in Ashburn, VA (IAD)Cloudflare | none | 0m |
| Sep 1411:59 UTC |  CircleCI | Increased wait times for macOS jobsCircleCI | minor | 1h |
| Sep 410:57 UTC |  Netlify | Increased errors on High Performance Edge Network - FRA RegionNetlify | minor | 0m |
| Sep 214:18 UTC |  Fly.io | Upstream network issuesFly.io | minor | 1h 39m |
| Sep 116:11 UTC |  ClickHouse | Service degradation in GCP us-central-1ClickHouse | none | 19m |
| Sep 114:44 UTC |  Google Cloud | Multiple products in us-central1-b are experiencing network service degradation.Google Cloud | major | 4h 8m |
Sources: vendors' own status pages, published postmortems and SEC 8-K Item 1.05 filings, read daily. Times as reported. Logos via logo.dev; trademarks belong to their owners.