A
Outage recap · AssemblyAI

AssemblyAI outage — October 6, 2026

On October 6, 2026, AssemblyAI had 3 reported incidents on AssemblyAI's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

Rejected Sessions on US Endpoint for Universal-3.6 Pro Realtime Model

minor
Started
Oct 6, 6:30 AM EDT
Resolved
Oct 6, 6:30 AM EDT
Duration
—

AssemblyAI's updates (1)

  1. resolved · Oct 6, 6:30 AM EDT

    From 10:30a - 12:30a UTC users experienced rejected connections when connecting to our Realtime Universal-3.6 Pro model on our US endpoint. Users received a 3005 Session Cancelled error message on connection. This issue has been resolved and the Realtime US endpoint for Universal-3.6 Pro is functioning normally. The EU Realtime endpoint was not affected.

What our checks recorded

We have no checks recorded from AssemblyAI's start time to its resolution.

Updates are AssemblyAI's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗

Increased Processing Times and Errors on US Endpoint for Universal-3.5 Pro Async model

major
Started
Oct 6, 10:00 AM EDT
Resolved
Oct 6, 10:25 AM EDT
Duration
25 min

AssemblyAI's updates (4)

  1. investigating · Oct 6, 10:00 AM EDT

    We have identified an issue affecting asynchronous transcription requests using Universal-3.5 Pro on our US endpoint. Beginning at 1:35p UTC, requests have increased processing time and some are resulting in errors. Our team is working to restore normal processing. Our EU endpoint is not affected. We will continue to provide updates as more information becomes available.

  2. identified · Oct 6, 10:10 AM EDT

    We have identified the issue and a fix has been released. We will provide further updates as soon as we can.

  3. monitoring · Oct 6, 10:13 AM EDT

    A fix has been implemented. We are seeing processing times return to the normal ranges and are continuing to monitor the results.

  4. resolved · Oct 6, 10:25 AM EDT

    This incident has been resolved. Between approximately 1:35p and 2:20p UTC, async transcription requests using Universal-3.5 Pro on our US endpoint took longer than usual to complete, and some requests failed. Processing times have returned to normal ranges and any requests that failed during this window can be safely resubmitted.

What our checks recorded

We checked AssemblyAI 6 times from AssemblyAI's start time to its resolution, once every five minutes. Every one of them reached AssemblyAI's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 115 ms, against 109 ms over the 24 hours before. AssemblyAI posted the incident at Oct 6, 10:00 AM EDT.

Updates are AssemblyAI's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗

Increased Processing Times and Errors on EU Endpoint for Universal-3 Pro Async model

minor
Started
Oct 6, 11:44 AM EDT
Resolved
Oct 6, 12:03 PM EDT
Duration
19 min

AssemblyAI's updates (4)

  1. investigating · Oct 6, 11:44 AM EDT

    We are experiencing an issue affecting asynchronous transcription requests using Universal-3 Pro on our EU endpoint. Beginning at 15:05 UTC, requests have increased processing time and some are resulting in errors. Our team is working to restore normal processing. Our US endpoint is not affected. Our team is actively investigating this issue.

  2. identified · Oct 6, 11:44 AM EDT

    The issue has been identified and a fix is being implemented.

  3. monitoring · Oct 6, 11:46 AM EDT

    A fix has been implemented. We are seeing processing times return to the normal ranges and are continuing to monitor the results.

  4. resolved · Oct 6, 12:03 PM EDT

    This incident has been resolved. Between approximately 15:05 and 15:45 UTC, async transcription requests using Universal-3 Pro on our EU endpoint took longer than usual to complete, and some requests failed. Processing times have returned to normal ranges and any requests that failed during this window can be safely resubmitted.

What our checks recorded

We checked AssemblyAI 4 times from AssemblyAI's start time to its resolution, once every five minutes. Every one of them reached AssemblyAI's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 94 ms, against 110 ms over the 24 hours before. AssemblyAI posted the incident at Oct 6, 11:44 AM EDT.

Updates are AssemblyAI's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗

AIDownCheck is not affiliated with AssemblyAI. This recap summarizes incidents published on AssemblyAI's official status page.