Elevated TTS errors in Asia Pacific (Mumbai)
major- Started
- Nov 15, 2:11 AM EST
- Resolved
- Nov 15, 12:51 AM EST
- Duration
- —
Cartesia's updates (3)
- resolved · Nov 15, 12:51 AM EST
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.
- monitoring · Nov 15, 2:12 AM EST
We have mitigated the issue on our end and are continuing to monitor the state of our service.
- resolved · Nov 15, 4:23 AM EST
This incident has been resolved.
What our checks recorded
We have no checks recorded from Cartesia's start time to its resolution.
Updates are Cartesia's own words from its status page (status: resolved); we never add an inferred cause.