- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 30of 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-03-11 19:53 UTC and 2026-03-10 16:00 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
A migration to transition some Growth orgs to a new permission system, which is activated by a feature flag, did not operate correctly, resulting in the appearance of lost role assignments for users. This affected some Growth orgs that have project-based permissions. Removing the feature flag for these orgs reverted them to the old permission system, restoring all role assignments correctly.
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-544e61395d
Is Amplitude still down?
No, this incident was resolved 2026-03-10 16:00 UTC. For Amplitude's live state, see https://down.guide/amplitude.
How long did it last?
0m, from 2026-03-11 19:53 UTC to 2026-03-10 16:00 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.