Rewindex

ChangesCartesiaPartial TTS Outage in the US

Cartesia: Major incident: Partial TTS Outage in the US

Major incidentmajor (vendor)Changed Detected status.cartesia.ai (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Cartesia removed; blue is what they added. Muted text is unchanged context.

AddedTitle#1
Before: not present
After: Partial TTS Outage in the US
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-07-29 21:58 UTC
AddedResolved time#5
Before: not present
After: 2026-07-29 22:39 UTC
AddedUpdateinvestigating#6
Before: not present
After: We are investigating an outage with our underlying infrastructure provider that impacted TTS traffic in the US.
AddedUpdatemonitoring#7
Before: not present
After: We have mitigated the issue on our end and are continuing to monitor the state of our service.
AddedUpdatemonitoring#8
Before: not present
After: We have mitigated the issue on our end and are continuing to monitor the state of our service.
AddedUpdateresolved#9
Before: not present
After: This incident has been resolved.

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

Rewindex captured this after the last checkpoint; the next run (00:41 UTC) commits it.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

History of this incident

Wednesday, July 29

1 incident change

All Cartesia changesCartesia profileMarkdownJSON