Intermittent Sign in issue
ElevenLabs reports an intermittent sign-in issue that affects password-based sign-ins. Other sign-in methods work as expected. ElevenLabs has identified the cause and is working on a fix.
State
Identified
Started
Ongoing for
1 h 17 min
Worst impact
Notice
Timeline
2 updatesInvestigating
36 min 47%
Identified
41 min 53%
Updates
Times in UTCAs posted by ElevenLabs
We have identified the cause of the sign-in errors and are working on a fix.
We are currently investigating an issue affecting password-based sign-ins. Other sign-in methods are working as expected.
ElevenLabs in the last 90 days
Full historyIncidents in 90 days
2
Days with an incident
2
Median duration
1 h 42 min
This incident
25% shorter than the median
Other ElevenLabs incidents
All incidentsFollow 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