Degraded TTS

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 0m it lasted.

  Anything that failed between 2026-03-04 17:30 UTC and 2026-03-04 17:30 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.

Updates from Bland AI 1

1. resolvedMar 4, 2026, 5:30 PM UTC

   Our BTTS service experienced degraded performance due to a failure in our underlying cloud infrastructure's ability to scale compute capacity to meet demand. This resulted in agents stuttering, failing to vocalize responses, increased latency, or producing incomplete audio output during the affected window, for calls that utilize BTTS v2 voices. The timeline was as follows: 6:00 AM PST: BTTS model began failing to scale due to insufficient compute capacity in its assigned cloud cluster. 6:30 AM PST: An automated alert fired but was misconfigured as non-critical and was not actioned. ~8:00 AM PST: Rising call volume exceeded available capacity, causing noticeable impact to production calls. 9:11 AM PST: We identified degraded performance through internal monitoring and began investigating. 9:32 AM PST: BTTS compute was migrated to a separate cloud cluster with available capacity. Scaling resumed normally and performance returned to baseline.

   provider

Corrections

None so far.

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