Bland AI

Affected: API

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-10-19 16:45 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...

2. resolved 2026-10-19 16:54 UTC

   This incident has been resolved.

3. postmortem 2026-10-19 19:09 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...

Excerpts are shortened. Read the full incident on Bland AI's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-10-14 22:16 UTC

   The issue has been identified and a fix is being implemented.

2. identified 2026-10-14 22:24 UTC

   An upstream outage with our inference infrastructure provider has taken down our primary dialogue LLM cluster, resulting in agent silence. We have blocked further outbound dispatch and are queueing calls. We are moving workloads over to restore functionality.

3. identified 2026-10-14 22:45 UTC

   LLM workload is scaling up in a healthy cluster, expecting 10 minutes until resolution.

4. monitoring 2026-10-14 23:01 UTC

   Replicas are scaled up in the healthy cluster, monitoring system health and errors now

5. resolved 2026-10-14 23:11 UTC

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

6. postmortem 2026-10-15 00:49 UTC

   **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. The queue was fully drained by 4:41 PM PT. **What happened**...

Excerpts are shortened. Read the full incident on Bland AI's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-10-05 18:00 UTC

   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. Timeline: 11:15 AM - Requests begin...

Excerpts are shortened. Read the full incident on Bland AI's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-09-25 15:41 UTC

   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. Earlier, from about 8:10 PM to 2:00 AM PT, some calls also...

2. resolved 2026-09-25 16:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bland AI's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-09-14 13:00 UTC

   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. After diagnosing the issue we corrected our scale up mechanism to target...

Excerpts are shortened. Read the full incident on Bland AI's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-08-27 21:00 UTC

   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. Outbound calls during this window experienced queue delays and elevated latency when they did dispatch, inbound...

Excerpts are shortened. Read the full incident on Bland AI's status page.

Failure mode: Traffic surge or denial-of-service attack. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-07-14 12:45 UTC

   A burst of traffic beginning this morning at 5:45am PT has strained global resources, resulting in high LLM response times. We are currently throttling requests until shared model resources recover. Expect slow agent dialogue and knowledge base query response times. Expecting...

2. resolved 2026-07-14 18:15 UTC

   LLM response times have recovered. A postmortem will be added within the hour.

Excerpts are shortened. Read the full incident on Bland AI's status page.

Affected: API, AWS ec2-us-west-2

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-05 13:13 UTC

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

2. monitoring 2026-06-05 13:23 UTC

   A fix has been rolled out and is being monitored.

3. resolved 2026-06-05 16:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bland AI's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-15 14:55 UTC

   We are actively investigating an issue related to warm transfers not merging.

2. monitoring 2026-05-15 16:03 UTC

   A root cause has been identified at the network layer, attempting a fix now and monitoring

3. resolved 2026-05-15 17:21 UTC

   This incident has been resolved. A postmortem will be provided shortly.

4. postmortem 2026-05-15 18:37 UTC

   Warm 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 failed to merge calls between carriers and brokers. From our...

Excerpts are shortened. Read the full incident on Bland AI's status page.

Affected: API

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-13 13:34 UTC

   We are observing heightened API timeouts, affecting both inbound and outbound calling. We are actively investigating the alarms.

2. monitoring 2026-04-13 14:22 UTC

   Error rate has decreased, calls and dashboard access are operational again. Continuing to monitor as we investigate root cause.

3. resolved 2026-04-13 15:10 UTC

   API is stable, a root cause at the database level has been identified. Once confirmed, postmortem will be updated with findings.

4. postmortem 2026-04-13 17:38 UTC

   # **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 degraded. Most affected requests timed out on the client side after 60...

Excerpts are shortened. Read the full incident on Bland AI's status page.

Affected: API, AWS ec2-us-west-2

Failure mode: A schema or data migration caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-03-25 14:02 UTC

   We are currently investigating the issue. Inbound and outbound calls are affected in the US region.

2. monitoring 2026-03-25 14:20 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-03-25 14:40 UTC

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

4. postmortem 2026-03-25 14:41 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...

Excerpts are shortened. Read the full incident on Bland AI's status page.

Affected: API, API, API

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-24 18:24 UTC

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

2. monitoring 2026-03-24 20:30 UTC

   A fix has been deployed and no errors have been observed since 1:18 PM PDT. The team is still monitoring.

3. resolved 2026-03-24 21:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bland AI's status page.

Affected: API, API, API

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-03-23 16:00 UTC

   An issue with the BTTS v1 model deployment has been identified and a fix is being worked on. This incident only affects BTTS v1 voices.

2. monitoring 2026-03-23 21:13 UTC

   A new version of the v1 model has been deployed and is now accepting traffic. Monitoring to ensure efficacy.

3. resolved 2026-03-24 00:04 UTC

   The BTTS v1 model and engine is operating normally again.

