- Level
- confirmed
- Worst impact
- Degraded
- Components
- API, AWS ec2-us-west-2
- Regions
- us, us-west-2
- Down Index
- 25of 100
What to do
Check whether you use Bland AI 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 42m it lasted.
Anything that failed between 2025-08-06 02:59 UTC and 2025-08-06 03:41 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 3
- investigating
A percentage of calls are experiencing higher latency. Issue is being investigated now.
provider
- resolved
This incident has been resolved.
provider
- postmortem
Some calls were experiencing higher latency, from 7:34pm - 8:35pm, due to an issue with a downstream provider. We have confirmed resolution and set fallbacks to keep latency low if this issue happens again.
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-7836b26646
Is Bland AI still down?
No, this incident was resolved 2025-08-06 03:41 UTC. For Bland AI's live state, see https://down.guide/bland.
How long did it last?
42m, from 2025-08-06 02:59 UTC to 2025-08-06 03:41 UTC, by the times Bland AI posted.
What was affected?
Bland AI named 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.