- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 18of 100
What to do
Check whether your product depends on Bland AI. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide 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 2025-07-25 18:34 UTC and 2025-07-25 16: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.
Root cause
There was an intermittent transcription issue when using Babel due to scaling with our GPU provider, causing audio to not be picked up from the user, that started at 9:30am PST.
Category: Capacity
Read the postmortemUpdates from Bland AI 1
- resolved
There was an intermittent transcription issue when using Babel due to scaling with our GPU provider, causing audio to not be picked up from the user, that started at 9:30am PST. This has been fully resolved as of 11:30am PST.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-7c68fb0d06
Is Bland AI still down?
No, this incident was resolved 2025-07-25 16:30 UTC. For Bland AI's live state, see https://down.guide/providers/bland.
How long did it last?
0m, from 2025-07-25 18:34 UTC to 2025-07-25 16:30 UTC, by the times Bland AI posted.
What caused it?
Capacity. Bland AI wrote: "There was an intermittent transcription issue when using Babel due to scaling with our GPU provider, causing audio to not be picked up from the user, that started at 9:30am PST." The postmortem: https://stspg.io/mvhft198jjv4
Where does this come from?
Bland AI's official status page, https://status.bland.ai, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.