Amplitude incident: Data Processing Delays

Affected components

• Amazon Web Services
• Cohort Export
• Data Processing
• Evaluation API

1. resolvedApr 29, 2026, 14:33 UTC

   This incident has been resolved.

2. monitoringApr 29, 2026, 09:54 UTC

   The issue has been resolved.

3. monitoringApr 29, 2026, 09:10 UTC

   We are continuing to monitor for any further issues.

4. monitoringApr 29, 2026, 08:59 UTC

   We are continuing to monitor for any further issues.

5. monitoringApr 29, 2026, 08:39 UTC

   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.

6. identifiedApr 29, 2026, 08:30 UTC

   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.

7. identifiedApr 29, 2026, 08:20 UTC

   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.

8. investigatingApr 29, 2026, 08:15 UTC

   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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Amplitude's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Snyk: Snyk recurring tests showing slow performanceMinor · Apr 21, 2026, 18:58 UTC
• Akamai: Intermittent Edge Delivery Delays in Chennai, IN (MAA) RegionMinor · Apr 28, 2026, 16:42 UTC
• Linode: Service Issue - Connectivity Issues - Chennai (IN-MAA)Minor · Apr 28, 2026, 17:17 UTC
• Akamai: Reporting Issues affecting URL Traffic and URL Responses reportsMinor · Apr 29, 2026, 05:19 UTC
• Linode: Object Storage Key creation and validation failing with error 403 in multiple data centersMinor · Apr 29, 2026, 09:22 UTC

How often does Amplitude have incidents?

Amplitude reported 17 incidents in the last 90 days, 7 of them major or critical. A typical incident lasted 2h 23m. See Amplitude's uptime and incident history