Otter.ai

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-09-14 22:58 UTC

   Our team has identified the issue and is working to fully restore services. Users should now be able to log in and use Otter but may experience some slowness.

2. resolved 2026-09-14 23:17 UTC

   Otter systems have been fully restored.

Excerpts are shortened. Read the full incident on Otter.ai's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-07 22:51 UTC

   Some customers may experience issues with Otter joining Microsoft Teams meetings. We’re investigating and will share updates here.

2. monitoring 2026-09-08 01:58 UTC

   We identified an issue affecting Otter joining Microsoft Teams meetings and deployed a fix. Join success has improved, but we are continuing to monitor.

3. resolved 2026-09-08 16:55 UTC

   The issue affecting Otter joining Microsoft Teams meetings has been resolved. We deployed a fix and have confirmed that Otter can again join Teams meetings successfully.

Excerpts are shortened. Read the full incident on Otter.ai's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-28 19:09 UTC

   We are currently experiencing an issue with email delivery, including notification emails, invite emails, password reset emails, payment emails and reminders, as well as the bulk export feature. Our team is aware of the issue and is working to resolve it as soon as possible.

2. resolved 2026-08-28 20:18 UTC

   Otter systems have been fully restored.

Excerpts are shortened. Read the full incident on Otter.ai's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-27 19:01 UTC

   We are currently experiencing a delay in Summary and Speaker tagging. Otter Chat is also impacted as a result. Our team is aware and working on a solution as soon as possible.

2. investigating 2026-08-27 20:06 UTC

   We are currently experiencing a delay in Summary and Speaker tagging. Otter Chat is also impacted as a result. Our team is aware and working on a solution as soon as possible.

3. resolved 2026-08-27 21:24 UTC

   Otter systems have been fully restored.

4. resolved 2026-08-27 21:24 UTC

   Otter systems have been fully restored.

Excerpts are shortened. Read the full incident on Otter.ai's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-04 17:31 UTC

   We are currently experiencing a delay in generating speech outlines and summaries. Our team is aware and working on a solution as soon as possible.

2. monitoring 2026-06-04 22:01 UTC

   Monitoring / Recovery in Progress A solution has been implemented to resolve the recent delays. We are currently processing the delayed speech outlines and summaries, and normal delivery speeds will be fully restored shortly.

3. resolved 2026-06-05 06:52 UTC

   The recent delay in generating speech outlines and summaries has been completely resolved. All pending summaries have been successfully processed and are now accessible. Normal service speeds have fully resumed.

Excerpts are shortened. Read the full incident on Otter.ai's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-02 14:00 UTC

   We are currently experiencing an outage affecting Notetaker's ability to join Google Meet meetings. Our team is aware of the issue and is working on a solution as soon as possible.

2. monitoring 2026-06-02 23:40 UTC

   Our engineering team has identified the issue. We have resumed operations but will continue to monitor the situation.

3. resolved 2026-06-03 17:17 UTC

   Otter systems have been fully restored.

Excerpts are shortened. Read the full incident on Otter.ai's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-22 15:33 UTC

   We are currently experiencing an outage with Otter services. Our team is aware and working on a solution as soon as possible.

2. identified 2026-05-22 16:02 UTC

   Our team has identified the issue and is working to fully restore services. Users should now be able to log in and use Otter but some lingering issues with Otter Notetaker joining your calls may persist while we continue working to resolve the issue.

3. monitoring 2026-05-22 18:09 UTC

   Our engineering team has identified and addressed the issue. We have resumed operations but will continue to monitor the situation.

4. resolved 2026-05-27 20:02 UTC

   Otter systems have been fully restored.

Excerpts are shortened. Read the full incident on Otter.ai's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-12 18:05 UTC

   We are currently experiencing an outage with Otter services. Our team is aware and working on a solution as soon as possible.

2. identified 2026-05-12 19:15 UTC

   Our team has identified the issue and is working to fully restore services.

3. monitoring 2026-05-12 20:01 UTC

   ]We have resumed operations but will continue to monitor the situation.

4. resolved 2026-05-13 18:32 UTC

   Otter systems have been fully restored.

