- Level
- confirmed
- Worst impact
- Degraded
- Components
- API
- Down Index
- 23of 100
What to do
Check whether you use Bland AI API. 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 2h 35m it lasted.
Anything that failed between 2025-05-21 16:45 UTC and 2025-05-21 19:20 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 4
- identified
High number of calls are queued up due to a huge influx of calls. We are expanding our queue. You should expect to see a delay in calls dispatch for a short period. This occured at 9:16am.
provider
- identified
Impacted calls are non-BYOT, outbound calls. Customers who are fielding inbound calls, or running outbound calls on BYOT are unaffected.
provider
- monitoring
A fix has been implemented and we are monitoring the results. Calls should be dispatching immediately now.
provider
- resolved
This incident has been resolved.
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-9ce1d4a244
Is Bland AI still down?
No, this incident was resolved 2025-05-21 19:20 UTC. For Bland AI's live state, see https://down.guide/bland.
How long did it last?
2h 35m, from 2025-05-21 16:45 UTC to 2025-05-21 19:20 UTC, by the times Bland AI posted.
What was affected?
Bland AI named API.
What caused it?
Bland AI hasn't published a root cause. If it does, it shows here.
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.