Bland AI outage, 19 October 2026

Inbound calls failing to connect

Started
Resolved
19 Oct 2026, 16:54 UTC (after 9 min)
Impact
Major
Affected
API

Is this still happening?

No. Bland AI marked this incident resolved on 19 Oct 2026, 16:54 UTC, 9 min after it began.

Right now: Bland AI reports all systems operational. (as of 26 Oct, 03:47 UTC) Live Bland AI status

Last update from Bland AI

**Summary** On October 19, 2026, from 9:45 to 9:53 AM PT, many inbound calls to Bland phone numbers in our US region failed to connect. From about 9:30 AM PT, inbound calls also took longer than normal to connect. Inbound calls have connected normally since 9:54 AM PT. **What happened** Our primary US database slowed down while it ran required maintenance on several of its largest tables during morning peak traffic. At the same time, long-running queries and a background job tied up database connections. To answer an inbound call, our servers look up the number's configuration in the database. Those lookups took longer than our telephony layer allows, so calls were rejected. Engineers...

19 Oct 2026, 19:09 UTC

Read the full incident on the official Bland AI status page

Similar Bland AI incidents

Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.

  1. , resolved after 7 min

    Knowledge Base Queries Failing

  2. , resolved after 1 h 2 min

    Issue with dispatching outbound calls

  3. , resolved after 3 h 5 min

    STT Partial Outage

  4. , resolved after 1 h 35 min

    API Timeouts

  5. , resolved

    US Region Database outage

Other recent Bland AI incidents

  1. LLM outage - Widespread agent silence

  2. Variable Extraction Model Routing Failures

  3. Delayed or missing agent audio on BTTS V3 voices

  4. High LLM Response Latency

  5. Elevated latency on voice calls

  6. Heightened LLM Latency

  7. Degraded Warm Transfers Performance

  8. Degraded TTS for BTTS v1 voices

All recorded Bland AI incidents