Cartesia

This incident has been resolved.

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

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

We are investigating the issue.

This incident has been resolved.

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

We are investigating the issue.

We are investigating the issue.

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.

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

We are investigating some connection errors in US region.

This incident has been resolved.

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

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

We are investigating the issue.

This incident has been resolved.

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

The change has been rollbacked in APAC.

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`.

This incident has been resolved.

Impacts voice agent background sounds and TTS history.

This incident has been resolved.

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

This incident has been resolved.

We are continuing to investigate the issue.

We are investigating the issue.

We're experiencing an elevated level of errors downloading files and are currently looking into the issue.

This incident has been resolved. We apologize for the inconvenience and will provide further details once we've concluded our internal investigation.

We are investigating the issue.

This incident has been resolved.

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

Rerouting traffic

We have identified some network issues and are attempting to mitigate the issue.

We are investigating the issue.

We are investigating the issue.

This incident has been resolved.

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

We are investigating the issue.

This issue should be resolved now. We'll follow up with an RCA, but please reach out if you continue to see unexpected errors.

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

We have failed over to a backup provider and we're seeing recovery across the API.

We are investigating the issue.

We've mitigated this issue and customers should no longer see any degraded performance.

We’re investigating an issue affecting autoscaling performance. Services remain available, though some customers may experience temporary degradation in quality. Our team is actively working to identify and mitigate the issue, and we’ll provide updates as they become available. We've also identified partial failures for some voice cloning requests and mitigated the issue.

We’re investigating an issue affecting autoscaling performance. Services remain available, though some customers may experience temporary degradation in quality. Our team is actively working to identify and mitigate the issue, and we’ll provide updates as they become available.

This incident has been resolved.

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

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

We are investigating an outage with our underlying infrastructure provider that impacted TTS traffic in the US.

This incident has been resolved.

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

Issue initiating new agent deployments via the CLI has been identified and a fix is being implemented. Calls are not impacted.

This incident has been resolved.

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

We are investigating the issue.

This incident has been resolved.

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

We are investigating the issue.

This incident has been resolved.

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

We are investigating the issue and what components are affected.

Cartesia server was down for ~8-10 minutes

Incident's been resolved.

Fix has been deployed, validated on a few test accounts and waiting for user feedback.

The Playground is currently down for a subsection of users. We've identified the issue and are rolling back the change.

When your product or service isn’t functioning as expected, let your customers know by creating an incident. Communicate early, even if you don’t know exactly what’s going on.

Empathize with those affected and let them know everything is operating as normal.

As you continue to work through the incident, update your customers frequently.

Let your users know once a fix is in place, and keep communication clear and precise.

Root cause identified and full fix deployed to production. Post mortem to be shared out soon.

Stop-gap was deployed at 3:39. API is up, monitoring while root causing.

We had a major outage from 1:35-3:36

We have deployed a temporary remediation and are currently monitoring the API.

An outage has recurred and we are actively resolving the issue.

A fix has been implemented and we are monitoring the results.

Deployed a stop-gap to resolve outage. Still root causing the issue.

We are continuing to investigate this issue.

We are currently investigating an API outage.

One of our workers was corrupted for 20-30 minutes, so a small increase in voice generation issues there.

Root cause was identified. Solution has been working for the last ~4-5 hours so marking this as resolved.

A stop-gap has been implemented, still root causing.

Production API has gone down

This incident has been resolved.

Will monitor until Vercel is back up

Confirmed the deployed fix works as intended. Reported user issues have been resolved.

A fix has been deployed, tests in production look good waiting for user feedback.

A recent deploy has caused some users to report issues with voice cloning. We are currently investigating