- Level
- confirmed
- Worst impact
- Partial outage
- Components
- API, API, AWS ec2-us-west-2
- Regions
- us, us-west-2
- Down Index
- 28of 100
What to do
Check whether you use Bland AI API, API, AWS ec2-us-west-2 in 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 1m it lasted.
Anything that failed between 2025-09-09 20:26 UTC and 2025-09-09 20:27 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
We experienced an inbound call routing issue from 12:06pm to 12:20pm that prevented inbound calls from connecting properly. Service has been fully restored.
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-226f390ef4
Is Bland AI still down?
No, this incident was resolved 2025-09-09 20:27 UTC. For Bland AI's live state, see https://down.guide/bland.
How long did it last?
1m, from 2025-09-09 20:26 UTC to 2025-09-09 20:27 UTC, by the times Bland AI posted.
What was affected?
Bland AI named API, API, AWS ec2-us-west-2 in 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.