Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Outage in Take Blip

Unavailability in the operation of the bots

Resolved Major
October 15, 2026 - Started about 1 month ago - Lasted about 4 hours
Official incident page

Incident Report

We have identified an issue that is causing the bots to be unavailable. Our engineering team is currently working to investigate the situation, determine the root cause of the failure, and define the necessary steps to restore bot functionality.During our investigation, we identified connection issues and problems with database operations. Our technical teams are continuing to analyze the situation; we have observed the restoration of connections, the recovery of conversation history, and the return to normal operation for some bots.
Components affected
Take Blip Desk Take Blip BlipChat

Trusted by 1,000+ teams

The Status Page Aggregator with Early Outage Detection

Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.

IsDown status aggregator dashboard
Latest Updates ( sorted recent to last )
RESOLVED about 1 month ago - at 10/15/2026 09:29PM

The issue affecting bot operations has been resolved. The failure, which originated at the external provider of the database service used by the platform, affected the message flow of bots, including message reception, processing, and response delivery, message routing, and conversation history. We worked together with the provider on the fix, restarted some services, and validated the environment, which remains under monitoring. We ask customers to validate that their operations are working normally and, if any behavior persists, to contact support with the bot, the affected contact, and the date and time of the occurrence.

MONITORING about 1 month ago - at 10/15/2026 08:41PM

Most of the environment is already recovering gradually. The service responsible for message routing and for associating notifications with received messages, the service responsible for conversation context and history, and the completion of history loading in some specific databases are still awaiting full restoration. Until these items are completed, failures or delays may occur in message routing, message status updates, and the display of conversation history. We are working together with the database service provider to complete the restoration and validating services as they are normalized. We will provide another update within 30 minutes or as soon as new information becomes available.

MONITORING about 1 month ago - at 10/15/2026 08:11PM

We are still awaiting the full restoration of services affected by a failure at the external provider of the database service used by the platform. Part of the environment is already recovering gradually, while other services are still awaiting the completion of corrective actions to resume operation. The impact continues to affect the message flow of bots, including message reception, processing, and response delivery for both automated interactions and Desk. We are working together with the provider to resolve the issue and validating services as they are restored. We will provide another update within 30 minutes or as soon as new information becomes available.

MONITORING about 1 month ago - at 10/15/2026 07:39PM

Some services are already recovering gradually, while others remain unavailable. The instability is caused by a failure at the external provider of the database service used by the platform, and we are working together with the provider to resolve the issue. The impact affects the message flow of bots, including message reception, processing, and response delivery for both automated interactions and Desk. We continue tracking the recovery and validating restored services until the environment is fully normalized. We will provide another update within 30 minutes or as soon as new information becomes available.

INVESTIGATING about 1 month ago - at 10/15/2026 07:11PM

We have identified that the instability is caused by a failure at the external provider of the database service used by the platform. The inconsistency originated in the provider's environment, not in our infrastructure, and affects the overall message flow of bots, including message reception, processing, and response delivery for both automated interactions and Desk. Normalization depends on corrective actions being carried out by the provider, and recovery is progressing gradually. We continue following up with the provider and, once the service is restored, we will validate the message flow and operational stability. We will provide another update within 30 minutes or as soon as new information becomes available.

INVESTIGATING about 1 month ago - at 10/15/2026 06:46PM

We continue working on the incident related to an external component used in our database infrastructure. The impact is not limited to Desk and affects the overall message flow of bots, including message reception, processing, and response delivery for both automated and human-assisted interactions. Corrective measures are still being applied and services are recovering gradually. As recovery progresses, our technical teams will validate the end-to-end message flow and the operational stability of the affected environments. We will provide another update within 30 minutes or as soon as new information becomes available.

INVESTIGATING about 1 month ago - at 10/15/2026 06:36PM

We have identified inconsistencies in an external component used within our database infrastructure, which integrates various resources required for our operations. This issue may affect message processing and the functionality of bots. An investigation is underway. Measures to address the identified inconsistencies are already being implemented, and we are awaiting a gradual resumption of services to validate operational stability.

INVESTIGATING about 1 month ago - at 10/15/2026 05:58PM

We have identified an issue that is causing the bots to be unavailable. Our engineering team is currently working to investigate the situation, determine the root cause of the failure, and define the necessary steps to restore bot functionality.During our investigation, we identified connection issues and problems with database operations. Our technical teams are continuing to analyze the situation; we have observed the restoration of connections, the recovery of conversation history, and the return to normal operation for some bots.

The Status Page Aggregator with Early Outage Detection

With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.

Start free trial

No credit card required · Cancel anytime · 6320 services available

Integrations with Slack Microsoft Teams Google Chat Datadog PagerDuty Zapier Discord Webhook