Excerpts are shortened. Read the full incident on Bland AI's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-03-04 17:30 UTC

   Our 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 responses, increased latency, or producing incomplete audio...

Excerpts are shortened. Read the full incident on Bland AI's status page.

Affected: API

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-02 02:30 UTC

   We had a scheduled downtime between 6pm and 6:30pm PT. Due to unforeseen circumstances, the maintenance work has exceeded the expected window. This impacts all API access including calls. We are working on restoring database connections and expect resolution shortly.

2. investigating 2026-03-02 02:49 UTC

   Database connections have been restored. The API is operational again, and calls are running again.

3. resolved 2026-03-02 02:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bland AI's status page.

Affected: API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-02-12 21:57 UTC

   At 1:32 PM PST database requests began timing out in the Canada region. This has been identified as a database provider outage. Incident is ongoing

2. monitoring 2026-02-12 23:14 UTC

   A fix has been implemented and we are monitoring the results.

3. investigating 2026-02-13 00:31 UTC

   The database provider is still investigating the root cause. We will update here as soon as we hear updates from them.

4. resolved 2026-02-13 01:14 UTC

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

Excerpts are shortened. Read the full incident on Bland AI's status page.

Affected: AWS ec2-ap-southeast-2, AWS ec2-us-west-2

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-02-09 20:06 UTC

   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.

2. resolved 2026-02-09 20:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bland AI's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-02-04 22:00 UTC

   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.

Excerpts are shortened. Read the full incident on Bland AI's status page.

Failure mode: Traffic surge or denial-of-service attack. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-02-04 21:00 UTC

   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.

Excerpts are shortened. Read the full incident on Bland AI's status page.

Failure mode: A schema or data migration caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-01-29 03:00 UTC

   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.

Excerpts are shortened. Read the full incident on Bland AI's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2025-12-20 23:00 UTC

   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.

Excerpts are shortened. Read the full incident on Bland AI's status page.

Affected: API, AWS ec2-us-west-2

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-12-09 00:36 UTC

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

2. investigating 2025-12-09 00:39 UTC

   The issue has been resolved.

3. resolved 2025-12-09 00:43 UTC

   This incident has been resolved.

4. postmortem 2025-12-09 00:49 UTC

   Our 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 to prevent the issue from happening again.

Excerpts are shortened. Read the full incident on Bland AI's status page.

Affected: API, AWS ec2-us-west-2, Cloudflare Load Balancing and Monitoring

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-19 08:27 UTC

   We are currently investigating an issue of requests routing to api.bland.ai failing.

2. monitoring 2025-11-19 08:44 UTC

   The issue looks to have resolved, we are still identifying the root issue.

3. resolved 2025-11-19 10:04 UTC

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

Excerpts are shortened. Read the full incident on Bland AI's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2025-11-06 13:00 UTC

   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.

Excerpts are shortened. Read the full incident on Bland AI's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2025-10-23 00:30 UTC

   An upstream provider outage, that provides dynamic feature flag components - suffered a failure in their network configurations. We are assessing this dependency and will ensure it can no longer be a failure point for the dispatching of calls. For clarity, we attach their...

Excerpts are shortened. Read the full incident on Bland AI's status page.

Affected: API, AWS ec2-us-west-2

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2025-10-20 17:58 UTC

   Service disruptions with AWS is affecting our upstream provider, causing intermittent issues with dispatching calls.

2. monitoring 2025-10-20 18:08 UTC

   The issue looks to be resolved as of 10:56am PST, and had started at 10:40am PST. We will continue to monitor to confirm.

3. resolved 2025-10-20 19:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bland AI's status page.

Affected: API, API, AWS ec2-us-west-2

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2025-09-09 20:26 UTC

   We experienced an inbound call routing issue from 12:06pm to 12:20pm that prevented inbound calls from connecting properly. Service has been fully restored.

2. resolved 2025-09-09 20:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bland AI's status page.

Affected: API, AWS ec2-us-west-2

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-08-06 02:59 UTC

   A percentage of calls are experiencing higher latency. Issue is being investigated now.

2. resolved 2025-08-06 03:41 UTC

   This incident has been resolved.

3. postmortem 2025-08-06 03:41 UTC

   Some calls were experiencing higher latency, from 7:34pm - 8:35pm, due to an issue with a downstream provider. We have confirmed resolution and set fallbacks to keep latency low if this issue happens again.

Excerpts are shortened. Read the full incident on Bland AI's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-07-25 16:30 UTC

   There was an intermittent transcription issue when using Babel due to scaling with our GPU provider, causing audio to not be picked up from the user, that started at 9:30am PST. This has been fully resolved as of 11:30am PST.

Excerpts are shortened. Read the full incident on Bland AI's status page.

Affected: AWS ec2-ap-southeast-2, AWS ec2-us-west-2

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-07-25 12:38 UTC

   Our GPU provider has been facing elevated issues, affecting our inference. This started at 5:13am.

