Some conversations are fail to start
major- Started
- Jul 29, 6:23 PM EDT
- Resolved
- Jul 29, 6:29 PM EDT
- Duration
- 6 min
Tavus's updates (4)
- investigating · Jul 29, 6:14 PM EDT
We are currently investigating the issue
- investigating · Jul 29, 6:23 PM EDT
We have identified the issue. An outage affecting our upstream TTS provider, Cartesia, is causing some conversations using Cartesia as the default TTS to fail to start. Only conversations configured to use Cartesia for TTS are affected. Cartesia is working on resolving this issue, and we're continuing to monitor. https://status.cartesia.ai/incidents/01KYQZ97RPSZBJRPEQGVGJANZP
- identified · Jul 29, 6:25 PM EDT
We are working with Cartesia to restore service
- resolved · Jul 29, 6:29 PM EDT
Cartesia has restored service, and conversations configured to use Cartesia for TTS are starting successfully again.
What our checks recorded
We checked Tavus 1 time from Tavus's start time to its resolution, once every five minutes. Every one of them reached Tavus's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 176 ms, against 122 ms over the 24 hours before. Tavus posted the incident at Jul 29, 6:14 PM EDT.
Updates are Tavus's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