# Cartesia: Elevated TTS errors in Asia Pacific (Mumbai)

> Cartesia reported major TTS failures and slow responses in Asia Pacific (Mumbai), caused by an internal routing component disconnecting without automatically reconnecting. Its update says failures began at 05:51 UTC and service was restored at 06:03 UTC; the incident record lists a 2026-11-15 07:12

Canonical: https://rewindex.com/company/cartesia/incidents/01M7F0QM8Y4P41796C8HNK3QXG
Last updated: 2026-11-15T09:33:15Z

- Impact (vendor’s label): major
- Status: resolved · edited after publishing
- Started: 2026-11-15 05:51 UTC · Resolved: 2026-11-15 09:23 UTC · Duration: 3.5 h
- Updates: 3 · Affected components: Text to Speech (APAC)
- [Vendor status page: https://status.cartesia.ai/incidents/01M7F0QM8Y4P41796C8HNK3QXG](https://status.cartesia.ai/incidents/01M7F0QM8Y4P41796C8HNK3QXG)
- [Company: Cartesia](https://rewindex.com/company/cartesia.md)

## Summary

Cartesia reported major TTS failures and slow responses in Asia Pacific (Mumbai), caused by an internal routing component disconnecting without automatically reconnecting. Its update says failures began at 05:51 UTC and service was restored at 06:03 UTC; the incident record lists a 2026-11-15 07:12 UTC start and remained open in monitoring (0 min at last update). _(machine-written, sol)_
## Timeline of updates

- **resolved** 2026-11-15 05:51 UTC: 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** 2026-11-15 07:12 UTC: We have mitigated the issue on our end and are continuing to monitor the state of our service.
- **resolved** 2026-11-15 09:23 UTC: This incident has been resolved.

## Rewindex changes for this incident

- 2026-11-15 05:51 UTC: [Major incident: Elevated TTS errors in Asia Pacific (Mumbai)](https://rewindex.com/change/ibc15f4e24f7bd4.md)
- 2026-11-15 07:23 UTC: [Incident silently edited: Elevated TTS errors in Asia Pacific (Mumbai)](https://rewindex.com/change/r7f375b59926a89.md)
- 2026-11-15 09:33 UTC: [Incident updated: Elevated TTS errors in Asia Pacific (Mumbai)](https://rewindex.com/change/r66f825c8849be1.md)

## Cite this

Status incident (vendor impact label: major) posted by Cartesia, started 2026-11-15 05:51 UTC, resolved after 3.5 h, 3 update(s); edited after publishing.

- Canonical URL: https://rewindex.com/company/cartesia/incidents/01M7F0QM8Y4P41796C8HNK3QXG
- Citation: Cartesia, “Elevated TTS errors in Asia Pacific (Mumbai)” (2026-11-15 05:51 UTC). Archived by Rewindex: https://rewindex.com/company/cartesia/incidents/01M7F0QM8Y4P41796C8HNK3QXG (CC BY 4.0).
- Markdown link: `[Cartesia: Elevated TTS errors in Asia Pacific (Mumbai) (2026-11-15)](https://rewindex.com/company/cartesia/incidents/01M7F0QM8Y4P41796C8HNK3QXG)`


---
Canonical: https://rewindex.com/company/cartesia/incidents/01M7F0QM8Y4P41796C8HNK3QXG · Markdown: https://rewindex.com/company/cartesia/incidents/01M7F0QM8Y4P41796C8HNK3QXG.md · JSON: https://rewindex.com/api/v1/companies/cartesia/incidents/01M7F0QM8Y4P41796C8HNK3QXG · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-16T00:17:01.778Z
