Tavus Outage History
Uptime record, past incidents, and downtime history for Tavus.
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| June 2026 | 92.6% | 27 | 2 |
| May 2026 | 90.3% | 31 | 3 |
| April 2026 | 83.3% | 30 | 5 |
| March 2026 | 100% | 3 | 0 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 91 Days)
Mar 29
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
June 2026
Replica Join Failures for New Replicas
Started: Jun 17, 1:22 PM
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.
Jun 17, 3:09 PM
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.
Jun 17, 1:22 PM
Async video generation and replica training are processing slower than expected
Started: Jun 16, 5:24 AM
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.
Jun 16, 5:24 AM
May 2026
Some conversations not starting
Started: May 8, 12:27 PM
monitoring
A fix has been implemented and we are monitoring the results.
May 8, 12:50 PM
investigating
We are investigating an infrastructure issue that is causing some conversations not to start
May 8, 12:27 PM
April 2026
Degraded Performance Across Multiple Services
Started: Apr 30, 4:43 PM
monitoring
All deployments have been restored, and the issue with our cloud provider has been resolved. Services are now up and running, and we’re continuing to monitor to ensure stability.
Apr 30, 6:31 PM
identified
We’ve identified the root cause of the issue and are working on deploying a fix.
Update: All services, except perception, are currently operating as expected.
Update: We’re experiencing service degradation due to an issue with our cloud provider that is throttling model inference. We’ve restored some deployments and are working with them to bring all systems back to normal.
Apr 30, 4:43 PM
investigating
We’re currently seeing elevated error rates across multiple parts of our stack, including perception, knowledge base, Gemini conversation LLM, objectives, and guardrails.
Apr 30, 3:29 PM
Increased error rates with perception models
Started: Apr 29, 3:21 PM
monitoring
Raven-0 and Raven-1 are now operating normally, and we are actively monitoring the system to ensure continued stability.
Apr 29, 7:31 PM
identified
The issue was identified and a fix has been deployed
Apr 29, 7:29 PM
investigating
We are investigating increased error rates with Raven-0 and Raven-1
Apr 29, 3:21 PM
Intermittent Call Connection Issues
Started: Apr 17, 4:05 PM
monitoring
There are intermittent call connection issues tied to upstream Daily and Cloudflare outages.
Daily: https://status.daily.co/
Cloudflare: https://www.cloudflarestatus.com/
Apr 17, 4:05 PM
Replica takes longer to join in some conversations
Started: Apr 14, 12:38 PM
investigating
We are currently investigating this issue.
Apr 14, 12:38 PM
Elevated Error Rate When Joining Conversations
Started: Apr 10, 3:42 PM
monitoring
A fix has been released by the Daily team, we are seeing traffic return to normal and will be continuing to monitor
Apr 10, 3:48 PM
identified
We are seeing elevated API errors from our webRTC provider Daily
https://status.daily.co/incidents/0vkhkxd7m20b
Apr 10, 3:42 PM
Conversations not properly initiating
Started: Apr 5, 10:36 PM
monitoring
A sub GPU provider has encountered a <10 minute outage involving their AWS instance. Traffic was automatically rerouted, although some conversations which were already sent to this provider did not properly join.
All traffic is now performing within SLA, and we're continuing to monitor.
Apr 5, 10:55 PM
investigating
Conversations requests are succeeding, but encountering issues at the GPU level which are causing replicas to not properly join
Apr 5, 10:36 PM