Bland experienced a critical incident on March 25, 2026 affecting API and AWS ec2-us-west-2, lasting 37m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Mar 25, 2026, 02:02 PM UTC
We are currently investigating the issue. Inbound and outbound calls are affected in the US region.
- monitoring Mar 25, 2026, 02:26 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 25, 2026, 02:40 PM UTC
This incident has been resolved at 7:23am PST. We will follow up with a post-mortem.
- postmortem Mar 25, 2026, 02:41 PM UTC
# **Incident: Service Disruption — March 25, 2026** ## **Summary** On March 25, 2026, Bland experienced a service disruption from approximately 6:47 AM to 7:23 AM PT. During this window, call dispatching, API requests, and dashboard access were impacted. Inflight calls were largely unaffected. Full service was restored by 7:23 AM PT. ## **What happened** A routine database migration was applied during a period of elevated traffic. The migration triggered unexpected lock contention in our database, causing connections to stall. While the migration itself completed within 10 minutes, residual connection issues persisted until our engineering team rolled infrastructure containers to restore full connectivity. ## **Impact** For approximately 25 minutes, inbound calls could not connect and outbound calls could not be dispatched. API requests were failing or timing out, and the dashboard, including call logs, was inaccessible. After partial recovery around 7:13 AM PT, some services operated with degraded performance for an additional 10 minutes until full resolution. ## **What we’re doing about it** We are implementing the following changes to prevent a recurrence: **Migration scheduling:** All database migrations will now be applied exclusively during off-hours maintenance windows, aligned with our existing deployment schedule. **In-app status visibility:** We are adding a status page embed directly into the Bland dashboard so that any future incidents are immediately visible to users without needing to check the status page separately. **Infrastructure safeguards:** We are working with our database infrastructure provider to further understand the lock contention behavior and implement safeguards against it. We sincerely apologize for the disruption and take the reliability of our platform seriously. If you have any questions, please reach out to our support team.