Where does this status come from?

From ElevenLabs's own status page API at https://status.elevenlabs.io. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are ElevenLabs's words.

How can my agent or app check ElevenLabs status?

Fetch https://upbutler.com/status/elevenlabs/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"elevenlabs"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or ElevenLabs's?

Add "elevenlabs" to the dependencies of your UpButler workspace. When one of your monitors fails while ElevenLabs has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Is ElevenLabs down?

Right now

No. ElevenLabs is operational.

No incidents reported.

Read from status.elevenlabs.io 26 s ago · every 120s

For agents

proceed

Proceed.

GET upbutler.com/status/elevenlabs/status.agent.json

MCP: upstream_status {"service":"elevenlabs"}

Text to speech, voice agents and dubbing.

What ElevenLabs reports

Operational

Taken as is from ElevenLabs's own status page API. Incident titles and component names below are theirs.

Open status.elevenlabs.io

UpButler's independent probe

There is no keyless endpoint of ElevenLabs that says anything useful, so UpButler does not probe it. To check your own ElevenLabs account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

ElevenLabs components

11 operational

Text to SpeechOperational
Speech to TextOperational
OtherOperational
ConversationsOperational
TelephonyOperational
RAGOperational
QualityOperational
Other API endpointsOperational
UIOperational
IntegrationsOperational
ElevenCreativeOperational

ElevenLabs incidents, last 90 days

8 finished incidents seen since UpButler started tracking on 2026-10-10, 5 of them rated major or critical by ElevenLabs. A typical one lasted 1 h 34 min; the longest 6 h 1 min.

Started (UTC)	Incident	Impact	Lasted
2026-10-08 16:09	Increased Dubbing Latency and Failure Rate	major	6 h 1 min
2026-10-08 15:19	Agent SIP Conversation Disruption	major	25 min
2026-10-08 08:48	Music 2.5 endpoints performance degraded	minor	10 min
2026-10-06 10:28	EU Agents disruption in SIP calls	major	2 h 23 min
2026-10-06 09:09	increase in latency	minor	3 h 5 min
2026-09-29 18:49	Agents, STT, and Creative Platform: Increased Latency, Conversation Failures, and STT Failures	major	1 h 34 min
2026-09-28 15:42	Increased latency for Speech to Text API requests	minor	1 h 12 min
2026-09-28 13:57	Agents - EU Residency	major	42 min

Tell your outage from ElevenLabs's

Declare that your project depends on ElevenLabs. When one of your monitors fails while ElevenLabs has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - elevenlabs

Ask before you retry

curl -s https://upbutler.com/status/elevenlabs/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "elevenlabs",
  "verdict": "proceed",
  "status": "operational",
  "reason": "No incidents reported",
  "retryAfterSec": null,
  "incident": null,
  "probe": null
}

Questions

Is ElevenLabs down right now?: No. As of 2026-10-10 05:14 UTC, ElevenLabs is operational. This page reads the status again every 2 minutes.
Where does this status come from?: From ElevenLabs's own status page API at https://status.elevenlabs.io. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are ElevenLabs's words.
How can my agent or app check ElevenLabs status?: Fetch https://upbutler.com/status/elevenlabs/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"elevenlabs"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or ElevenLabs's?: Add "elevenlabs" to the dependencies of your UpButler workspace. When one of your monitors fails while ElevenLabs has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

More in ai models and tooling

UpButler is not affiliated with ElevenLabs. Status and incident text belong to ElevenLabs and are read from their public status source; the probe result is UpButler's own measurement.