← Back to ElevenLabs's check readings
We started checking ElevenLabs on August 22, 2026, which is 64 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when ElevenLabs reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what ElevenLabs's own status page declared. Below it, any public chatter we saw about ElevenLabs and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what ElevenLabs's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Unverified user reportsNo reports about ElevenLabs in the last 24 hours, which is not evidence that nothing is wrong.
ElevenLabs's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is ElevenLabs's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention ElevenLabs next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Their declared record
ElevenLabs's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Multiple US endpoints experiencing timeouts and latencyPartial outage
Oct 13, 2026, 9:21 AM UTC to Oct 13, 2026, 9:47 AM UTC (27 min)resolved
their latest update (Oct 13, 2026, 2:18 PM UTC): The incident is resolved. Error rates are back to normal, and stable service has been confirmed. We will publish a Root cause analysis once our review of the incident is complete.
Instant Voice Clone creation failuresMinor incident
Oct 13, 2026, 3:25 AM UTC to Oct 13, 2026, 3:25 AM UTC (0 min)resolved
their latest update (Oct 13, 2026, 3:25 AM UTC): Between 03:25 and 04:44 UTC on October 13, 2026, some requests to create an Instant Voice Clone failed with an error. This affected the Voice Lab in the app and the Voices API endpoint (POST /v1/voices/add), when background noise removal was turned on. Clones created without back…
Instant Voice Clone creation failuresMinor incident
Oct 13, 2026, 3:25 AM UTC to Oct 13, 2026, 3:25 AM UTC (0 min)resolved
their latest update (Oct 13, 2026, 3:25 AM UTC): Between 03:25 and 04:44 UTC on October 13, 2026, some requests to create an Instant Voice Clone failed with an error. This affected the Voice Lab in the app and the Voices API endpoint (POST /v1/voices/add), when background noise removal was turned on. Clones created without back…
TTS failures and increased latencyMinor incident
Oct 12, 2026, 4:30 PM UTC to Oct 12, 2026, 4:30 PM UTC (0 min)resolved
their latest update (Oct 12, 2026, 4:30 PM UTC): We experienced a transient error due to a heavy traffic spike. We will implementing improvements to be more resilient in the future.
Increased Dubbing Latency and Failure RatePartial outage
Oct 8, 2026, 4:09 PM UTC to Oct 8, 2026, 10:10 PM UTC (6h 1m)resolved
their latest update (Oct 8, 2026, 10:10 PM UTC): After several hours of monitoring, our metrics show that error rate has remained at its stable baseline since 17:55 UTC; the increase in Dubbing platform latency and failure rate is now resolved.
Increased Dubbing Latency and Failure RatePartial outage
Oct 8, 2026, 4:09 PM UTC to Oct 8, 2026, 10:10 PM UTC (6h 1m)resolved
their latest update (Oct 8, 2026, 10:10 PM UTC): After several hours of monitoring, our metrics show that error rate has remained at its stable baseline since 17:55 UTC; the increase in Dubbing platform latency and failure rate is now resolved.
Agent SIP Conversation DisruptionPartial outage
Oct 8, 2026, 3:19 PM UTC to Oct 8, 2026, 3:43 PM UTC (25 min)resolved
their latest update (Oct 8, 2026, 3:43 PM UTC): We have monitored error metrics and have confirmed that as of 15:15 UTC, we do not see continuing Agent SIP conversation failures. We will conduct an internal investigation and post a full Root Cause Analysis upon conclusion.
Agent SIP Conversation DisruptionPartial outage
Oct 8, 2026, 3:00 PM UTC to Oct 8, 2026, 3:43 PM UTC (44 min)resolved
their latest update (Oct 8, 2026, 3:43 PM UTC): We have monitored error metrics and have confirmed that as of 15:15 UTC, we do not see continuing Agent SIP conversation failures. We will conduct an internal investigation and post a full Root Cause Analysis upon conclusion.
Music 2.5 endpoints performance degradedMinor incident
Oct 8, 2026, 8:48 AM UTC to Oct 8, 2026, 8:58 AM UTC (10 min)resolved
their latest update (Oct 8, 2026, 8:58 AM UTC): Music had reduced availability after a latent infrastructure configuration issue was triggered by routine automated maintenance. This stopped new instances from starting and prevented automated recovery, and service was restored by manual intervention.
The service is now full…
EU Agents disruption in SIP callsPartial outage
Oct 6, 2026, 10:28 AM UTC to Oct 6, 2026, 12:51 PM UTC (2h 23m)resolved
their latest update (Oct 6, 2026, 12:51 PM UTC): The issue has been resolved. EU SIP services are operational and stable.
Showing the 10 most recent of 72 incidents ElevenLabs has declared in the history we hold.
These entries are ElevenLabs's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
ElevenLabs's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.