Skip to main content
Amplitude

Data Processing Delays

Degraded Lasted 6h 18m · started · Amplitude's page

Level
confirmed
Worst impact
Degraded
Components
Evaluation API, Data Processing, Cohort Export, Amazon Web Services
Down Index
37of 100

What to do

  • Check whether you use Amplitude Evaluation API, Data Processing, Cohort Export, Amazon Web Services. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 6h 18m it lasted.

    Anything that failed between 2026-04-29 08:15 UTC and 2026-04-29 14:33 UTC may need a replay.
  • Subscribe to Amplitude's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=amplitude works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Amplitude 8

  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.

    provider

  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.

    provider

  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.

    provider

  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.

    provider

  5. monitoring

    We are continuing to monitor for any further issues.

    provider

  6. monitoring

    We are continuing to monitor for any further issues.

    provider

  7. monitoring

    The issue has been resolved.

    provider

  8. resolved

    This incident has been resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-4e472dc11c

Is Amplitude still down?

No, this incident was resolved 2026-04-29 14:33 UTC. For Amplitude's live state, see https://down.guide/amplitude.

How long did it last?

6h 18m, from 2026-04-29 08:15 UTC to 2026-04-29 14:33 UTC, by the times Amplitude posted.

What was affected?

Amplitude named Evaluation API, Data Processing, Cohort Export, Amazon Web Services.

What caused it?

Amplitude hasn't published a root cause. If it does, it shows here.

Where does this come from?

Amplitude's official status page, https://amplitude.statuspage.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.