Skip to main content
Bland AI

Inbound calls not getting picked up

Degraded Lasted 56m · started · Bland AI's page

Level
confirmed
Worst impact
Degraded
Components
API, API, AWS ec2-ap-southeast-2, AWS ec2-us-west-2, Cloudflare Load Balancing and Monitoring
Regions
ap-southeast-2, us, us-west-2
Down Index
31of 100

What to do

  • Check whether you use Bland AI API, API, AWS ec2-ap-southeast-2, AWS ec2-us-west-2 and 1 more 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 56m it lasted.

    Anything that failed between 2025-05-12 17:07 UTC and 2025-05-12 18:03 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

  1. investigating

    Inbound calls are not getting picked up 2 minutes ago. We suspect its a database timeout.

    provider

  2. monitoring

    Calls are connecting again, and we are monitoring the issue. AWS had an outage, and we are confirming the root issue. We will report again with the root cause

    provider

  3. monitoring

    We are continuing to monitor for any further issues.

    provider

  4. resolved

    Our database provider was facing Intermittent Pooler Connectivity Issues. Things have stabilized now and the agent is back to normal performance. The incident was from 10:02am to 10:30am.

    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-25cf3b0007

Is Bland AI still down?

No, this incident was resolved 2025-05-12 18:03 UTC. For Bland AI's live state, see https://down.guide/bland.

How long did it last?

56m, from 2025-05-12 17:07 UTC to 2025-05-12 18:03 UTC, by the times Bland AI posted.

What was affected?

Bland AI named API, API, AWS ec2-ap-southeast-2, AWS ec2-us-west-2 and 1 more 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.