Cartesia reported "Elevated connection errors in US regions" on its status page at 2026-09-01 20:00 UTC.

Cartesia did not name the affected components. The updates on this page have the details.

When did the incident start and end?

It started at 2026-09-01 20:00 UTC and ended at 2026-09-01 20:04 UTC. It lasted 3 min.

How do I get alerts for Cartesia?

Subscribe to the Cartesia live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Cartesia. outages.live reads it every few minutes and keeps every update.

CartesiaIncident · 2026-09-01 20:00 UTC

Elevated connection errors in US regions

ResolvedOfficial update

We have identified the root cause as upstream provider cluster maintenance that affected our service ingress. Some clients experienced connection errors, but subsequent retries were successful.

The latest update from Cartesia.

State

Resolved

Started

61 d ago

2026-09-01 20:00 UTC

Lasted

3 min

until 2026-09-01 20:04 UTC

Worst impact

Degraded

Timeline

3 updates

20:0020:0120:0220:0320:04

DegradedUpdate postedTimes in UTC

Investigating

3 min 100%

Updates

Times in UTC

As posted by Cartesia

Resolved2026-09-02 00:55 UTC

We have identified the root cause as upstream provider cluster maintenance that affected our service ingress. Some clients experienced connection errors, but subsequent retries were successful.

Resolved2026-09-01 20:04 UTC

We have mitigated the issue and continuing the root cause investigation.

Investigating2026-09-01 20:00 UTC

We are investigating some connection errors in US region.

Cartesia in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

1 h 5 min

This incident

95% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

21 h 4 min

median 1 h 5 min

90 days agoToday

Other Cartesia incidents

All incidents

Cartesia·Elevated latency for instant voice cloning

This incident has been resolved.

Resolvedresolved 9 d ago

Cartesia·Managed Agents with OpenAI LLMs may see degraded performance

This incident has been resolved.

Resolvedresolved 11 d ago

Cartesia·Playground unavailable

The Playground has been restored and is healthy. The disruption is resolved. API services were unaffected.

Resolvedresolved 17 d ago

Cartesia·Intermittent API and Playground Errors

This incident has been resolved.

Resolvedresolved 24 d ago

Cartesia·API key issuing degraded

This incident has been resolved.

Resolvedresolved 39 d ago

Follow Cartesia

Your coding agent knows when Cartesia is down, and tells you when a failure is theirs, not yours. You can also get Cartesia incidents in a feed reader or in Slack.

Prompt

Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "cartesia" and tell me if Cartesia has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS

https://outages.cc/feed.xml?providers=cartesia

Slack

/feed subscribe https://outages.cc/feed.xml?providers=cartesia

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane