Bland experienced a major incident on October 19, 2026 affecting API, lasting 8m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- monitoring Oct 19, 2026, 05:58 PM UTC
Between 9:45 and 9:53 AM PT (16:45–16:53 UTC), many inbound calls to Bland numbers in the US region failed to connect. Some inbound calls also had slower call setup starting around 9:30 AM PT. The cause was a database slowdown. Inbound calls have connected normally since 9:54 AM PT. We are monitoring while we roll out fixes to prevent this from happening again. Outbound calls were not affected.
- resolved Oct 19, 2026, 06:52 PM UTC
This incident has been resolved.
- postmortem Oct 19, 2026, 07:09 PM UTC
**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 stopped the long-running queries, which freed database capacity, and inbound calls recovered. **Impact** - Inbound calls to US numbers from 9:45 to 9:53 AM PT: many calls failed to connect. - Inbound calls to US numbers from about 9:30 AM PT: calls took longer than normal to connect. - Our other regions, including our FedRAMP environment, were not affected. - We have found no impact on call records or recordings. **What we're doing about it** - We've deployed a time limit on the slow queries involved. The background job no longer holds database connections while it waits. - We're changing how maintenance runs on our largest tables, so it happens in smaller passes and doesn't pile up at peak. - We're limiting how much database capacity a single query can use, and reserving capacity for call setup. - We're adding alerts on inbound call setup time, so we're paged before customers notice. We're sorry for the disruption. If this incident affected your calls, please contact your account team for a closer review.