C
Outage recap · Cartesia

Cartesia outage — August 14, 2026

On August 14, 2026, Cartesia had 2 reported incidents on Cartesia's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

Issues with files

minor
Started
Aug 14, 2:24 AM EDT
Resolved
Aug 14, 3:30 AM EDT
Duration
1h 7m

Cartesia's updates (2)

  1. identified · Aug 14, 2:24 AM EDT

    Impacts voice agent background sounds and TTS history.

  2. resolved · Aug 14, 3:30 AM EDT

    This incident has been resolved.

What our checks recorded

We checked Cartesia 13 times from Cartesia's start time to its resolution, once every five minutes. Every one of them reached Cartesia's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 117 ms, against 139 ms over the 24 hours before. Cartesia posted the incident at Aug 14, 2:24 AM EDT.

Updates are Cartesia's own words from its status page (status: resolved); we never add an inferred cause.

TTS language region validation fails requests

minor
Started
Aug 14, 3:58 AM EDT
Resolved
Aug 14, 5:34 AM EDT
Duration
1h 37m

Cartesia's updates (4)

  1. identified · Aug 14, 3:58 AM EDT

    A change rejects unknown TTS language regions, e.g. `hi-in` is rejected since an ISO 3166-1 alpha-2 country code is expected. We are working on rolling back this change. To correct the issue immediately, avoid sending the country code or send a corrected country code such as `hi-IN`.

  2. identified · Aug 14, 4:07 AM EDT

    The change has been rollbacked in APAC.

  3. monitoring · Aug 14, 5:31 AM EDT

    We have mitigated the issue on our end and are continuing to monitor the state of our service.

  4. resolved · Aug 14, 5:34 AM EDT

    This incident has been resolved.

What our checks recorded

We checked Cartesia 19 times from Cartesia's start time to its resolution, once every five minutes. Every one of them reached Cartesia's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 146 ms, against 137 ms over the 24 hours before. Cartesia posted the incident at Aug 14, 3:58 AM EDT.

Updates are Cartesia's own words from its status page (status: resolved); we never add an inferred cause.

AIDownCheck is not affiliated with Cartesia. This recap summarizes incidents published on Cartesia's official status page.