- Level
- confirmed
- Worst impact
- Partial outage
- Regions
- apac
Summary
Cartesia says an internal routing component in Asia Pacific (Mumbai) lost its connection and did not reconnect automatically, causing many TTS requests to fail or respond slowly. Service was restored at 06:03 UTC on November 15; the incident is resolved.
Written by anthropic/claude-haiku-5.5 from Cartesia's own updates.
What to do
Check whether you use Cartesia in apac. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2026-11-15 07:11 UTC and 2026-11-15 05:51 UTC may need a replay.Subscribe to Cartesia's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=cartesia works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Cartesia 3
- resolved
From 21:51 PT on November 14 (05:51 UTC, November 15), an internal routing component lost its connection and did not reconnect automatically. As a result, a substantial portion of TTS requests in our Asia Pacific (Mumbai) region failed or responded slowly. We identified the issue and restored service at 22:03 PT (06:03 UTC), and error rates and latency have been normal since. We’re improving how this component recovers more gracefully from connection failures in the future.
provider
- monitoring
We have mitigated the issue on our end and are continuing to monitor the state of our service.
provider
- resolved
This incident has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-e62c49bfbf
Is Cartesia still down?
No, this incident was resolved 2026-11-15 05:51 UTC. For Cartesia's live state, see https://down.guide/providers/cartesia.
How long did it last?
0m, from 2026-11-15 07:11 UTC to 2026-11-15 05:51 UTC, by the times Cartesia posted.
What was affected?
Cartesia named in apac.
What caused it?
Cartesia hasn't published a root cause. If it does, it shows here.
Where does this come from?
Cartesia's official status page, https://status.cartesia.ai, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.