Bland AI Outage History

26 incidents recorded over the last 365 days, 24 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Bland AI status100.00% uptime history

Every Recorded Bland AI Incident

Bland AI incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 19, 2026Inbound calls failing to connect**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…8 minResolved
Oct 14, 2026LLM outage - Widespread agent silence**Summary** On October 14, 2026, from about 3:00 PM to 4:10 PM PT, agents on many calls went silent or took several seconds to respond. Outbound calls requested during the incident were held in a queue and placed late…55 minResolved
Oct 5, 2026Variable Extraction Model Routing FailuresAt 11:15 AM PDT a provider side routing update caused variable extraction requests for fail for some customers. Some post call features were also affected including summary generations and analysis schemas. Fully…-107 minResolved
Sep 25, 2026Delayed or missing agent audio on BTTS V3 voicesThis incident has been resolved.19 minResolved
Sep 14, 2026High LLM Response LatencyA misconfigured cluster of LLM replicas failed to scale up during our morning burst of traffic, causing high agent response time and possibly complete silence in severe cases between 6:00am and 6:35am PT. After…-52 minResolved
Aug 27, 2026Elevated latency on voice callsFrom 2:00 PM PDT to 2:30 PM a provider outage caused limited inference capacity. Automated monitoring systems restricted outbound call dispatch during the incident. Outbound calls during this window experienced queue…-31 minResolved
Jul 14, 2026Heightened LLM LatencyLLM response times have recovered. A postmortem will be added within the hour.5h 30mResolved
Jun 8, 2026System MaintenanceThe scheduled maintenance has been completed.5 minScheduled
Jun 5, 2026STT Partial OutageThis incident has been resolved.3h 5mResolved
May 15, 2026Degraded Warm Transfers PerformanceWarm Transfer Service Disruption — May 15, 2026 Resolved | Impact: 06:00–10:17 AM PDT \(~4 hours\) | Severity: Major What happened For approximately four hours on the morning of May 15, our Warm Transfer feature…2h 26mResolved
Apr 13, 2026API Timeouts# **API Service Disruption — April 13, 2026** **Resolved** | Impact: 06:34–07:22 PDT \(48 minutes\) | Severity: Major ## **What happened** For approximately 48 minutes on the morning of April 13, our API was…1h 35mResolved
Mar 25, 2026US Region Database outage# **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…0 minResolved
Mar 24, 2026Degraded TTS for BTTS v1 voicesThis incident has been resolved.2h 39mResolved
Mar 23, 2026Degraded TTS for BTTS v1 voicesThe BTTS v1 model and engine is operating normally again.8h 3mResolved
Mar 4, 2026Degraded TTSOur BTTS service experienced degraded performance due to a failure in our underlying cloud infrastructure's ability to scale compute capacity to meet demand. This resulted in agents stuttering, failing to vocalize…0 minResolved
Mar 2, 2026Continued Database DowntimeThis incident has been resolved.19 minResolved
Mar 2, 2026Database Maintenance DowntimeThe scheduled maintenance has been completed.30 minScheduled
Feb 12, 2026Canada Database Provider OutageThe database provider has identified a potential internal networking configuration that may have caused the incident. Database connections and voice agent calls in Canada should be back to normal now.3h 17mResolved
Feb 9, 2026Agent Audio Output FailingThis incident has been resolved.0 minResolved
Feb 5, 2026Inbound Voice FallbacksA change to inbound call initialization caused calls to fallback to a default voice rather than the custom voice they were configured with. This impacted the majority of inbound calls from 1:52-3:18 PST.-260 minResolved
Feb 4, 2026API/DB OutageAn increase in database requests resulted in much higher latency, causing the majority of call requests (inbound and outbound) to fail from 12:56-12:59. In progress calls were unaffected.0 minResolved
Jan 29, 2026API/DB OutageA database outage from a migration resulted in the majority of API requests to fail from approximately 6:57-7:07 PM pst, with intermittent failures until 7:25 PM. This outage impacted most of the platform, including…0 minResolved
Dec 21, 2025Calls degradedDialogue generation and most post call processing had high error rates from 3:09 PM - 3:49 PM PST due to a provider outage. During this period the agent was not responding/very slow to respond for some dialogue turns.-113 minResolved
Dec 9, 2025Knowledge Base Queries FailingOur containers did not have enough memory for our knowledge base requirements, which was causing the queries to fail as of 11:30am PST today. More resources have been provisioned to the containers with extra bandwidth…7 minResolved
Nov 19, 2025API OutageWe will be updating this with a full resolution tomorrow morning. Currently, it looks to be due to a spike in requested data, affecting our database throughput.1h 37mResolved
Nov 6, 2025Agent Generation IssuesAn issue with an upstream inference provider caused errors in agent dialogue generation for some customers. Traffic was routed to a backup deployment as of 5:11 and error rates have recovered.-55 minResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Bland AI incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Bland AI Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Bland AI acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Bland AI outage in this window ran 8h 3m, against a mean recovery of 1h 32m. If you depend on Bland AI in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.