2. monitoring 2025-07-25 12:51 UTC

   The GPU provider has remedied the fix and latency seems to have recovered for the past 10 minutes. We are monitoring to confirm a full resolution.

3. resolved 2025-07-25 12:55 UTC

   The incident has been resolved

Excerpts are shortened. Read the full incident on Bland AI's status page.

Affected: API, API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-07-24 15:56 UTC

   We are aware of a downstream provider having audio streaming issues, identical to the issues observed recently. We apologize for the issues and are investigating a fix.

2. monitoring 2025-07-24 16:07 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-07-24 16:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bland AI's status page.

Affected: API, API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-07-24 07:09 UTC

   Our GPU provider is facing issues similar to the event previously today. We are exploring a way to mitigate this.

2. monitoring 2025-07-24 07:36 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-07-24 07:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bland AI's status page.

Affected: API, API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2025-07-23 18:41 UTC

   We are aware of a downstream provider having audio streaming issues. We believe it to be identical to the issues observed yesterday. We apologize for the issues and are investigating.

2. monitoring 2025-07-23 18:45 UTC

   The downstream provider has remedied the issue. We are monitoring the fix.

3. resolved 2025-07-23 18:50 UTC

   This incident has been resolved.

4. postmortem 2025-07-23 18:50 UTC

   An upstream provider, suffered a fault in the GCP central1 region. The length of the incident was observed as/from: 11:32 PDT → 11:43 PDT. We deeply apologize for this issue, and are working with our provider to investigate the 2nd day of an incident in nature.

Excerpts are shortened. Read the full incident on Bland AI's status page.

Affected: API, API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-07-22 19:19 UTC

   We are investigating failures in calls in both an inbound and outbound direction.

2. monitoring 2025-07-22 19:25 UTC

   A downstream provider suffered a temporary fault. This affected the audio transport of the call. They have confirmed to us that the situation has been mitigated. We are continuing to monitor actively.

3. resolved 2025-07-22 19:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bland AI's status page.

Failure mode: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-07-16 18:00 UTC

   There was an issue with knowledge base nodes for fetching information from the knowledge base, causing the agent to hallucinate a response. The issue has been resolved as of 17th July 9:15AM.

Excerpts are shortened. Read the full incident on Bland AI's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2025-07-11 00:00 UTC

   The call logs page was not visible for multiple users from 5:10PM to 5:24PM. The issue has since been fixed.

Excerpts are shortened. Read the full incident on Bland AI's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2025-07-10 21:30 UTC

   Calls that reached a Knowledge Base Node would have been unresponsive from 2:30pm today. The issue has been fixed as of 9:30PM.

Excerpts are shortened. Read the full incident on Bland AI's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2025-06-24 10:00 UTC

   We experienced a temporary service disruption due to scheduled maintenance by one of our third-party providers, from 3:10AM PST to 8:30AM PST. The impact was the platform being slow, api requests timing out and calls failing. The issue has been fully resolved and all services...

Excerpts are shortened. Read the full incident on Bland AI's status page.

Affected: API, API, AWS ec2-ap-southeast-2, AWS ec2-us-west-2, Cloudflare Load Balancing and Monitoring

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2025-06-20 17:46 UTC

   Our GPU provider had an outage at 10:28am, causing calls to potentially have no audio from the agent. They have since recovered at 10:35am, and are monitoring to ensure the fix is fully live.

2. resolved 2025-06-20 17:48 UTC

   The incident has been resolved as of 10:44am.

Excerpts are shortened. Read the full incident on Bland AI's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2025-06-17 23:00 UTC

   We had partial degradation in outbound calls being dispatched, because of a downstream provider having an incident with one of their services for phone number lookup. The incident was from 3:55pm to 4:13pm.

Excerpts are shortened. Read the full incident on Bland AI's status page.

Affected: API, API, AWS ec2-ap-southeast-2, AWS ec2-us-west-2, Cloudflare Load Balancing and Monitoring

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS, Cloudflare, Google Cloud.

1. identified 2025-06-12 18:20 UTC

   We’re currently seeing issues affecting upstream network providers, including Twilio, GCP, and Cloudflare. While Bland hosts all of it's calls on AWS, GCP powers some of the services used by our vendors around the call experience, so outages there can directly impact call...

2. monitoring 2025-06-12 20:36 UTC

   Upstream providers are restoring service. Some calls may continue to be impacted as broader services restore their operations. We are seeing success in using the Dashboard, and sending/receiving calls. We will provide more updates as they become available.

3. resolved 2025-06-12 21:18 UTC

   An upstream provider to our vendors, has asserted that a full recovery will be complete by 13:00 (PST). We've observed that most, if not all calls are operational. We will re-open this incident if things should change.

