Tavus Status
System status
View historical uptime →Incident overview
Total incidents
13
Active now
0
Resolved
13
Avg. resolution
51m
Recent incidents
View all →Conversations using Gemma-4 are experiencing delays
Charlie Builder Maintenance for 10 Minutes
Elevated Errors Rate in Face Training Pipeline
Elevated start up times for some conversations
Intermittent Response Issues with Cartesia TTS
Some Custom Replica Creations failing due to upstream Infra Provider Issue
Some Conversations Failing to Start
Cartesia Incident
Increased conversation latency using the Gemma 4 model
Some conversations are fail to start
Frequently asked questions
Is Tavus down right now?
Tavus is currently operational. DevHelm monitors Tavus's official status page continuously and updates this page every 5 minutes.
What is Tavus's current uptime?
Tavus has a measured 30-day uptime of 100.00%. Over the last 24 hours, uptime is 100.00%, and over 7 days it is 100.00%. These figures are computed from Tavus's official status page data.
How many incidents has Tavus had recently?
Tavus has experienced 13 incidents in the recent monitoring window. Resolved incidents were fixed in an average of 51m. All incidents are currently resolved.
What components does Tavus monitor?
DevHelm tracks 21 individual components for Tavus, including Conversational Video Interface, API, Replica Training Service, Replica Video Service, Customer Portal, and 16 more. Each component has its own status and 90-day uptime history shown above.
How can I get notified about Tavus outages?
You can subscribe to Tavus's incident feed via Atom/RSS at devhelm.io/status/tavus/feed.xml for use in any feed reader. For real-time alerts via Slack, email, PagerDuty, or webhooks, add Tavus as a dependency in your DevHelm workspace.
About Tavus status monitoring
This page provides real-time operational status for Tavus, powered by DevHelm's continuous monitoring infrastructure. We track Tavus's official status page and aggregate component-level data into uptime percentages, incident timelines, and historical trends.
Tavus status data is refreshed every 5 minutes. We currently track 21 individual components, each with its own operational status and 90-day uptime history.
Uptime percentages represent the proportion of time all monitored components reported operational status. Incident data comes from vendor-published incident timelines and includes status updates, affected components, and resolution times.
Track Tavus in your stack
Get alerted when Tavus has issues — before your users notice. Set up in 30 seconds.