Amplitude Status · History · Incident #5882
RESOLVEDIntermittent Connectivity Issues
Minor · Started Jul 24, 2026 · 10:05 AM
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
Amplitude Status · History · Incident #5882
RESOLVEDMinor · Started Jul 24, 2026 · 10:05 AM
Duration
< 1m
Severity
Minor
Detection lead
—
User reports
—
Summary
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.
Started
Jul 24, 2026 · 10:05 AM
Resolved
Jul 24, 2026 · 10:05 AM
Duration
< 1m
Severity
None
Event timeline
Resolved
Jul 24 · 10:05 AM AmplitudeBetween 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.
Pattern
Delay in realtime data processing
Aug 1, 2026 · 26m
View incident →We are actively investigating a delay in our pipeline processing
Jul 31, 2026 · 1h 44m
View incident →We are actively investigating bigquery exports taking a long time to complete
Jul 24, 2026 · 1h 14m
View incident →Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026. Pulsetic® is a registered trademark.