- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 20of 100
What to do
Check whether your product depends on Amplitude. 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 0m it lasted.
Anything that failed between 2026-09-11 00:19 UTC and 2026-09-09 20:32 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 1
- resolved
Some S3 export files delivered between September 9 at 20:32 UTC and September 10 at 04:01 UTC were missing the bucket-owner-full-control permission, which prevented affected customers from reading them. The issue is resolved. Exports moving forward and outside this timeframe are not impacted. No data was lost. For impacted files in the affected timeframe, set your bucket's Object Ownership to Bucket owner enforced (disable ACLs), if compatible with your bucket access requirements. If you have questions or continue to experience issues, please submit a support request.
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-19d2dbda9b
Is Amplitude still down?
No, this incident was resolved 2026-09-09 20:32 UTC. For Amplitude's live state, see https://down.guide/amplitude.
How long did it last?
0m, from 2026-09-11 00:19 UTC to 2026-09-09 20:32 UTC, by the times Amplitude posted.
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.