Skip to main content
Cartesia

Degraded API Performance in US Regions

Partial outage Lasted 0m · started · Cartesia's page

Level
confirmed
Worst impact
Partial outage
Regions
us
Down Index
22of 100

What to do

  • Check whether you use Cartesia in us. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

    Anything that failed between 2026-10-07 23:17 UTC and 2026-10-07 22:23 UTC may need a replay.
  • Subscribe to Cartesia's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=cartesia works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Root cause

The root cause has been identified as a change that led to increased load in our internal caching service.
Read the postmortem

Updates from Cartesia 5

  1. investigating

    Customers in the US regions are facing increased latency for some API requests.

    provider

  2. monitoring

    The root cause has been identified as a change that led to increased load in our internal caching service. We have mitigated the issue on our end and are continuing to monitor the state of our service.

    provider

  3. investigating

    Our caching service briefly experienced increased load due to the same configuration change, leading to increased latency in US regions again.

    provider

  4. monitoring

    This degradation has been quickly mitigated; we are closely monitoring performance for all key endpoints in the US regions.

    provider

  5. resolved

    The replacement for the offending change has been deployed. The incident is resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-bb4505755b

Is Cartesia still down?

No, this incident was resolved 2026-10-07 22:23 UTC. For Cartesia's live state, see https://down.guide/cartesia.

How long did it last?

0m, from 2026-10-07 23:17 UTC to 2026-10-07 22:23 UTC, by the times Cartesia posted.

What was affected?

Cartesia named in us.

What caused it?

Cartesia wrote: "The root cause has been identified as a change that led to increased load in our internal caching service." The postmortem: https://status.cartesia.ai/incidents/01M4CAGW6BB52AVXQXAK4Q7ECF

Where does this come from?

Cartesia's official status page, https://status.cartesia.ai, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.