Cartesia had 49 outages in the last 2 years totaling 30h 46m of downtime — averaging 2 incidents per month.
There were 49 Cartesia outages since June 9, 2025 totaling 30h 46m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are investigating the issue
A fix has been implemented and we are monitoring.
This incident has been resolved.
We are experiencing infrastructure issue with one of our infra provider, mainly impacting our voice clone feature in the US.
We are continuing to work on a fix for this issue.
We have mitigated the issue on our end and are continuing to monitor the state of our service.
This incident has been resolved.
There was a partial outage for ink-whisper due to which traffic being routed to a particular pod worker was failing. We have rolled out a fix for this to prevent this from happening again.
We are currently investigating the issue.
A fix has been implemented to address agent deployment and call connection errors. We are monitoring the results.
This incident has been resolved.
We are aware of elevated training durations for Pro Voice Clones, the team is actively investigating.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We're experiencing an elevated level of errors downloading files and are currently looking into the issue.
Our file server is unable to verify read permissions. Most requests should succeed now.
We are continuing to work on a fix for this issue.
This incident has been resolved.
We're experiencing errors downloading files.
Our file server could not verify read permissions.
We are currently investigating timeouts on API requests to CRUD endpoints (including Voices & Agents).
We are continuing to investigate - users accessing the Playground may also be affected by this.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Due to issues with a downstream provider, calls made to voice agents on the Line platform may fail to connect
We are continuing to investigate this issue.
The issue with our downstream provider has been resolved.
We have identified an issue with our authentication provider that is currently affecting the Cartesia playground. No production API traffic is affected.
We have confirmed resolution of the incident with our auth provider.
Our TTS endpoints for sonic-3.5 experienced degraded performance and queuing between UTC 15:01 and UTC 15:32. We've mitigated the issue and are monitoring the situation.
Due to some billing issues with our telephony provider, phone calls were unavailable from 7:54 AM PST to 8:39 AM PST. We've since resolved the issue and are looking into how to improve our processes further to avoid issues like this in the future. Please let us know if you continue to see any errors, we apologize for the inconvenience.
This incident has been resolved.
We are noticing issues with some services that require a path to blob stores: The following are impacted: - Voice agent call recordings (creating and downloading) - Voice Cloning Creation - Pro Voice Cloning The following are *NOT impacted*: - Our TTS API - The voice agent call will complete (just no call recordings)
We are continuing to investigate this issue.
We deployed some mitigations and most services are restored. The only degradation we face is that voice agent call recordings are currently delayed.
A fix has been implemented and we are monitoring the results.
This incident has been resolved. All voice agent call recordings should be visible on the playground. Please let us know if you continue to experience any issues.
We are currently investigating this issue.
The issue seems to be stemming from an upstream provider.
A mitigation has been rolled out and we're monitoring for recovery.
This incident has been resolved.
We are currently investigating an issue with playground pages taking a long time to load. Initial investigation indicates the issue started at 2:37 PM PT (10m ago).
We have identified and mitigated the issue. We are monitoring the fix.
We have confirmed the fix had its intended effect. This incident is resolved.
We are investigating an issue causing some voice agents are failing to reach their runtime deployments, returning a "trouble connecting to an agent" error. We will share an update as soon as we have more information.
We've identified an issue with an upstream provider, and we're actively working on rolling it back.
This incident has been resolved.
We are currently investigating this issue.
An upstream infrastructure provider identified a DNS resolution issue affecting WebSocket connections to voice agent deployments. A mitigation has been put in place and failure rates have recovered fully. We are continuing to monitor.
This incident has been resolved.
Our application was deployed on a node that had falsely configured networking setup, resulted in degradation of our TTS service in the US. Customers may see elevated connection errors and false rate limiting errors. The incident happened between 9:04AM and 9:08AM PT.
We are experiencing intermittent connectivity issues affecting voice agent sessions due to degradation at an upstream infrastructure provider. Some calls may fail to connect or drop unexpectedly.
A mitigation and additional observability have been deployed. We are actively monitoring for recovery and are seeing connections recover.
This incident has been resolved.
We're currently experiencing degraded login functionality on play.cartesia.ai due to an issue with our authentication provider, Clerk. We're monitoring the situation and you can also track their status at: https://status.clerk.com/
This incident has been resolved by Clerk.
Duration: March 10, 2026, 9:00 AM PST - 9:14 PM PST Impact: Runtime logs for Line agent calls made during this time period were not available via the dashboard or API. Call processing was not affected. Resolution: Our engineering team identified the root cause as an upstream breaking change from an infrastructure provider that disrupted our log ingestion pipeline. A hotfix was deployed and log collection has been fully restored. All logs from the affected window have also now been recovered and backfilled. Next Steps: We are conducting a postmortem to improve reliability and detection speed moving forward.
TTS generations using pronunciation dictionaries produce incorrect audio (some structured metadata is read out in the speech). Workaround for affected customers: use `sonic-3` instead of `sonic-3-latest`.
We have rolled back the bad deploy and pronunciation dictionaries are once again working with `sonic-3-latest`.
This incident has been resolved.
Some users are having trouble signing in; some users are experiencing latency in signin. Our provider Clerk has an incident page here: https://status.clerk.com/ API and API authorization is unaffected; this is only on play.cartesia.ai and docs.cartesia.ai
Our provider has rolled out a fix and we are monitoring the recovery.
This incident has been resolved.