Is Blip down?

We have identified an issue affecting access to the Portal and the Desk across certain clusters. Clients report that screens remain in a continuous loading state, preventing them from viewing or using the services. This slowness/freezing during loading has been observed in specific environments. The technical team has been alerted, and a crisis response team (SWAT) has been immediately mobilized to diagnose the issue.

We have identified an issue affecting access to the Portal and the Desk across certain clusters. An analysis of routes and connectivity reveals that traffic from clients in specific regions or units is being redirected to different servers, while access remains normal in other locations. Since our internal team is experiencing no such instability, our primary hypothesis is that the issue stems from a failure within edge services or third-party network/infrastructure providers.

We have identified an issue affecting access to the Portal and the Desk across certain clusters. Our team?s internal tests continue to function normally, which confirms that the root cause of the problem does not lie within Blip?s internal infrastructure. Technical analysis indicates that the timeout errors are linked to incompatibilities with edge partners or third-party firewall/routing rules within the networks of specific service providers and clients.

We have identified an issue affecting access to the Portal and the Desk across certain clusters. This behavior is linked to an external infrastructure problem involving a partner/vendor; it does not directly impact the platform as a whole, but rather affects specific networks and locations. Our technical team is currently validating measures to provide a workaround for clients while the vendor works on a definitive resolution.

We have identified an issue affecting access to the Portal and the Desk across certain clusters. This behavior is linked to an external infrastructure problem involving a partner/vendor; it does not directly impact the platform as a whole, but rather affects specific networks and locations. Our technical team is currently validating measures to provide a workaround for clients while the vendor works on a definitive resolution.

We have identified an issue affecting access to the Portal and the Desk across certain clusters. The external provider applied a fix at 11:52 BRT and continues to monitor the outcome. Our support team has provided testing instructions to the affected clients, and we are currently in the validation phase, awaiting feedback from users to confirm that access has been fully stabilized for them.

We identified an issue affecting access to the Portal and the Desk across certain clusters. Our external infrastructure and edge provider implemented a permanent fix at 11:52 BRT and continued to monitor the results. Affected clients have confirmed that access to the Portal and Desk has been successfully restored, and validation tests conducted by our technical team have verified the full recovery of network routes and the stabilization of the platform.

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.

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.

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.

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.

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.

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.

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.

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.

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.

Issues operating Blip Desk: messages sent by customers are logged but do not appear to the agent; agent responses neither reach customers nor save to the history; and contact data and history older than 90 days are unavailable. Actions taken: Identified spikes in server errors/warnings (approx. 60,000 records/min) related to processing failures and "Destination not found" errors. Mapped and defined the impact on the customer base and Desk workflows. Analyzed infrastructure, WebSocket communication, pod integrity, and the Starter component. Performed a controlled shutdown of Starter instances to isolate potential consumer concurrency issues in Confluent. Restored and normalized message flow for Desk and WhatsApp following the Starter shutdown.

We identified a service outage affecting Blip Desk operations. This resulted in customer service difficulties: messages sent by customers failed to appear on the agent's screen, while responses sent by agents neither reached the customer nor were saved to the history; additionally, contact details and Desk history older than 90 days were not displayed. Actions taken: Mapping of error/warning spikes on the server (approximately 60,000 records/min) related to processing failures and "Destination not found" errors. Analysis of infrastructure, WebSocket connections, pod integrity, and Starter component configurations. Controlled shutdown of Starter instances to isolate concurrency issues regarding message consumption from Confluent topics. Restoration and validation of normal message flow for Desk and WhatsApp. Restart and final real-time monitoring tests to confirm environment stability.

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

The incident has been resolved. The issue was caused by a peak in the volume of individual campaign sends, which overloaded message processing and caused slowness. Adjustments were applied to improve processing performance, reduce excessive resource consumption, and separate individual and batch campaign processing. The service is now fully normalized.

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