TTS language region validation fails requests
This incident has been resolved.
The latest update from Cartesia.
State
Resolved
Started
80 d ago
2026-08-14 07:58 UTC
Lasted
1 h 37 min
until 2026-08-14 09:34 UTC
Worst impact
Degraded
Timeline
4 updatesIdentified
1 h 33 min 97%
Monitoring
3 min 3%
Updates
Times in UTCAs posted by Cartesia
This incident has been resolved.
We have mitigated the issue on our end and are continuing to monitor the state of our service.
The change has been rollbacked in APAC.
A change rejects unknown TTS language regions, e.g. `hi-in` is rejected since an ISO 3166-1 alpha-2 country code is expected. We are working on rolling back this change. To correct the issue immediately, avoid sending the country code or send a corrected country code such as `hi-IN`.
Cartesia in the last 90 days
Full historyIncidents in 90 days
14
Days with an incident
12
Median duration
1 h 5 min
This incident
1.5× the median
Other Cartesia incidents
All incidentsCartesia·Elevated latency for instant voice cloning
This incident has been resolved.
Cartesia·Managed Agents with OpenAI LLMs may see degraded performance
This incident has been resolved.
Cartesia·Playground unavailable
The Playground has been restored and is healthy. The disruption is resolved. API services were unaffected.
Cartesia·Intermittent API and Playground Errors
This incident has been resolved.
Cartesia·API key issuing degraded
This incident has been resolved.
Follow Cartesia
Your coding agent knows when Cartesia is down, and tells you when a failure is theirs, not yours. You can also get Cartesia 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.cc/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 "cartesia" and tell me if Cartesia 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.cc/feed.xml?providers=cartesia/feed subscribe https://outages.cc/feed.xml?providers=cartesiaFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane