Is Bland AI down? › Outage history

Bland AI outage history

Bland AI published 25 incidents on its official status page since Oct 20, 2025, 6 of them rated at the highest impact level. 5 were major or long incidents with their own pages; the biggest are listed first. Below them is every smaller incident, then our own 90 day check history.

Biggest Bland AI outages

Ranked by the official impact level, then by how long they lasted. Each has its own page with the cause, the fix time and every official update.

  1. Feb 12, 2026: Canada Database Provider Outage 3 hours 18 min · rated "Critical"
  2. Nov 19, 2025: API Outage 1 hour 37 min · rated "Critical"
  3. Apr 13, 2026: API Timeouts 1 hour 36 min · rated "Critical"
  4. Oct 20, 2025: Issue with dispatching outbound calls 1 hour 3 min · rated "Critical"
  5. Jul 14, 2026: Heightened LLM Latency 5 hours 30 min · rated "Major"

Every smaller Bland AI incident

Minor and short incidents from the Bland AI status page, newest first, each with a line from the official updates. Times are UTC.

October 2026

  • Oct 19, 2026, 16:45 UTC · Inbound calls failing to connect

    9 minutes · rated "Major"

    "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."

  • Oct 14, 2026, 22:16 UTC · LLM outage - Widespread agent silence

    55 minutes · rated "Critical"

    "Replicas are healthy, opening queue back up. Expect a backlog of requests over the next hour"

  • Oct 5, 2026, 19:47 UTC · Variable Extraction Model Routing Failures

    duration not stated · rated "Major"

    "At 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 recovered at 12:11 PM."

September 2026

  • Sep 25, 2026, 15:41 UTC · Delayed or missing agent audio on BTTS V3 voices

    20 minutes · rated "Major"

    "From about 6:25 AM to 8:35 AM PT, some calls using BTTS V3 voices had delayed or missing agent audio. On affected calls, the agent could go silent for 10 to 30 seconds, and some calls then continued in a fallback voice."

  • Sep 14, 2026, 13:52 UTC · High LLM Response Latency

    duration not stated · marked as no impact

    "A 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."

August 2026

  • Aug 27, 2026, 21:31 UTC · Elevated latency on voice calls

    duration not stated · rated "Major"

    "From 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."

June 2026

  • Jun 5, 2026, 13:13 UTC · STT Partial Outage

    3 hours 5 min · rated "Minor"

    "We are investigating reports of missing transcription results affecting some customer's calls."

May 2026

March 2026

  • Mar 25, 2026, 14:40 UTC · US Region Database outage

    duration not stated · rated "Critical"

    "This incident has been resolved at 7:23am PST. We will follow up with a post-mortem."

  • Mar 24, 2026, 18:24 UTC · Degraded TTS for BTTS v1 voices

    2 hours 39 min · rated "Minor"

    "BTTS V1 is experiencing elevated error rates. We're currently investigating a fix."

  • Mar 23, 2026, 16:00 UTC · Degraded TTS for BTTS v1 voices

    8 hours 3 min · rated "Minor"

    "The BTTS v1 model and engine is operating normally again."

  • Mar 4, 2026, 17:30 UTC · Degraded TTS

    duration not stated · rated "Major"

    "Our BTTS service experienced degraded performance due to a failure in our underlying cloud infrastructure's ability to scale compute capacity to meet demand."

February 2026

  • Feb 9, 2026, 20:06 UTC · Agent Audio Output Failing

    duration not stated · rated "Major"

    "From 11:24-11:45 PST some calls experienced a disruption where agent audio was not being played, resulting in silence on the call. This issue is fully resolved but full impact is still being investigated."

  • Feb 5, 2026, 02:20 UTC · Inbound Voice Fallbacks

    duration not stated · rated "Major"

    "A 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."

  • Feb 4, 2026, 21:00 UTC · API/DB Outage

    duration not stated · rated "Major"

    "An 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."

January 2026

  • Jan 29, 2026, 03:00 UTC · API/DB Outage

    duration not stated · marked as no impact

    "A 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 active calls."

December 2025

  • Dec 21, 2025, 00:53 UTC · Calls degraded

    duration not stated · marked as no impact

    "Dialogue 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."

  • Dec 9, 2025, 00:36 UTC · Knowledge Base Queries Failing

    7 minutes · rated "Major"

    "We are currently investigating the issue of knowledge base queries failing. Calls will fallback to respond without the knowledge base context."

November 2025

  • Nov 6, 2025, 13:55 UTC · Agent Generation Issues

    duration not stated · rated "Major"

    "An 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."

October 2025

  • Oct 23, 2025, 00:39 UTC · Upstream Provider Outage

    duration not stated · rated "Minor"

    "An upstream provider outage, that provides dynamic feature flag components - suffered a failure in their network configurations."

Bland AI uptime, last 90 days

Tracked since Oct 7, 2026. Updated Oct 22, 2026, 12:35 UTC.

Uptime100%
Avg response286 ms
Problems, 30 days1
Last problemOct 19, 2026
90 days agoUp Degraded Down No dataToday

Every Bland AI problem in the last 90 days

  • Degraded

    Inbound calls failing to connect

    Oct 19, 2026, 18:04 UTC · lasted 48 minutes · from Bland AI's official status page

Day by day

Day (UTC)UptimeAvg responseWorst
Oct 22, 2026100%161 msUp
Oct 21, 2026100%233 msUp
Oct 20, 2026100%272 msUp
Oct 19, 2026100%286 msDegraded
Oct 18, 2026100%258 msUp
Oct 17, 2026100%255 msUp
Oct 16, 2026100%357 msUp
Oct 15, 2026100%264 ms
Oct 14, 2026100%280 ms
Oct 13, 2026100%312 msUp
Oct 12, 2026100%297 msUp
Oct 11, 2026100%337 msUp
Oct 10, 2026100%326 msUp
Oct 9, 2026100%313 ms
Oct 8, 2026100%302 ms
Oct 7, 2026100%328 msUp

Bland AI outage questions

Was Bland AI down today?

No. We recorded no Bland AI outage, degraded period or maintenance today (Oct 22, 2026, UTC).

Was Bland AI down yesterday?

No. We recorded no Bland AI outage, degraded period or maintenance yesterday (Oct 21, 2026, UTC).

When was Bland AI last down?

The latest problem was on Oct 19, 2026, 18:04 UTC and lasted 48 minutes: Inbound calls failing to connect.

What was the biggest Bland AI outage?

Of the incidents on record since Oct 20, 2025, the biggest was on Feb 12, 2026: Canada Database Provider Outage. The Bland AI status page rated it "Critical" and it lasted 3 hours 18 min.

How often does Bland AI go down?

Bland AI's status page posted 25 incidents since Oct 20, 2025, 4 of them in the last 30 days. Most incidents affect part of the service, not all of it. Uptime from our own checks over the last 90 days: 100%.

Times are UTC. Official incidents are the company's own posts, quoted from the Bland AI status page. Problem periods start when the official status page or our checks first show a problem and end when the service is next found working, so durations are accurate to within a few minutes. Recent outages across all services.