← Back to Amplitude History
minor✓ Resolved

Data Processing Delays

AmplitudeWed, Apr 29, 2026, 08:15 AM
Status
resolved
Duration
6h 20m
Updates
7
Coverage
0 articles

INCIDENT TIMELINE

✓ ResolvedWed, Apr 29, 2026, 02:35 PM
This incident has been resolved.
monitoringWed, Apr 29, 2026, 09:54 AM
The issue has been resolved.
monitoringWed, Apr 29, 2026, 09:10 AM
We are continuing to monitor for any further issues.
monitoringWed, Apr 29, 2026, 08:59 AM
We are continuing to monitor for any further issues.
monitoringWed, Apr 29, 2026, 08:39 AM
AWS 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.
identifiedWed, Apr 29, 2026, 08:30 AM
AWS 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.
identifiedWed, Apr 29, 2026, 08:20 AM
Our 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.
investigatingWed, Apr 29, 2026, 08:15 AM
Our 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.

📊 TECHNICAL DETAILS

Internal ID
a238663a-1219-4b7b-ab55-e1e7e7ae352a
External ID
y74nshmt30vk
🕐 Started
Wed, Apr 29, 2026, 08:15 AM
🔄 Last Updated
Wed, Apr 29, 2026, 02:35 PM
✓ Resolved
Wed, Apr 29, 2026, 02:35 PM
MINOR
Impact Level
6h 20m
Total Duration
7
Status Updates
Affected Components
Evaluation APIData ProcessingCohort ExportAmazon Web Services
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed