Degraded performance of Voice Library voices
This incident has been resolved. For a full timeline and Root Cause Analysis, see the US incident:
The latest update from ElevenLabs.
State
Resolved
Started
Lasted
2 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
2 min 100%
Updates
Times in UTCAs posted by ElevenLabs
This incident has been resolved. For a full timeline and Root Cause Analysis, see the US incident:
Due to the Incident in the Global residency, some voice library voices in the Isolated environments experienced degraded performance. All products that used voices from the voice library were affected.
ElevenLabs in the last 90 days
Full historyIncidents in 90 days
5
Days with an incident
5
Median duration
1 h 54 min
This incident
98% shorter than the median
Other ElevenLabs incidents
All incidentsElevenLabs·Increased Latency and Errors
ElevenLabs reported elevated latency and errors across TTS, STT, Music, Voices, API, Dubbing, the Creative and Dashboard UI, and ElevenAgents, including some inbound telephony and WebSocket call failures. ElevenLabs stated that the incident is resolved, and it lasted about 5 hours and 28 minutes.
ElevenLabs·Scribe v3 Live outage
Scribe v3 Live was unavailable. The issue affected the Scribe v3 Live model only, with no other components listed. ElevenLabs reported an outage from 00:50 to 01:11 BST, then monitored the fix. ElevenLabs resolved the outage, which lasted about 21 minutes.
ElevenLabs·Intermittent Sign in issue
ElevenLabs reported an intermittent sign-in issue that affected password-based sign-ins. Other sign-in methods worked as expected. ElevenLabs resolved the issue on 4 November 2026. The incident lasted 151 minutes.
ElevenLabs·ElevenCreative - Image & Video - Degraded performance
The issue affecting image and video generation, Flows, and MCP in ElevenCreative has been resolved. Generations are completing normally.
Follow ElevenLabs
Your coding agent knows when ElevenLabs is down, and tells you when a failure is theirs, not yours. You can also get ElevenLabs incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "elevenlabs" and tell me if ElevenLabs has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=elevenlabs/feed subscribe https://outages.live/feed.xml?providers=elevenlabsFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane