- Level
- confirmed
- Worst impact
- Partial outage
- Components
- AWS ec2-ap-southeast-2, AWS ec2-us-west-2
- Regions
- ap-southeast-2, us, us-west-2
- Down Index
- 31of 100
What to do
Check whether you use Bland AI AWS ec2-ap-southeast-2, AWS ec2-us-west-2 in ap-southeast-2, us, us-west-2. 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-02-09 20:06 UTC and 2026-02-09 20:06 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 2
- monitoring
From 11:24-11:45 PST some calls experienced a disruption where agent audio was not being played, resulting in silence on the call. This issue is fully resolved but full impact is still being investigated.
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-94ef3adfe0
Is Bland AI still down?
No, this incident was resolved 2026-02-09 20:06 UTC. For Bland AI's live state, see https://down.guide/bland.
How long did it last?
0m, from 2026-02-09 20:06 UTC to 2026-02-09 20:06 UTC, by the times Bland AI posted.
What was affected?
Bland AI named AWS ec2-ap-southeast-2, AWS ec2-us-west-2 in ap-southeast-2, us, us-west-2.
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.