CHYP.ai · ORBIT // Cloudy_Day Security Suite

AI services

Operational ElevenLabs status

elevenlabs.io · Official status page (Statuspage-compatible JSON)

FROM ALL SOURCES

No sign of a widespread ElevenLabs problem right now; every source we read is quiet.

confidence: medium Vendor: operational · users: normal · routing: no data.

Vendor status vs. reality: Vendor status and outside signals roughly agree
The four clocks
ClockStartedRunning
Vendor clock when the vendor's open incident started47 h 25 min
Crowd clock when user reports began rising above normalnot seenn/a
Network clock when routing anomaly data first flagged itnot seenn/a
ORBIT clock when our checker first recorded the changenot seenn/a

Evidence

  • Official page: Operational (“All Systems Operational”). evidence confidence: high
  • Vendor stage: resolved on “Increased Latency and Errors”. evidence confidence: high
  • User reports are within normal range (0 in 15 min). evidence confidence: low

What we don't know: what is happening inside ElevenLabs' own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp. Routing data shows reachability, not whether the app works.

Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .

Cloudy_Day's take

Stage vs. health

The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: operational · users: normal · routing: no data. Vendor status and outside signals roughly agree.

Who depends on whom

ElevenLabs may run on Google Cloud (inferred). We don't map other services that depend on ElevenLabs. Dependency chains are where single points of failure hide.

Identity & trust lens

Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.

For users

Nothing points to a broad problem. If it's broken for you, try “Is it just me?” and check your own network first.

For security teams

Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on ElevenLabs or its upstream providers, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).

What to watch next

Any new vendor incident, a jump in user reports above baseline, or trouble at the providers ElevenLabs may depend on.

Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with ElevenLabs. No blame or attack claims without an official source. Generated .

INCIDENT REPLAY

Increased Latency and Errors

major resolved · started · resolved

11 updates

  1. investigating

    We’re seeing an increase in API errors and latency for multiple products. Agent conversations and dub creation are not impacted by this issue. We’re currently investigating and will post updates as soon as they become available.

  2. investigating

    We’re now seeing that some agent conversations are impacted by this issue. We’re still investigating this and will continue to post updates as they become available.

  3. investigating

    We are still investigating issues impacting services in the US residency. Products with confirmed impact: - TTS — partial elevated latency and some failing requests - STT — partial elevated latency and some failing requests - ElevenAgents — further updates pending - Dubbing — elevated failure rate - Music — partial elevated latency and failing requests - Creative — issues loading UI

  4. investigating

    We are still investigating issues impacting services in the US residency. Update on ElevenAgents: we can confirm that outbound telephony calls are operational, and quality within an active conversation is unaffected. Affected with degraded performance / partial failure: - some inbound websocket calls fail to connect - some inbound telephony calls (including Twilio and SIP) fail to connect - increased latency and elevated failure rates in agent get, update, create, delete operations - increased slowness in UI operations

  5. identified

    We’ve identified the cause of the ongoing US residency degradation and have begun stabilizing the underlying systems. Median response times have partially recovered, and some users may still experience intermittent errors and elevated latency across the following products: - TTS, STT & Music — partial elevated latency and some failing requests - Voices & API — elevated latency and intermittent errors when fetching or loading voices - Dubbing — elevated failure rate and delays (showing early signs of improvement) - Creative & Dashboard UI — slowness and issues loading pages - ElevenAgents — outbound telephony and active conversation quality remain operational; some inbound telephony (SIP/Twilio) and WebSocket calls may fail to connect, and agent management/UI operations remain slow We are actively working to restore full functionality, and rolling out fixes to permanently reduce pressure

  6. identified

    We’re still working to fully restore functionality and address the root cause for this issue. We will continue posting updates about this as they become available.

  7. monitoring

    After further observation, latency is back to normal levels and we’re seeing a reduction in error rates across all products. We’re currently still monitoring to confirm resolution.

  8. resolved

    Systems are now operational across all products. We will post a root cause analysis after an extensive review.

  9. investigating

    We have seen an increase in agent conversation failures due to a reoccurrence of this issue. We are investigating and will post further updates as they become available.

  10. monitoring

    We’ve applied a fix for the agent conversation initiation failures and we’re currently monitoring to confirm full resolution. These initiation errors stopped at 15:20 UTC. These failures had no impact on other products.

  11. resolved

    After further monitoring, we can confirm that the root cause of the conversation initiation failures has been resolved. We will post a root cause analysis for the incident after further review.

Official incident page ↗

Community comments (0)

Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.

No approved comments yet.

How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.

Where to next