C
Outage recap · Cartesia

Cartesia outage — September 3, 2026

On September 3, 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.

Intermittent websocket connection throttling

minor
Started
Sep 3, 5:08 AM EDT
Resolved
Sep 3, 8:57 AM EDT
Duration
3h 49m

Cartesia's updates (4)

  1. investigating · Sep 3, 5:08 AM EDT

    We are investigating the issue.

  2. investigating · Sep 3, 5:26 AM EDT

    We are investigating the issue.

  3. monitoring · Sep 3, 5:43 AM EDT

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

  4. resolved · Sep 3, 8:57 AM EDT

    This incident has been resolved.

What our checks recorded

We checked Cartesia 46 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 119 ms, against 154 ms over the 24 hours before. Cartesia posted the incident at Sep 3, 5:08 AM EDT.

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

Intermittent issues with voice cloning in APAC

minor
Started
Sep 3, 6:34 PM EDT
Resolved
Sep 4, 3:37 PM EDT
Duration
21h 4m

Cartesia's updates (4)

  1. investigating · Sep 3, 6:34 PM EDT

    We are investigating the issue.

  2. monitoring · Sep 3, 11:53 PM EDT

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

  3. monitoring · Sep 3, 11:53 PM EDT

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

  4. resolved · Sep 4, 3:37 PM EDT

    This incident has been resolved.

What our checks recorded

We checked Cartesia 253 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 149 ms, against 142 ms over the 24 hours before. Cartesia posted the incident at Sep 3, 6:34 PM 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.