# Cartesia: Intermittent issues with voice cloning in APAC
- Impact (vendor’s label): minor
- Status: resolved
- Started: 2026-09-03 22:34 UTC · Resolved: 2026-09-04 19:37 UTC · Duration: 21 h
- Updates: 4 · Affected components: Voice Cloning
- [Vendor status page: https://status.cartesia.ai/incidents/01M1MPH0GASADA7EAFFVGKYPFC](https://status.cartesia.ai/incidents/01M1MPH0GASADA7EAFFVGKYPFC)
- [Company: Cartesia](https://rewindex.com/company/cartesia.md)
## Part of an outage event
- [AWS us-west-2 outage, Sep 3, 2026: 20 vendors, 20 incidents](https://rewindex.com/events/2026-09-03-aws-us-west-2)
- This incident started in the same window without naming AWS (timing only, not evidence of a link). (timing only, posted +44 min vs AWS’s own post)
```mermaid
flowchart LR
root["AWS us-west-2
posted 21:49 UTC"]:::root
before["Posted before AWS did
3 vendors, 3 blamed AWS
Materialize, Temporal Cloud, Semgrep"]:::blames
root --> before
h1["Within an hour
4 vendors, 4 blamed AWS
Dropbox, Teleport, Wiz, SurveyMonkey"]:::blames
root --> h1
me["Cartesia (this incident)
posted +44 min"]:::me
root -.->|"same window"| me
```
_Detected automatically from incidents that started together and named the same provider; a link means one incident named another vendor, not a confirmed cause._
## Timeline of updates
- **investigating** 2026-09-03 22:34 UTC: We are investigating the issue.
- **monitoring** 2026-09-04 03:53 UTC: We have mitigated the issue on our end and are continuing to monitor the state of our service.
- **monitoring** 2026-09-04 03:53 UTC: We have mitigated the issue on our end and are continuing to monitor the state of our service.
- **resolved** 2026-09-04 19:37 UTC: This incident has been resolved.
---
Canonical: https://rewindex.com/company/cartesia/incidents/01M1MPH0GASADA7EAFFVGKYPFC · Markdown: https://rewindex.com/company/cartesia/incidents/01M1MPH0GASADA7EAFFVGKYPFC.md · JSON: https://rewindex.com/api/v1/companies/cartesia/incidents/01M1MPH0GASADA7EAFFVGKYPFC · Generated 2026-10-20T01:31:53.544Z