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 started30 days
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 “Website Slowness and API Request Latency”. 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

Website Slowness and API Request Latency

major resolved · started · resolved

11 updates

  1. investigating

    We are currently investigating an issue with website and API requests and are working to identify the root cause as quickly as possible. We will provide an update as soon as more information becomes available. TTS API request and Agents conversations are working. There may be issues related to API services that affect conversation initiation.

  2. identified

    We have identified an underlying issue with our cloud provider that is impacting service availability.

  3. identified

    We have isolated the components responsible for performance degradation and are attempting to implement workarounds to bypass the affected cloud provider services.

  4. identified

    Our engineering team is continuing to investigate issues with the cloud provider components. Multiple engineering teams and leadership is involved in the efforts. We'll continue monitoring closely and provide timely updates as the situation evolves.

  5. identified

    Our engineering team is actively exploring multiple remediation paths in parallel while working to isolate the root cause. We have escalated this issue both to our infrastructure provider and to internal leadership to ensure it receives the highest level of attention and resources. A definitive root cause has not yet been identified, but we are making iterative changes and closely monitoring their impact. We will continue to provide updates as our investigation progresses.

  6. identified

    Our team continues to actively investigate the degraded performance affecting services. We are working through several lines of investigation in parallel and methodically testing potential contributing factors. This remains escalated with our infrastructure provider and internal leadership, with additional engineering resources dedicated to this effort. While a definitive root cause has not yet been identified, each step is helping us build a clearer picture of the underlying issue. We understand the impact this is having and are treating this with the highest priority. We will provide another update in 15-20 minutes.

  7. identified

    We are continuing to investigate all possible root causes and eliminate potential causes. Additionally we are clarifying affected products below. **What's affected:** - **Agents Platform** - degraded performance due to issues around conversation initiation. Conversations that do start function as normal thus API customers should retry failed initiation conversations. - **Website** - intermittent slowness **What's working normally:** - Text-to-Speech (TTS) API - Speech-to-Text (STT) API - Dubbing API Our engineering team remains fully engaged and is continuing to work through active lines of investigation alongside our infrastructure provider. We are iterating on potential mitigations and monitoring the results closely. We will continue to provide updates every 15-20 minutes.

  8. identified

    Our team remains fully engaged and continues to work through active lines of investigation. All previously noted affected and operational components remain in the same state. We will provide another update in 15-20 minutes

  9. monitoring

    We have implemented changes to the affected services that have resulted in signs of recovery and improved performance. We are closely monitoring to confirm stability and will provide an another update in 15–20 minutes.

  10. monitoring

    Affected services continue to show sustained improvement following the changes implemented earlier. We are continuing to monitor key metrics and will confirm full resolution once we are satisfied with stability across baseline error rates. Next update in 15-20 minutes.

  11. resolved

    As of 7:45 PM UTC, all affected services have fully recovered and are operating normally. **Agents Platform** and **Audio Platform (Website)** have returned to full health. Text-to-Speech (TTS), Speech-to-Text (STT), and Dubbing APIs were unaffected throughout the incident. The root cause has been identified and remediated. We will be conducting a thorough post-incident review and will share further details in a follow-up report. We apologize for the disruption and appreciate your patience throughout this incident. If you are still experiencing any issues, please don't hesitate to contact our support team.

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