Skip to content
OutageDeck

Incident detail

Data Processing Delays

Data Processing Delays

Resolved incidentMinor0 affected services

Timeline window

to

Timeline

Incident updates

Updates are normalized from the official source chronology so timeline changes remain easy to scan.

  1. Investigating

    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.

  2. Identified

    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.

  3. Identified

    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.

  4. Monitoring

    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.

  5. Monitoring

    We are continuing to monitor for any further issues.

  6. Monitoring

    We are continuing to monitor for any further issues.

  7. Monitoring

    The issue has been resolved.

  8. Resolved

    This incident has been resolved.