Looking for an update now? Check the current status, or follow Tavus for future changes.
89.5%of 38 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
86.7%
30
4
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 3Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Our upstream GPU provider has applied a mitigation and gemma-4 error rates have returned to normal. We have alternate routing paths staged and ready to enable if the issue recurs. We are monitoring before marking this resolved.
identified
We've confirmed the issue originates with our GPU provider, who has declared a networking incident on their side. We're testing mitigations to route gemma-4 traffic elsewhere. Conversations using other LLMs are unaffected. If you need stability now, you can point your persona at a different LLM.
identified
The issue is isolated to our default LLM (gemma-4), served by a GPU provider that began returning errors at 17:40 UTC. As a temporary mitigation we are routing gemma-4 traffic to an alternate model. Customers on gemma-4 may notice a change in response style while this is in effect; we will revert once the provider recovers.
identified
This is affecting gemma-4; we recommend our customers switch to a different LLM for immediate needs.
investigating
Starting at 17:40 UTC, conversations using our default LLM began experiencing long delays and unresponsive replicas. A GPU provider is returning errors and our automatic failover is recovering most turns, but with significant added latency. We are routing traffic to a backup provider.
investigating
It appears this issue is coming from one of our downstream providers, Crusoe. We're continuing to investigate full scope of conversations affected.
investigating
We are aware of an issue currently impacting tavus conversations, we are investigating.
Legacy Incident Archive
16 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
August 2026
Elevated Errors Rate in Face Training Pipeline
minorSource not attested
Last archived state: resolved
View archived record details
Replica Training Service
monitoring
A fix has been rolled out and we are seeing errors resolve. We are continuing to monitor the fix
investigating
We are investigating an elevated error rate in image-to-face trainings.
Intermittent Response Issues with Cartesia TTS
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Cartesia has restored service, and conversations using Cartesia TTS are responding normally again. We are actively monitoring the service to ensure continued stability.
identified
We are working with Cartesia to restore normal service as quickly as possible.
Upstream status: https://status.cartesia.ai/
investigating
We are investigating an issue affecting a small number of conversations configured to use Cartesia for TTS. PAL may intermittently fail to respond during conversations. We are actively investigating the cause.
Some Custom Replica Creations failing due to upstream Infra Provider Issue
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The upstream provider has recovered and we're relaunching custom replica trainings.
identified
We are experiencing some custom replica training failures due to an upstream infra provider issue. We are working on restarting all new customer replica trainings as soon as possible. Nothing is needed from your side.
Some Conversations Failing to Start
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
All traffic has been routed away from the affected provider, and conversations are starting normally. We are actively monitoring the service to confirm continued stability.
identified
One of our GPU providers is experiencing networking issues, which is impacting conversations configured to use Cartesia for TTS and may cause them to fail to start. We are actively routing traffic away from the affected region
investigating
An outage affecting one of our GPU providers is causing elevated error rates for some conversations
Cartesia Incident
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are seeing traffic return to normal
identified
https://status.cartesia.ai/
Cartesia is failing over traffic. Elevnlabs users are not affected
investigating
An outage affecting our upstream TTS provider, Cartesia, is causing some conversations using Cartesia as the default TTS to fail to start.
Elevenlabs users are not affected
July 2026
Increased conversation latency using the Gemma 4 model
minorSource not attested
Last archived state: resolved
View archived record details
identified
Our upstream model provider is rate- limiting a subset of requests for the Gemma 4 model, resulting in increased latency. We are routing traffic away from the affected capacity and working with the provider to restore normal performance.
investigating
We are investigating increased conversation latency affecting conversations using the Gemma 4 model.
Conversations using other models are operating normally. We are actively working to identify the cause and will provide an update as soon as more information is available.
OSS LLM (tavus-oss) elevated latency and dropped turns
minorSource not attested
Last archived state: resolved
View archived record details
identified
tavus-oss conversational LLM rate-limited after an upstream provider change. Latency and dropped turns possible.
Delaying Joining on Google Meet Invites
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are currently investigating this issue.
June 2026
Replica Join Failures for New Replicas
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been deployed and we have identified the root cause. Only a very limited subset of conversations using newly trained replicas were affected by join failures. We are continuing to monitor the system.
identified
We have identified an issue where newly created replicas are failing to join CVI conversations. Existing replicas are unaffected. This issue is caused by a problem with a downstream provider, who has been notified and is actively working on a resolution. We will provide further updates as the situation develops.
Async video generation and replica training are processing slower than expected
minorSource not attested
Last archived state: resolved
View archived record details
identified
Async video generation and replica training are encountering slower than expected processing times. While requests are completing successfully, they are taking longer than expected. We have identified a downstream provider encountering hardware slow downs. We are working with the provider to expedite a resolution.
This incident does not impact CVI.
