down
Is Cartesia down?
Check Cartesia availability, incident history, downtime reports, and website performance.
https://cartesia.ai ↗Mapped components are operational in the latest status update; individual experiences can vary.
Estimated down reports for Cartesia
Last 24 hoursThere is not enough activity for a usable 24-hour estimate. Status and website measurements remain available below.
Last collection attempt: 2026-10-20 11:19:29 UTC · Insufficient activity.
No user-submitted outage reports in the last 24 hours.
Cartesia outage history
2025–2026Daily history over the past 12 months. Select a day for its evidence.
Select a square for daily details. Scroll sideways to explore earlier months.
How to read this calendar
Dates use New York time (America/New_York). Green means no issues observed with sufficient monitoring coverage; it does not guarantee uninterrupted uptime. Pink includes official incidents, repeated website failures, or corroborated user reports. Gray days are unknown. Activity estimates alone do not turn a day pink. Today’s result can change.
Cartesia website uptime and response time
Current website availability is unknown. No website checks available yet.
Unknown
Successful website checks (24h)
0 successful / 0 measurable checks
Unknown
Median response time
Unknown
95th percentile response time
0 failed checks; 0 restricted checks. Restricted checks are excluded from the success rate. Lines connect recorded samples across gaps; availability between checks is unknown. Response time measures receipt of HTTP headers, not full page load. Checks run from one US monitoring server and do not verify sign-in, API, or app features. These sampled results are separate from down reports and estimated activity.
Evidence behind the status
Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary.
Website checks and estimated activity have independent update times. Refer to each section for its latest observation.
These measurements describe different things. A reachable homepage can coexist with login or API failures. Missing evidence stays unknown.
Official component status
Cartesia official status · fetched 2026-10-22 00:15:14 UTC
11 mapped components · 0 reporting problems
| Component | Provider status |
|---|---|
| Text to Speech (US) | operational |
| Text to Speech (EU) | operational |
| Text to Speech (APAC) | operational |
| Text to Speech (AU) | operational |
| Speech to Text (US) | operational |
| Speech to Text (EU) | operational |
| Speech to Text (APAC) | operational |
| Speech to Text (AU) | operational |
| Playground | operational |
| Voice Cloning | operational |
| Voice Agents | operational |
Official incident timeline
Playground unavailable · resolved · 2026-10-15T22:41:36Z
Product match: unmapped.
Read the provider’s incident report
- · resolved
The Playground has been restored and is healthy. The disruption is resolved. API services were unaffected.
- · identified
The Playground is currently unavailable. API services are unaffected. We have identified the cause of the disruption and are actively working to remediate.
Intermittent API and Playground Errors · resolved · 2026-10-08T23:09:19Z
Product match: unmapped.
Read the provider’s incident report
- · resolved
This incident has been resolved.
- · monitoring
The intermittent connectivity issues have resolved; we are continuing to monitor the state of our service.
- · investigating
We are investigating intermittent errors affecting some API and Playground operations, including access-token creation, voice browsing, and agent management. We are working to identify the cause and mitigate.
Degraded API Performance in US Regions · resolved · 2026-10-07T23:17:34Z
Product match: unmapped.
Read the provider’s incident report
- · resolved
The replacement for the offending change has been deployed. The incident is resolved.
- · monitoring
This degradation has been quickly mitigated; we are closely monitoring performance for all key endpoints in the US regions.
- · investigating
Our caching service briefly experienced increased load due to the same configuration change, leading to increased latency in US regions again.
- · 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.
- · investigating
Customers in the US regions are facing increased latency for some API requests.
API key issuing degraded · resolved · 2026-09-25T23:47:52Z
Product match: unmapped.
Read the provider’s incident report
- · resolved
This incident has been resolved.
- · identified
Newly created API keys issued during this this period are invalid. Please create new API keys.
- · identified
We've traced the issue to a bug in a change to our API key issuing logic that caused new keys to not be persisted correctly. The change is being reverted. Existing production traffic is not affected. We are exploring remediation options for API keys that were issued during the incident.
- · investigating
We've identified an issue where new API keys result in an "Invalid API key" error.
Intermittent issues with voice cloning in APAC · resolved · 2026-09-04T19:37:58Z
Product match: unmapped.
Read the provider’s incident report
- · resolved
This incident has been resolved.
- · monitoring
We have mitigated the issue on our end and are continuing to monitor the state of our service.
- · monitoring
We have mitigated the issue on our end and are continuing to monitor the state of our service.
- · investigating
We are investigating the issue.
Intermittent websocket connection throttling · resolved · 2026-09-03T12:57:26Z
Product match: unmapped.
Read the provider’s incident report
- · resolved
This incident has been resolved.
- · monitoring
We have mitigated the issue on our end and are continuing to monitor the state of our service.
- · investigating
We are investigating the issue.
- · investigating
We are investigating the issue.
Elevated connection errors in US regions · resolved · 2026-09-02T00:55:30Z
Product match: unmapped.
Read the provider’s incident report
- · resolved
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.
- · resolved
We have mitigated the issue and continuing the root cause investigation.
- · investigating
We are investigating some connection errors in US region.
Elevated server-side TTFA for sonic-3.5 and sonic-3 in EU + US region · resolved · 2026-08-21T13:33:39Z
Product match: unmapped.
Read the provider’s incident report
- · resolved
This incident has been resolved.
- · monitoring
We have mitigated the issue on our end and are continuing to monitor the state of our service.
- · monitoring
We have mitigated the issue on our end and are continuing to monitor the state of our service.
- · investigating
We are investigating the issue.
Recovery tracker
No recent recovery can be established from available evidence.
0 consecutive successful checks within the last 30 minutes. These checks measure the public website; they cannot establish recovery of every feature.
Slowdown detection
More successful checks are needed to establish a response-time baseline.
Recent median: unknown · Earlier median: unknown. Flags require at least 3 recent and 5 earlier checks, more than twice the baseline, and at least 500 ms extra latency. Slowness alone does not identify server load as the cause.
Emerging down-report signals
No recent emerging problem patterns are available for this service.
Query “cartesia” · observed 2026-10-22 00:00:36 UTC · 0 newly observed problem phrases.
Query “is cartesia” · observed 2026-10-22 00:00:36 UTC · 0 newly observed problem phrases.
Emerging problem patterns can persist after an incident and do not measure report counts or prove an outage.
Is it down in your region?
Run one public website check from a community probe. Results describe that probe, not every user in a country.
Results are reused for 15 minutes. Shared free allowance: up to 60 tests per hour. A successful website check does not verify authenticated app or API functions.
Infrastructure incident context
Check whether broader platform incidents coincide with the problem you are seeing. These providers are context, not verified dependencies of Cartesia.
No active incidents recorded.
- Elevated Error Rate for Durable Objects in Lisbon · investigating
- Incorrect geo location for some Cloudflare WARP users · identified
About Cartesia status on Iszdown
Check Cartesia availability, incident history, downtime reports, and website performance.
This page combines the available Cartesia report activity, official product status, public website measurements, and daily history. Each measurement has its own observation time. A search spike alone does not confirm downtime, and a reachable website does not establish that sign-in or every product feature works.
11 product-matched official components are listed above. No public website measurement is available in the current window.
Visit the official Cartesia website · Official provider status · How it works
What to check when Cartesia is not working
These are troubleshooting suggestions, not a list of currently reported problems.
Cartesia will not open
Compare your usual browser or app with a private browser window, then try another network if available. Save unsent work first. A difference between networks can help separate a local connection problem from a wider disruption.
Cartesia is slow or only one feature fails
Record the affected action, exact error, and time. Compare the website response measurements with any official component incidents; loading a homepage does not test every feature.
Website troubleshooting guide · Sign-in problems · API errors and timeouts
Include the time, affected feature, and error message when contacting official support. Keep passwords, payment information, session cookies, and access tokens private.
Recent Cartesia outage history
Latest available product-matched official incidents in the calendar’s archive. Times below use UTC. Duration is the provider’s recorded incident window, not a measurement of impact on every user.
| Incident | Started (UTC) | Recorded duration | Last collected status |
|---|---|---|---|
| Playground unavailable | 4 min | resolved | |
| Intermittent API and Playground Errors | 14 min | resolved | |
| Degraded API Performance in US Regions | 354 min | resolved | |
| Intermittent issues with voice cloning in APAC | 1264 min | resolved | |
| Intermittent websocket connection throttling | 229 min | resolved | |
| Elevated connection errors in US regions | 3 min | resolved | |
| Elevated server-side TTFA for sonic-3.5 and sonic-3 in EU + US region | 88 min | resolved | |
| TTS language region validation fails requests | 97 min | resolved |
Frequently asked questions about Cartesia
Is Cartesia down right now?
Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary. This page was assembled at 2026-10-22T00:15:37.000Z.
How many Cartesia outage reports are there today?
The displayed rolling 24-hour window contains 0 recorded reports, from 2026-10-21T00:10:00.000Z to 2026-10-22T00:10:00.000Z. This is not a calendar-day total or a count of affected people. Estimated activity is shown separately as an estimate.
Why does Cartesia show operational when it is not working for me?
An official operational status can coexist with a local network issue, account problem, or feature-specific incident. Compare the mapped components, recent incident updates, and regional diagnostic on this page. Automated website checks test public access, not your signed-in session or every Cartesia feature.
When was Cartesia status last updated?
The latest status observation was 2026-10-22T00:15:14.000Z. Only matched product components and incidents are shown. The assessment is recent.
Has Cartesia had outages before?
The daily calendar links available incident evidence and retains daily monitoring summaries. Pink marks service issues, green requires sufficient observations with no issues observed, and gray means insufficient coverage. The collected history is incomplete and is not a lifetime outage count or a guarantee of uninterrupted uptime.
How do I follow Cartesia or report a problem?
Use “Watch this service” to save Cartesia in this browser’s watchlist, then return to compare its status with other saved services. Optional browser notifications can flag status changes while the watchlist page stays open and visible; background alerts are not sent. Use the problem-report button for an outage report; contact the provider through its official website for account, billing, or private support issues. Iszdown is independent and cannot resolve provider support tickets.
Related services to Cartesia
Check a related product separately; its status can differ from Cartesia.