- Level
- confirmed
- Worst impact
- Degraded
- Components
- Data Processing
- Down Index
- 33of 100
What to do
Check whether you use Amplitude Data Processing. 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 3h 15m it lasted.
Anything that failed between 2026-07-05 15:56 UTC and 2026-07-05 19:11 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
- monitoring
Our data processing systems are delayed. This incident started at 6:30 PDT. Current status: Our ingestion systems are working as expected and no data is lost. We've identified the issue and the data processing system is catching up now. ETA to fully resolved is ~2hours (11 PDT)
provider
- monitoring
Realtime data is fully caught up and available all features within Amplitude should have data fully available. Some export data from the past hour may still be delayed.
provider
- resolved
All systems are caught up and functioning normally.
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-4178074d47
Is Amplitude still down?
No, this incident was resolved 2026-07-05 19:11 UTC. For Amplitude's live state, see https://down.guide/amplitude.
How long did it last?
3h 15m, from 2026-07-05 15:56 UTC to 2026-07-05 19:11 UTC, by the times Amplitude posted.
What was affected?
Amplitude named Data Processing.
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.