Excerpts are shortened. Read the full incident on Otter.ai's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-05-08 17:25 UTC

   Our team has identified the issue causing delays in imports processing and summaries processing. We've applied a fix and are working towards resolving any backed up processing files.

2. resolved 2026-05-11 12:10 UTC

   Otter systems have been fully restored.

Excerpts are shortened. Read the full incident on Otter.ai's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-04 19:41 UTC

   We are currently experiencing an issue with calendar updates not being recognized/delayed in Otter. Any modifications to calendar; including meeting creation, deletion or changing the start time, will be delayed. You may also see delays or Otter joining at incorrect times if the...

2. resolved 2026-05-04 19:59 UTC

   Otter systems have been fully restored.

Excerpts are shortened. Read the full incident on Otter.ai's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-03-21 00:07 UTC

   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.

2. monitoring 2026-03-24 21:19 UTC

   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.

3. resolved 2026-03-25 04:30 UTC

   Otter systems have been fully restored.

Excerpts are shortened. Read the full incident on Otter.ai's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-24 19:49 UTC

   Users not in a workspace (such as mobile users) may be currently experiencing an issue starting a manual recording. Our team is aware of the issue and is working on a solution as soon as possible. In the meantime, we recommend recording the audio separately and [importing it...

2. identified 2026-03-24 21:16 UTC

   Our team has identified the root cause and is working to fix the issue.

3. resolved 2026-03-25 04:30 UTC

   Otter systems have been fully restored.

Excerpts are shortened. Read the full incident on Otter.ai's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-03-13 16:00 UTC

   Our engineering team has identified the issue that may be causing speech processing delays. Speeches will be processed, but may take longer than usual. We appreciate your patience as we work through processing speeches.

2. resolved 2026-03-16 12:18 UTC

   Otter systems have been fully restored.

Excerpts are shortened. Read the full incident on Otter.ai's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-03-13 18:14 UTC

   Otter experienced a brief outage, but the site should be loading again as intended. Our engineers have identified the issue. We have resumed operations but will continue to monitor the situation.

2. resolved 2026-03-13 19:10 UTC

   Otter systems have been fully restored.

Excerpts are shortened. Read the full incident on Otter.ai's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-12 17:00 UTC

   We are currently experiencing a delay with processing conversations. Recordings are queued and will be processed in due time, but may be delayed in transcribing the recording itself.

2. resolved 2026-03-13 01:03 UTC

   Otter systems have been fully restored.

Excerpts are shortened. Read the full incident on Otter.ai's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-09 16:59 UTC

   We are currently experiencing an issue with Otter not joining some Zoom meetings. Our team is aware and working on a solution as soon as possible.

2. monitoring 2026-03-09 19:49 UTC

   Our engineering team has identified the issue and applied a fix to having Otter join Zoom meetings. The issue is related to issues due to Zoom. We're working with Zoom to resolve the issue fully as soon as possible. We have resumed operations but will continue to monitor the...

3. resolved 2026-03-12 10:55 UTC

   Otter systems have been fully restored.

Excerpts are shortened. Read the full incident on Otter.ai's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-09 00:25 UTC

   We are currently experiencing delays in speaker tagging. Our team is aware and working on a solution as soon as possible.

2. investigating 2026-03-09 04:11 UTC

   We are currently experiencing an outage with Otter services. Our team is aware and working on a solution as soon as possible.

3. identified 2026-03-09 04:14 UTC

   Our team has identified the issue has deployed a fix to reduce the delays in speaker tagging for recorded speeches.

4. resolved 2026-03-09 05:25 UTC

   Otter systems have been fully restored.

Excerpts are shortened. Read the full incident on Otter.ai's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-02-23 13:00 UTC

   We are currently experiencing an issue with our outbound emails. This may cause delays in emails going out from the Otter System which includes, but not limited to: -Email invitations (Users will still be able to receive and accept them in app) -Bulk Export Links -Meeting...

2. identified 2026-02-23 20:16 UTC

   Our team has identified the issue and is working to fully restore our outbound emails once more. We've found this is due to an upstream issue and are working with our service providers to resolve the issue as soon as possible. -------------- This may cause delays in emails going...

3. resolved 2026-02-23 22:54 UTC

   Otter systems have been fully restored.

Excerpts are shortened. Read the full incident on Otter.ai's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-21 20:00 UTC

   We are currently experiencing an outage with Otter services. Our team is aware and working on a solution as soon as possible.

2. monitoring 2026-01-21 20:23 UTC

   Our engineering team has identified the issue. We have resumed operations but will continue to monitor the situation.

3. resolved 2026-01-21 21:22 UTC

   Otter systems have been fully restored.

Excerpts are shortened. Read the full incident on Otter.ai's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-21 16:01 UTC

   We are currently experiencing an outage with Otter services. Our team is aware and working on a solution as soon as possible.

2. monitoring 2026-01-21 16:13 UTC

   Our engineering team has identified the issue. We have resumed operations but will continue to monitor the situation.

3. monitoring 2026-01-21 16:30 UTC

   Our engineering team has identified the issue. We have resumed operations but will continue to monitor the situation.

4. identified 2026-01-21 17:04 UTC

   Our team has identified the issue and is working to fully restore services. Users should now be able to log in and use Otter but may experience some slowness.

5. monitoring 2026-01-21 17:16 UTC

   Our engineering team has identified the issue. We have resumed operations but will continue to monitor the situation.

6. resolved 2026-01-21 19:00 UTC

   Otter systems have been fully restored.

Excerpts are shortened. Read the full incident on Otter.ai's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-20 17:16 UTC

   We are currently experiencing an outage with Otter services. Our team is aware and working on a solution as soon as possible.

2. monitoring 2026-01-20 17:26 UTC

   Our engineering team has identified the issue. We have resumed operations but will continue to monitor the situation.

3. identified 2026-01-20 18:04 UTC

   Our team has identified the issue and is working to fully restore services. Users should now be able to log in and use Otter but may experience some slowness.

4. monitoring 2026-01-20 18:14 UTC

   Our engineering team has identified the issue. We have resumed operations but will continue to monitor the situation.

5. resolved 2026-01-20 18:30 UTC

   Otter systems have been fully restored.

Excerpts are shortened. Read the full incident on Otter.ai's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-14 17:07 UTC

   We are currently experiencing an outage with Otter services. Our team is aware and working on a solution as soon as possible.

2. identified 2026-01-14 17:18 UTC

   Our team has identified the issue and is working to fully restore services. Users should now be able to log in and use Otter but may experience some slowness.

3. monitoring 2026-01-14 18:17 UTC

   Our engineering team has identified the issue. We have resumed operations but will continue to monitor the situation.

4. resolved 2026-01-14 18:50 UTC

   Otter systems have been fully restored.

Excerpts are shortened. Read the full incident on Otter.ai's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-01-07 01:13 UTC

   Our team has identified the issue and is made a fix which must be reviewed by the Apple iOS store. Version 3.90.1 will contain the fix and we'll be releasing it as soon as Apple approves the update. We apologize for any inconvenience.

2. monitoring 2026-01-07 22:01 UTC

   We have deployed a fix to log in via SSO on the iOS app. Please update your app to version 3.90.1 and try logging in with SSO once more. We apologize for any inconvenience.

3. resolved 2026-01-08 16:56 UTC

   Otter systems have been fully restored.

Excerpts are shortened. Read the full incident on Otter.ai's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-11 21:10 UTC

   We are currently experiencing a delay with real-time transcription. All recordings should still be occurring and will be processed in full, this only affects the live transcription. Our team is aware and working on a solution as soon as possible.

2. monitoring 2025-12-11 21:36 UTC

   Our engineering team has identified the issue. We have resumed operations but will continue to monitor the situation.

3. resolved 2025-12-12 01:03 UTC

   Otter systems have been fully restored.

Excerpts are shortened. Read the full incident on Otter.ai's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-12-11 19:39 UTC

   We are currently experiencing an outage with Otter services. Our team is aware and working on a solution as soon as possible.

2. monitoring 2025-12-11 19:54 UTC

   Our engineering team has identified the issue. We have resumed operations but will continue to monitor the situation.

3. resolved 2025-12-11 20:56 UTC

   Otter systems have been fully restored.

Excerpts are shortened. Read the full incident on Otter.ai's status page.