- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 20of 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 2h 49m it lasted.
Anything that failed between 2026-10-26 15:23 UTC and 2026-10-26 18:12 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 4
- investigating
We are currently experiencing an issue with Speaker Tagging and Diarization Our team is aware and working on a solution as soon as possible.
provider
- identified
Our team has identified the issue and is working to fully restore services and processing speaker taggings
provider
- monitoring
Our engineering team has identified the issue and applied a fix We have resumed operations but will continue to monitor the situation.
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-3819fc8a89
Is Otter.ai still down?
No, this incident was resolved 2026-10-26 18:12 UTC. For Otter.ai's live state, see https://down.guide/otter.
How long did it last?
2h 49m, from 2026-10-26 15:23 UTC to 2026-10-26 18:12 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.