Bland Outage History

Bland is up right now

Pingoru has recorded 49 incidents for Bland: 23 in the last 12 months and 6 in the last 90 days.

Source: status.bland.ai

49incidents recorded
23last 12 months
6last 90 days
2 hourstypical duration

Incidents, newest first

Minor July 24, 2025 Degraded Calls 18m API, API

Started Jul 24, 2025, 03:56 PM UTC· resolved Jul 24, 2025, 04:14 PM UTC

  1. identified Jul 24, 2025, 03:56 PM 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 Jul 24, 2025, 04:07 PM UTC

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

  3. resolved Jul 24, 2025, 04:14 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical July 24, 2025 Calls Unresponsive 28m API, API

Started Jul 24, 2025, 07:09 AM UTC· resolved Jul 24, 2025, 07:38 AM UTC

  1. identified Jul 24, 2025, 07:09 AM UTC

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

  2. monitoring Jul 24, 2025, 07:36 AM UTC

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

  3. resolved Jul 24, 2025, 07:38 AM UTC

    This incident has been resolved.

Read the full incident report →

Major July 23, 2025 Calls Degraded 8m API, API

Started Jul 23, 2025, 06:41 PM UTC· resolved Jul 23, 2025, 06:50 PM UTC

  1. investigating Jul 23, 2025, 06:41 PM 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 Jul 23, 2025, 06:45 PM UTC

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

  3. resolved Jul 23, 2025, 06:50 PM UTC

    This incident has been resolved.

  4. postmortem Jul 23, 2025, 06:50 PM 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.

Read the full incident report →

Minor July 16, 2025 Knowledge Base Node Failed to Fetch Context –

Started Jul 16, 2025, 06:00 PM UTC· resolved Jul 16, 2025, 06:00 PM UTC

  1. resolved Jul 17, 2025, 06:00 PM 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.

Read the full incident report →

Minor July 11, 2025 Call Logs Page Down –

Started Jul 11, 2025, 12:00 AM UTC· resolved Jul 11, 2025, 12:00 AM UTC

  1. resolved Jul 11, 2025, 12:29 AM UTC

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

Read the full incident report →

Minor July 10, 2025 Knowledge Base Nodes Issue –

Started Jul 10, 2025, 09:30 PM UTC· resolved Jul 10, 2025, 09:30 PM UTC

  1. resolved Jul 11, 2025, 04:46 AM 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.

Read the full incident report →

Major June 24, 2025 Service Disruption due to Scheduled Maintenance 5h 20m

Started Jun 24, 2025, 11:10 AM UTC· resolved Jun 24, 2025, 04:30 PM UTC

  1. resolved Jun 24, 2025, 05:46 PM 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 are now operating normally.

Read the full incident report →

Minor June 17, 2025 Partial Degradation in Dispatch of Outbound Calls –

Started Jun 17, 2025, 11:00 PM UTC· resolved Jun 17, 2025, 11:00 PM UTC

  1. resolved Jun 17, 2025, 11:47 PM 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.

Read the full incident report →

Critical June 12, 2025 Inbound and outbound calls outage 2h 58m API, API, AWS ec2-ap-southeast-2, AWS ec2-us-west-2 and 1 more

Started Jun 12, 2025, 06:20 PM UTC· resolved Jun 12, 2025, 09:18 PM UTC

  1. identified Jun 12, 2025, 06:20 PM 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 performance. We’re actively monitoring the situation and will provide updates as soon as we have more information. Thanks for your patience.

  2. monitoring Jun 12, 2025, 08:36 PM 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 Jun 12, 2025, 09:18 PM 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.

Read the full incident report →

Major May 30, 2025 Outbound Calls are not getting dispatched 15m API, AWS ec2-ap-southeast-2, AWS ec2-us-west-2, Cloudflare Load Balancing and Monitoring

Started May 30, 2025, 11:14 PM UTC· resolved May 30, 2025, 11:30 PM UTC

  1. investigating May 30, 2025, 11:14 PM UTC

    We are currently investigating this issue.

  2. monitoring May 30, 2025, 11:25 PM UTC

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

  3. resolved May 30, 2025, 11:30 PM UTC

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

