- Level
- confirmed
- Worst impact
- Major outage
- Down Index
- 39of 100
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 55m it lasted.
Anything that failed between 2026-10-14 22:16 UTC and 2026-10-14 23:11 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 6
- identified
The issue has been identified and a fix is being implemented.
provider
- identified
An upstream outage with our inference infrastructure provider has taken down our primary dialogue LLM cluster, resulting in agent silence. We have blocked further outbound dispatch and are queueing calls. We are moving workloads over to restore functionality.
provider
- identified
LLM workload is scaling up in a healthy cluster, expecting 10 minutes until resolution.
provider
- monitoring
Replicas are scaled up in the healthy cluster, monitoring system health and errors now
provider
- resolved
Replicas are healthy, opening queue back up. Expect a backlog of requests over the next hour
provider
- postmortem
**Summary** On October 14, 2026, from about 3:00 PM to 4:10 PM PT, agents on many calls went silent or took several seconds to respond. Outbound calls requested during the incident were held in a queue and placed late. The queue was fully drained by 4:41 PM PT. **What happened** A data center network outage at our upstream infrastructure provider cut off the cluster that runs the language model our agents use in conversation. The model’s time to first response rose from about 0.3 seconds to more than 7 seconds on average, so agents could not answer callers in time. To keep new outbound calls from connecting into silence, we paused outbound dispatch and queued new requests. The provider moved our model to a healthy cluster, and agents recovered by 4:10 PM PT. We reopened the queue at 4:07 PM PT and released held calls at a controlled rate. **Impact** * Live calls, inbound and outbound, from about 3:00 PM to 4:10 PM PT: agents were silent or slow to respond, and many callers hung up early. * Outbound calls requested during the incident were delayed, typically by 25 to 35 minutes. The backlog cleared by 4:41 PM PT. Calls that were canceled while queued were not placed. * We have found no impact on call records or recordings. **What we’re doing about it** * We’ve deployed a fallback that retries failed conversation requests on a second cloud provider. We’re extending it to switch providers when responses slow down, not only when they fail. * We’re spreading live-call conversation across more than one provider or cluster, so one failure can’t affect every call. * We’re changing agents to recover the turn, for example by asking the caller to repeat, instead of going silent when the model fails. * We’re paging on-call as soon as model response times rise, and slowing outbound dispatch automatically when the model is degraded. We’re sorry for the disruption. If this incident affected your calls, please contact your account team for a closer review.
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-df729fdb7d
Is Bland AI still down?
No, this incident was resolved 2026-10-14 23:11 UTC. For Bland AI's live state, see https://down.guide/bland.
How long did it last?
55m, from 2026-10-14 22:16 UTC to 2026-10-14 23:11 UTC, by the times Bland AI posted.
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.