- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 22of 100
What to do
Check whether your product depends on Otter.ai. 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 8h 39m it lasted.
Anything that failed between 2026-03-24 19:50 UTC and 2026-03-25 04:30 UTC may need a replay.Subscribe to Otter.ai's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=otter works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Otter.ai 3
- identified
Our team has identified the issue with processing some conversations. We are currently working on a fix and will deploy this as soon as possible.
provider
- monitoring
New conversations will process as normal. Conversations previously affected by this issue will be processed as our team works through the queue. Check back later if your conversation is still showing a processing issue. All conversations will be processed by our team.
provider
- resolved
Otter systems have been fully restored.
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-cdf136445d
Is Otter.ai still down?
No, this incident was resolved 2026-03-25 04:30 UTC. For Otter.ai's live state, see https://down.guide/otter.
How long did it last?
8h 39m, from 2026-03-24 19:50 UTC to 2026-03-25 04:30 UTC, by the times Otter.ai posted.
What caused it?
Otter.ai hasn't published a root cause. If it does, it shows here.
Where does this come from?
Otter.ai's official status page, https://status.otter.ai, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.