Read the full incident report →

Minor May 21, 2025 Calls dispatch delay 2h 35m API

Started May 21, 2025, 04:45 PM UTC· resolved May 21, 2025, 07:20 PM UTC

  1. identified May 21, 2025, 04:45 PM 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 May 21, 2025, 04:57 PM UTC

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

  3. monitoring May 21, 2025, 07:04 PM UTC

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

  4. resolved May 21, 2025, 07:20 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 12, 2025 Inbound calls not getting picked up 56m API, API, AWS ec2-ap-southeast-2, AWS ec2-us-west-2 and 1 more

Started May 12, 2025, 05:07 PM UTC· resolved May 12, 2025, 06:03 PM UTC

  1. investigating May 12, 2025, 05:07 PM UTC

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

  2. monitoring May 12, 2025, 05:28 PM 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 May 12, 2025, 06:03 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved May 12, 2025, 06:03 PM 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.

Read the full incident report →

Minor May 12, 2025 Database connection issue 1h 22m API, API, AWS ec2-ap-southeast-2, AWS ec2-us-west-2 and 1 more

Started May 12, 2025, 07:16 AM UTC· resolved May 12, 2025, 08:39 AM UTC

  1. identified May 12, 2025, 07:16 AM 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 May 12, 2025, 07:40 AM UTC

    A fix has been implemented and we're monitoring.

  3. identified May 12, 2025, 07:46 AM UTC

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

  4. identified May 12, 2025, 07:48 AM UTC

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

  5. monitoring May 12, 2025, 07:48 AM UTC

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

  6. resolved May 12, 2025, 08:39 AM UTC

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

Read the full incident report →

Minor May 8, 2025 API Latency 35m API, API

Started May 08, 2025, 09:23 PM UTC· resolved May 08, 2025, 09:59 PM UTC

  1. monitoring May 08, 2025, 09:23 PM 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 May 08, 2025, 09:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 2, 2025 Agent generation issues. 2m API

Started May 02, 2025, 12:46 AM UTC· resolved May 02, 2025, 12:49 AM UTC

  1. investigating May 02, 2025, 12:46 AM 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 May 02, 2025, 12:47 AM UTC

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

  3. resolved May 02, 2025, 12:49 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 29, 2025 Voice Unavailability 2h 1m API, API

Started Apr 29, 2025, 05:20 PM UTC· resolved Apr 29, 2025, 07:22 PM UTC

  1. investigating Apr 29, 2025, 05:20 PM 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 Apr 29, 2025, 07:22 PM UTC

    We are continuing to investigate this issue.

  3. resolved Apr 29, 2025, 07:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 28, 2025 Calls hanging up immediately 55m

Started Feb 28, 2025, 03:21 PM UTC· resolved Feb 28, 2025, 04:16 PM UTC

  1. investigating Feb 28, 2025, 03:21 PM UTC

    We are currently investigating this issue.

  2. monitoring Feb 28, 2025, 03:41 PM UTC

    calls are connecting as per normal

  3. resolved Feb 28, 2025, 04:16 PM UTC

    This incident has been resolved.

Read the full incident report →

Major February 19, 2025 Login Errors & Elevated API Errors 1h 22m API, API, AWS ec2-ap-southeast-2, AWS ec2-us-west-2 and 1 more

Started Feb 19, 2025, 12:25 AM UTC· resolved Feb 19, 2025, 01:48 AM UTC

  1. investigating Feb 19, 2025, 12:29 AM UTC

    We are currently investigating this issue.

  2. investigating Feb 19, 2025, 12:30 AM UTC

    We are continuing to investigate this issue.

  3. identified Feb 19, 2025, 12:40 AM 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 provide updates as soon as more information is available.

  4. monitoring Feb 19, 2025, 01:03 AM UTC

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

  5. resolved Feb 19, 2025, 01:48 AM UTC

    This incident has been resolved.

Read the full incident report →