Blip Outage History

We are currently experiencing low performance on Blip Desk. Impact: Slowness when using Blip Desk. Update: Our support team is actively working on it.

Issues with support interactions via Blip Desk: messages sent by agents are neither displayed on the screen nor recorded in the history/threads. Additionally, while messages sent by customers are logged, they do not appear to agents or encounter flow errors. High volume of warnings and server processing errors identified (envelope processing failures and "Destination not found" errors). Verification of Starter component configurations and instances, confirming isolated instances thus far.

We are investigating an issue that may be causing difficulties when sending active messages, with some messages appearing as "NOT PROCESSED". Technical teams are actively analyzing the situation. The next update is expected within 30 minutes or as soon as new information becomes available.

We are continuing to investigate an issue that may be causing difficulties when sending active messages, with some messages appearing as "NOT PROCESSED". Technical teams are performing sending tests and analyzing information to identify the cause of the processing errors. The next update is expected within 30 minutes or as soon as new information becomes available.

We have identified an anomaly in our environment, and our technical teams are investigating the issue.

We are investigating an issue affecting the loading of Blip Portal and Blip Desk. Customers may experience difficulties accessing these areas and loading their bots on the home page. Our technical team is actively investigating the situation. We will provide another update within 30 minutes, or sooner if new information becomes available.

We continue to address server instability that may be affecting the sending and receiving of messages. Technical work is ongoing. Engineering teams have made progress in checking logs and performing targeted pod restarts to restore system stability. We are continuing to work on resolving the incident and will provide another update within 30 minutes or sooner, should new information become available.

We have identified that customers may be experiencing slowness or delays in bot responses, with response times ranging from 10 seconds to one minute. Our technical teams have identified a recent update that may be linked to this issue and have already begun the process of rolling it back. We continue to monitor the environment to ensure service stability. We are actively working on the incident and will keep you informed. The next update will be sent within 30 minutes, or sooner if there are significant developments.

O envio de mensagens via BSUID (novo identificador da Meta) está temporariamente indisponível nos canais Growth, Blip Desk e API devido à realização de ajustes no serviço. Os envios utilizando número de telefone permanecem operando normalmente. Estamos trabalhando para restabelecer a funcionalidade e publicaremos novas atualizações nesta página conforme houver avanços.

We have identified slow message sending and media upload failures. As a result, customers have experienced/are experiencing/may experience media upload failures, with the error "Media upload error: Downloading media from weblink failed with http code 500, status message Timed out waiting for session" occurring.

We are investigating an issue affecting message sending through Blip Desk. Customers may experience failures or delays when sending messages. Our technical teams are actively investigating the scenario and working to better understand the scope and impact. We will provide a new update as soon as more information becomes available.

We continue investigating an issue affecting media message delivery on the WhatsApp channel. The scenario remains unchanged, and some customers may still experience failures when sending media messages. Our teams remain actively engaged in the investigation and are closely monitoring the situation. A high-priority case has been opened with the service provider involved, while additional analyses continue in parallel. We will provide further updates as soon as new information becomes available.

We are currently experiencing an instability affecting AI agents, which may result in agents not responding as expected. Our technical teams are actively investigating the issue and working on reverting a recent change to restore normal functionality. We will provide further updates within 30 minutes or as soon as more information becomes available.

We have identified an instability affecting ticket distribution on Blip Desk. Customers may experience issues when receiving, transferring, or pulling tickets. Our technical team is actively investigating the issue and working to restore normal operations as soon as possible.

We are still investigating an issue affecting ticket distribution on Blip Desk. Customers may continue to experience difficulties when receiving, transferring, or pulling tickets. Our technical team remains actively working to identify the root cause and restore normal operations.

We identified an issue affecting the Artificial Intelligence feature in Blip Studio. Bots configured with AI may not be responding to incoming messages. Our technical team is actively investigating the scenario to determine the cause and apply the necessary corrections. A new update will be provided within 30 minutes or as soon as we have further information

We are currently experiencing low performance on BlipChat. Impact: Slowness when using Blip Chat. Update: Our support team is actively working on it.

We are currently experiencing low performance on WhatsApp. Slowness while exchanging messages with chatbots via WhatsApp. Our support team is actively working on it.

The platform was normalized on January 22, 2026 at 2 PM (GMT-3) and remains operating stably, without impacting clients. Structural adjustments were made to the environment responsible for data queries, with load redistribution and continuous monitoring after the changes, ensuring the stabilization of the scenario.

We are currently investigating this issue.

We are currently investigating this issue.

We have identified an instability in the Blip portal due to a service provider failure.