Skip to main content
Otter.ai logo

Is Otter.ai Down?

No — Otter.ai is up

Reachable from all 8 checked regions

Average response time: 1226ms

Last checked · checks run every 6 hours

Official status page: https://status.otter.ai

Otter.ai uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
1255ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 21 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

21-day clean streak
Sep 14: no data
Sep 15: no data
Sep 16: no data
Sep 17: no data
Sep 18: no data
Sep 19: no data
Sep 20: no data
Sep 21: no data
Sep 22: no data
Sep 23: 100.00% uptime, 16 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 32 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 31 checks
Sep 30: 100.00% uptime, 28 checks
Oct 1: 100.00% uptime, 32 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 31 checks
Sep 14 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

jnb
2718ms
DNS 316ms TCP 293ms TLS 588ms TTFB 1545ms
lax
446ms
DNS 115ms TCP 30ms TLS 62ms TTFB 353ms
lhr
1155ms
DNS 43ms TCP 131ms TLS 264ms TTFB 761ms
nrt
1209ms
DNS 108ms TCP 129ms TLS 260ms TTFB 690ms
ord
656ms
DNS 27ms TCP 68ms TLS 138ms TTFB 381ms
sin
1522ms
DNS 11ms TCP 182ms TLS 367ms TTFB 791ms
sjc
369ms
DNS 133ms TCP 22ms TLS 47ms TTFB 281ms
syd
1734ms
DNS 209ms TCP 178ms TLS 358ms TTFB 1020ms

What Otter.ai does

Otter.ai transcribes meetings and conversations and writes summaries. Its Otter Notetaker, formerly OtterPilot, joins Zoom, Google Meet and Microsoft Teams calls from a connected calendar and records them automatically. Students, sales teams and journalists use it as the record of what was said, so an outage can mean a meeting with no notes at all.

What an outage looks like

The notetaker does not join a scheduled meeting, or joins and records nothing. Live notes stay blank while people are speaking. Recordings upload but transcripts never appear. Imported audio files sit processing. Sign-in with Google or Microsoft fails. Otter Chat does not answer questions about past meetings, and the public API returns errors to connected tools.

What to do about it

Check status.otter.ai, which lists Speech Processing, Otter Live Notes, Otter Pilot, Web Recording, File Importing, Otter Chat, Payments, the Public API and separate Google and Microsoft rows. If Speech Processing is degraded, start a backup recording now, in the meeting platform or on a phone, because a missed meeting cannot be transcribed later.

Is it down for everyone, or just you?

If this page says Otter.ai is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Otter.ai outage FAQ

Why did Otter not join my meeting?
The notetaker relies on your connected Google or Microsoft calendar and on the Otter Pilot component, which are separate rows on the status page. If either is degraded, the notetaker can miss meetings it would normally join. Check the meeting is still on the connected calendar, then add Otter manually. For an important call, record it in Zoom, Meet or Teams as well.
Will my recording be transcribed after the outage?
If the audio was captured, usually yes. Speech Processing and File Importing are reported separately from recording, so a recording that uploaded during an incident can be processed once transcription recovers. Audio that was never captured cannot be recovered, which is why a backup recording matters more than waiting.
Is Otter down or is it Zoom?
Check both. If Zoom, Meet or Teams is having trouble, the notetaker cannot join or hear the call even when Otter is healthy. If the meeting platform works and Otter rows are degraded, the problem is Otter. People in the meeting hearing each other fine is a good sign the meeting platform is not the cause.
Why can I not sign in to Otter?
Sign-in is reported separately for Email and Password, Google and Microsoft. If only the Google or Microsoft row is degraded, another sign-in method may still work if your account has one. If every sign-in row is healthy and you still cannot log in, the problem is more likely your account or browser.
Does an Otter outage affect notes I already have?
Existing transcripts are stored and are not deleted by an incident, but you may not be able to open them while the website or app is degraded. Otter Chat, which answers questions across past meetings, is its own component and can fail while viewing transcripts works.

How we measure this

  • We request Otter.ai's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Otter.ai publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Otter.ai goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required