Delayed or missing agent audio on BTTS V3 voices

What to do

• Check whether your product depends on Bland AI. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 20m it lasted.

  Anything that failed between 2026-09-25 15:41 UTC and 2026-09-25 16:00 UTC may need a replay.

• Subscribe to Bland AI's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=bland works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Root cause

The cause was a failure in the service that generates BTTS V3 speech.

Updates from Bland AI 2

1. monitoringSep 25, 2026, 3:41 PM UTC

   From about 6:25 AM to 8:35 AM PT, some calls using BTTS V3 voices had delayed or missing agent audio. On affected calls, the agent could go silent for 10 to 30 seconds, and some calls then continued in a fallback voice. Earlier, from about 8:10 PM to 2:00 AM PT, some calls also had intermittent delays before the agent spoke. The cause was a failure in the service that generates BTTS V3 speech. We restarted the service at about 8:20 AM PT, and audio has been normal since about 8:35 AM PT. We’re monitoring while we work on a permanent fix, and we’ll post another update when this is resolved.

   provider

2. resolvedSep 25, 2026, 4:00 PM UTC

   This incident has been resolved.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.