Excerpts are shortened. Read the full incident on Bland AI's status page.

Affected: API, AWS ec2-ap-southeast-2, AWS ec2-us-west-2, Cloudflare Load Balancing and Monitoring

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-05-30 23:14 UTC

   We are currently investigating this issue.

2. monitoring 2025-05-30 23:25 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-05-30 23:30 UTC

   The incident has been resolved. There was an issue with our queuing service that was preventing calls from being removed from our queue.

Excerpts are shortened. Read the full incident on Bland AI's status page.

Affected: API

Failure mode: Traffic surge or denial-of-service attack. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-05-21 16:45 UTC

   High number of calls are queued up due to a huge influx of calls. We are expanding our queue. You should expect to see a delay in calls dispatch for a short period. This occured at 9:16am.

2. identified 2025-05-21 16:57 UTC

   Impacted calls are non-BYOT, outbound calls. Customers who are fielding inbound calls, or running outbound calls on BYOT are unaffected.

3. monitoring 2025-05-21 19:04 UTC

   A fix has been implemented and we are monitoring the results. Calls should be dispatching immediately now.

4. resolved 2025-05-21 19:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bland AI's status page.

Affected: API, API, AWS ec2-ap-southeast-2, AWS ec2-us-west-2, Cloudflare Load Balancing and Monitoring

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-05-12 17:07 UTC

   Inbound calls are not getting picked up 2 minutes ago. We suspect its a database timeout.

2. monitoring 2025-05-12 17:28 UTC

   Calls are connecting again, and we are monitoring the issue. AWS had an outage, and we are confirming the root issue. We will report again with the root cause

3. monitoring 2025-05-12 18:03 UTC

   We are continuing to monitor for any further issues.

4. resolved 2025-05-12 18:03 UTC

   Our database provider was facing Intermittent Pooler Connectivity Issues. Things have stabilized now and the agent is back to normal performance. The incident was from 10:02am to 10:30am.

Excerpts are shortened. Read the full incident on Bland AI's status page.

Affected: API, API, AWS ec2-ap-southeast-2, AWS ec2-us-west-2, Cloudflare Load Balancing and Monitoring

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-05-12 07:16 UTC

   A small percentage of customers are facing issues of calls not connecting because of a database connection issue. This issue started at 9:30pm.

2. monitoring 2025-05-12 07:40 UTC

   A fix has been implemented and we're monitoring.

3. identified 2025-05-12 07:46 UTC

   A database issue is affecting our API requests from connecting. The fix will be live within 5 minutes.

4. identified 2025-05-12 07:48 UTC

   We are continuing to work on a fix for this issue.

5. monitoring 2025-05-12 07:48 UTC

   The fix has been deployed and calls should be back to normal. We are monitoring for any further issues.

6. resolved 2025-05-12 08:39 UTC

   Our database provider was facing Intermittent Pooler Connectivity Issues. The incident has been resolved.

Excerpts are shortened. Read the full incident on Bland AI's status page.

Affected: API, API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2025-05-08 21:23 UTC

   We've experienced API latency from between 14:00 to 14:10 PST. We're investigating the root cause. Calls dispatched or received during this period would not have connected. Currently, latency has subsided.

2. resolved 2025-05-08 21:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bland AI's status page.

Affected: API

Failure mode: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-05-02 00:46 UTC

   We are currently investigating issues the generation of agent speech. Calls may be silent in some cases. We are actively investigating the issue.

2. identified 2025-05-02 00:47 UTC

   The issue has been identified and a fix is being implemented.

3. resolved 2025-05-02 00:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bland AI's status page.

Affected: API, API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-04-29 17:20 UTC

   We're currently investigating unavailability with some of our standard voices. You may experience call failures that rely upon these voices, or calls may be using backup voices.

2. investigating 2025-04-29 19:22 UTC

   We are continuing to investigate this issue.

3. resolved 2025-04-29 19:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bland AI's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-02-28 15:21 UTC

   We are currently investigating this issue.

2. monitoring 2025-02-28 15:41 UTC

   calls are connecting as per normal

3. resolved 2025-02-28 16:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bland AI's status page.

Affected: API, API, AWS ec2-ap-southeast-2, AWS ec2-us-west-2, Cloudflare Load Balancing and Monitoring

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-02-19 00:25 UTC

   We are currently investigating this issue.

2. investigating 2025-02-19 00:30 UTC

   We are continuing to investigate this issue.

3. identified 2025-02-19 00:40 UTC

   We are experiencing login issues and elevated errors on our API, which may temporarily prevent some users from accessing the platform. This issue is limited to logging in and does not impact calls or other functionality. Our team is actively working on a resolution, and we will...

4. monitoring 2025-02-19 01:03 UTC

   A fix has been implemented and we are monitoring the results.

5. resolved 2025-02-19 01:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bland AI's status page.