Amplitude Status · History · Incident #1100
RESOLVEDData Processing Delays
Minor · Started Apr 29, 2026 · 1:15 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 #1100
RESOLVEDMinor · Started Apr 29, 2026 · 1:15 AM
Duration
6h 17m
Severity
Minor
Detection lead
—
User reports
—
Summary
This incident has been resolved.
Started
Apr 29, 2026 · 1:15 AM
Resolved
Apr 29, 2026 · 7:33 AM
Duration
6h 17m
Severity
Minor
Event timeline
Investigating
Apr 29 · 1:15 AM AmplitudeOur data processing systems are delayed. This incident started at 2026-04-29 12:20 AM PT. Current status: a) Our ingestion systems are working as expected and no data is lost. Our processing systems are not processing newly ingested data. b) Impacted customers will see delayed metrics for the last 1 hour. c) Experiment evaluation API is experiencing higher latencies. d) Cohort syncs to all 3rd party destinations is experiencing higher latencies. We've identified the issue and are working closely with our cloud provider to mitigate it. We will provide an update within the next hour, or sooner if new information becomes available.
Identified
Apr 29 · 1:20 AM AmplitudeOur data processing systems are delayed. This incident started at 2026-04-29 12:20 AM PT. Current status: a) Our ingestion systems are working as expected and no data is lost. Our processing systems are not processing newly ingested data. b) Impacted customers will see delayed metrics for the last 1 hour. c) Experiment evaluation API is experiencing higher latencies. d) Cohort syncs to all 3rd party destinations is experiencing higher latencies. We've identified the issue and are working closely with our cloud provider to mitigate it. We will provide an update within the next hour, or sooner if new information becomes available.
Identified
Apr 29 · 1:30 AM AmplitudeAWS has identified the issue and is actively working on a resolution. We will provide an update within the next hour, or sooner if new information becomes available.
Monitoring
Apr 29 · 1:39 AM AmplitudeAWS and Amplitude has mitigated the issue and are seeing recovery on impacted services. We will continue to monitor the status and provide an update within the next hour, or sooner if new information becomes available.
Monitoring
Apr 29 · 1:59 AM AmplitudeWe are continuing to monitor for any further issues.
Monitoring
Apr 29 · 2:10 AM AmplitudeWe are continuing to monitor for any further issues.
Monitoring
Apr 29 · 2:54 AM AmplitudeThe issue has been resolved.
Resolved
Apr 29 · 7:33 AM AmplitudeThis incident has been resolved.
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime. Try Free
Made by Designmodo
MONITORING
SERVICE
COMPARE
ACCOUNT