Outage recap · ElevenLabs

ElevenLabs outage — October 8, 2026

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

Music 2.5 endpoints performance degraded

minor
Started
Oct 8, 4:48 AM EDT
Resolved
—
Duration
end time not published

What our checks recorded

We checked ElevenLabs 24 times in the two hours after ElevenLabs's start time (it published no end time), once every five minutes. Every one of them reached ElevenLabs'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 157 ms, against 142 ms over the 24 hours before. ElevenLabs's feed showed the incident by Oct 8, 4:55 AM EDT (we read it every five minutes).

Updates are ElevenLabs's own words from its status page (status: resolved); we never add an inferred cause.

Agent SIP Conversation Disruption

major
Started
Oct 8, 11:19 AM EDT
Resolved
—
Duration
end time not published

What our checks recorded

We checked ElevenLabs 24 times in the two hours after ElevenLabs's start time (it published no end time), once every five minutes. Every one of them reached ElevenLabs'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 161 ms, against 141 ms over the 24 hours before. ElevenLabs's feed showed the incident by Oct 8, 11:20 AM EDT (we read it every five minutes).

Updates are ElevenLabs's own words from its status page (status: resolved); we never add an inferred cause.

Increased Dubbing Latency and Failure Rate

major
Started
Oct 8, 12:09 PM EDT
Resolved
—
Duration
end time not published

What our checks recorded

We checked ElevenLabs 24 times in the two hours after ElevenLabs's start time (it published no end time), once every five minutes. Every one of them reached ElevenLabs'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 170 ms, against 141 ms over the 24 hours before. ElevenLabs's feed showed the incident by Oct 8, 12:15 PM EDT (we read it every five minutes).

Updates are ElevenLabs's own words from its status page (status: resolved); we never add an inferred cause.

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