Skip to main content
Amplitude

Ingestion lag in our batch pipeline

Degraded Lasted 31m · started · Amplitude's page

Level
confirmed
Worst impact
Degraded
Components
Data Processing, Data Export
Down Index
30of 100

What to do

  • Check whether you use Amplitude Data Processing, Data Export. 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 31m it lasted.

    Anything that failed between 2026-05-05 19:13 UTC and 2026-05-05 19:44 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 3

  1. investigating

    We are investigating an incident in our batch ingestion pipeline that is causing ingestion issues in 1 partition. No data is lost and we are actively working on remediating this delay.

    provider

  2. monitoring

    A fix has been implemented and we are monitoring the results.

    provider

  3. 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-470cd9a74f

Is Amplitude still down?

No, this incident was resolved 2026-05-05 19:44 UTC. For Amplitude's live state, see https://down.guide/amplitude.

How long did it last?

31m, from 2026-05-05 19:13 UTC to 2026-05-05 19:44 UTC, by the times Amplitude posted.

What was affected?

Amplitude named Data Processing, Data Export.

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.