All Systems Operational

Uptime over the past 90 days. View historical uptime.
Conversational Video Interface Operational
API Operational
Replica Training Service Operational
Replica Video Service Operational
Customer Portal Operational
Background Video Service Operational
Bulk Request Service Operational
Video Conferencing Operational
AWS eks-us-east-1 Operational
AWS ecs-us-east-1 Operational
AWS elb-us-east-1 Operational
AWS lambda-us-east-1 Operational
AWS route53 Operational
AWS sqs-us-east-1 Operational
Google Cloud Platform Google Cloud SQL Operational
Google Cloud Platform Google Cloud Pub/Sub Operational
Google Cloud Platform Google Compute Engine Operational
Google Cloud Platform Google Kubernetes Engine Operational
Google Cloud Platform Identity & Access Management Operational
Slack integration Operational
Cartesia Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Sep 19, 2026

No incidents reported today.

Sep 18, 2026

No incidents reported.

Sep 17, 2026

No incidents reported.

Sep 16, 2026

No incidents reported.

Sep 15, 2026

No incidents reported.

Sep 14, 2026

Conversations using Gemma-4 are experiencing delays
Resolved - This incident is now resolved.
Sep 14, 19:02 UTC
Monitoring - 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.
Sep 14, 18:55 UTC
Update - 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.
Sep 14, 18:42 UTC
Update - 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.
Sep 14, 18:25 UTC
Identified - This is affecting gemma-4; we recommend our customers switch to a different LLM for immediate needs.
Sep 14, 18:18 UTC
Update - 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.
Sep 14, 18:14 UTC
Update - It appears this issue is coming from one of our downstream providers, Crusoe. We're continuing to investigate full scope of conversations affected.
Sep 14, 18:03 UTC
Investigating - We are aware of an issue currently impacting tavus conversations, we are investigating.
Sep 14, 17:58 UTC

Sep 13, 2026

No incidents reported.

Sep 12, 2026

No incidents reported.

Sep 11, 2026

No incidents reported.

Sep 10, 2026

No incidents reported.

Sep 9, 2026

No incidents reported.

Sep 8, 2026

No incidents reported.

Sep 7, 2026

No incidents reported.

Sep 6, 2026

No incidents reported.

Sep 5, 2026

No incidents reported.

Incident History Powered by Atlassian Statuspage