Blip Outage History

Started Oct 15, 2026, 05:58 PM UTC· resolved Oct 15, 2026, 09:29 PM UTC

1. investigating Oct 15, 2026, 05:58 PM UTC

   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.

2. investigating Oct 15, 2026, 06:36 PM UTC

   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.

3. investigating Oct 15, 2026, 06:46 PM UTC

   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.

4. investigating Oct 15, 2026, 07:11 PM UTC

   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.

5. monitoring Oct 15, 2026, 07:39 PM UTC

   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.

6. monitoring Oct 15, 2026, 08:11 PM UTC

   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.

7. monitoring Oct 15, 2026, 08:41 PM UTC

   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.

8. resolved Oct 15, 2026, 09:29 PM UTC

   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.

Read the full incident report →

Started Sep 29, 2026, 12:21 PM UTC· resolved Sep 29, 2026, 02:04 PM UTC

1. investigating Sep 29, 2026, 12:21 PM UTC

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

2. investigating Sep 29, 2026, 01:01 PM UTC

   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.

3. identified Sep 29, 2026, 01:43 PM UTC

   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.

4. resolved Sep 29, 2026, 02:04 PM UTC

   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.

Read the full incident report →

Started Sep 15, 2026, 01:03 PM UTC· resolved Sep 15, 2026, 02:34 PM UTC

1. investigating Sep 15, 2026, 01:29 PM UTC

   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.

2. investigating Sep 15, 2026, 01:48 PM UTC

   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.

3. identified Sep 15, 2026, 02:07 PM UTC

   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.

4. resolved Sep 15, 2026, 02:37 PM UTC

   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.

Read the full incident report →

Started Sep 09, 2026, 02:14 PM UTC· resolved Sep 09, 2026, 02:59 PM UTC

1. investigating Sep 09, 2026, 02:14 PM UTC

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

Read the full incident report →

Started Aug 24, 2026, 11:50 AM UTC· resolved Aug 24, 2026, 01:34 PM UTC

1. investigating Aug 24, 2026, 11:50 AM UTC

   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.

2. investigating Aug 24, 2026, 12:29 PM UTC

   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.

3. identified Aug 24, 2026, 01:06 PM UTC

   We have identified the root cause related to deployment configuration variables affecting system applications and messaging traffic. Our engineering team is actively deploying corrections, validating communication certificates, and monitoring overall service recovery. We will provide another update within 30 minutes, or sooner if new information becomes available.

4. resolved Aug 24, 2026, 01:34 PM UTC

   This incident has been resolved. The underlying configuration mapping errors, connection saturation, and TLS handshake failures have been fully addressed. All system services, messaging traffic, and affected clusters have been restored to full operation. Continuous monitoring remains active to ensure system stability.

Read the full incident report →

Started Aug 24, 2026, 11:35 AM UTC· resolved Aug 24, 2026, 12:28 PM UTC

1. identified Aug 24, 2026, 11:35 AM UTC

   We have identified degraded performance in WhatsApp message delivery, with the success rate below the defined standard. This may result in message failures or delays for some customers. Our technical team is already working with high priority to stabilize the service and mitigate impacts. This page will be updated until full service restoration.

Read the full incident report →

Started Aug 20, 2026, 12:50 PM UTC· resolved Aug 20, 2026, 10:38 PM UTC

1. investigating Aug 20, 2026, 12:50 PM UTC

   We have identified a widespread issue affecting email sending and receiving on the platform. This impacts all functions dependent on this service, including login/authentication emails, report generation, notifications, and other system alerts. We have currently mobilized the technical team to assess the situation and have begun investigating the environment's logs. The next update is expected in 30 minutes or as soon as we have further information.

2. investigating Aug 20, 2026, 02:22 PM UTC

   The communications and email dispatch service experienced a temporary access block, affecting all dependent functionalities such as login emails, reports, and notifications. We are actively investigating the situation and working to restore the service. We continue to investigate the causes of the outage in coordination with the service provider's support team and are analyzing our internal environments. We remain in direct contact with the service provider, insisting on top priority for the resolution of the support ticket. We are also pursuing business contacts and channels to expedite a resolution at the executive level. Technical investigation and close monitoring of the ticket with the service provider are currently ongoing. Additionally, we are identifying contacts for immediate commercial escalation. The next update is expected in 30 minutes or as soon as we have new information.

3. investigating Aug 20, 2026, 02:50 PM UTC

   The communications and email dispatch service experienced a temporary access block, affecting all dependent functionalities such as login emails, reports, and notifications. We are actively investigating the situation and working to restore the service. The engineering team has conducted an in-depth analysis of integration logs, volume metrics, and sending events leading up to the incident, providing new technical data to the provider. We are maintaining active communication and constant coordination with the provider's specialized support team, which is conducting a technical audit of account settings, operational limits, and reputation in order to unblock the environment. Alongside technical investigations, we continue to press for critical-priority handling within the partner's management structure. Telemetry data and internal diagnostics are currently being transmitted continuously as requested by the provider's engineering team. We continue to monitor the status of message queues and integration infrastructure in real time, while also mapping out and proactively evaluating technical mitigation alternatives. The next update is scheduled for 30 minutes from now, or as soon as new information becomes available.

4. investigating Aug 20, 2026, 03:30 PM UTC

   The communications and email dispatch service experienced a temporary access block, affecting all dependent functionalities such as login emails, reports, and notifications. We are actively investigating the situation and working to restore the service. Our engineering team has conducted a deeper root-cause analysis with the provider's technical support, more precisely identifying the factors that led to the outage. We have implemented the necessary technical adjustments and validations within the environment to expedite account unblocking and resume email dispatch. We remain in direct contact with support and escalation channels to ensure the restoration of the service is treated as a top priority. Current actions include executing and validating the unblocking procedures recommended by the provider's technical team, as well as proactively monitoring email queues and application dispatch routes. We are maintaining real-time coordination with the provider until operations return to normal. The next update is scheduled for 30 minutes from now, or sooner if new information becomes available.

5. investigating Aug 20, 2026, 04:54 PM UTC

   Our email communication and dispatch service experienced a temporary access block, affecting all dependent functionalities such as login emails, reports, and notifications. We are actively investigating the situation and working to restore the service. The provider's support team has provided specific instructions and requirements to resolve the account status. Our technical team has already begun implementing the requested changes as a top priority to expedite service restoration. Efforts are focused on the rapid and secure reactivation of the affected email workflows; we are currently applying the configurations and adjustments recommended by the provider. Validation tests will be conducted once the changes are implemented in the environment, alongside real-time coordination with support for final approval and unblocking. The next update is expected in 30 minutes or as soon as we have further news.

6. identified Aug 20, 2026, 06:09 PM UTC

   The email communication and dispatch service experienced a temporary access block, affecting all dependent functionalities such as login emails, reports, and notifications. We are actively investigating the situation and working to restore the service. The provider's support team has responded with specific instructions and requirements to resolve the account status. Our technical team has already begun implementing the requested changes as a top priority to expedite service restoration. Efforts are focused on the rapid and secure reactivation of the affected email workflows. We are currently applying the configurations and adjustments recommended by the provider. Validation tests will be conducted once the changes are implemented in the environment, alongside real-time coordination with support for final approval and unblocking. We have already released some configurations and are currently validating the situation through environment testing.

7. monitoring Aug 20, 2026, 06:29 PM UTC

   The email communication and dispatch service experienced a temporary access block, affecting all dependent functionalities such as login emails, reports, and notifications. We are actively investigating the situation and working to restore the service. The provider's support team has provided specific instructions and requirements to resolve the account status. Our technical team has prioritized implementing the requested changes to expedite service restoration. Efforts are focused on the rapid and secure reactivation of the affected email workflows. We are currently applying the configurations and adjustments recommended by the provider. Validation tests will be conducted once the changes are implemented in the environment, alongside real-time coordination with support for final approval and unblocking. We have already enabled certain configurations and are currently validating the situation through environment testing. Some unblocking actions have already been completed, and some clients have confirmed successful email delivery. We are awaiting feedback from other clients to confirm the normalization of specific services and finalize validation of the reported issue. The next update is scheduled for 30 minutes from now, or as soon as new information becomes available.

8. monitoring Aug 20, 2026, 07:55 PM UTC

   The email communication and dispatch service experienced a temporary access block, affecting all dependent features such as login emails, reports, and notifications. We have implemented the changes requested by the provider and are currently applying additional configurations to safeguard other platform features, as well as setting up proactive alerts to ensure a rapid response should the issue recur. We are currently implementing a new configuration to restructure workflows, ensuring that inconsistencies in email delivery do not impact or disrupt other system functions. We have established proactive alert rules to immediately notify the technical team of any recurrence of this behavior on the provider's end. Communication and technical investigation channels with the provider and internal teams remain active to ensure complete and permanent stabilization. We are currently finalizing isolation configurations to protect other application routes and features. We are also configuring and validating predictive monitoring alerts to mitigate future incidents and continuing the technical investigation in collaboration with the provider's team. The next update is scheduled for 30 minutes from now, or as soon as new information becomes available.

9. resolved Aug 20, 2026, 10:38 PM UTC

   The email provider's corporate account experienced a temporary access block, affecting the delivery of login emails, reports, and system notifications. We have implemented the changes requested by the provider and are configuring additional safeguards for other platform features, as well as setting up preventive alerts to ensure a rapid response should the issue recur. We are implementing a new configuration to restructure workflows, ensuring that any email delivery inconsistencies do not impact or compromise other system functions. Preventive alert rules have been established to immediately notify the technical team if this behavior recurs with the provider. Communication channels and technical investigations involving both the provider and internal teams remain active to ensure the situation is fully and permanently stabilized. To resolve the incident, we carried out the adjustments and configurations required to unblock and restore the corporate account. This included unblocking and validating essential system emails, reports, and portal emails, as well as reconfiguring email integration routes passing through the gateway to ensure smooth traffic flow without affecting other platform features. We also monitored environment testing and confirmed that email receipt had returned to normal for affected customers. Next steps: An internal meeting will be held tomorrow among the responsible teams to evaluate and define the next steps for resuming email services, ensuring a safe and controlled reactivation.

Read the full incident report →

Started Aug 06, 2026, 08:47 PM UTC· resolved Aug 06, 2026, 09:01 PM UTC

1. investigating Aug 06, 2026, 08:47 PM UTC

   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.

2. resolved Aug 06, 2026, 09:01 PM UTC

   We identified that customers were experiencing slow bot response times, with delays ranging from 10 seconds to a full minute. The technical team mobilized to validate the issue and investigate the environment's logs. We performed a rollback of the application update that had been intended to improve the platform. We appreciate everyone's patience and cooperation while we addressed this situation.

Read the full incident report →

Started Aug 05, 2026, 03:58 PM UTC· resolved Aug 06, 2026, 04:48 PM UTC

1. investigating Aug 05, 2026, 04:18 PM UTC

   We are investigating an issue that may prevent some messages from appearing in Blip Desk and in the Portal history. In some cases, messages may initially appear and then disappear after a short period. Our technical team is actively investigating the issue. We will provide another update within 30 minutes or sooner if additional information becomes available.

2. investigating Aug 05, 2026, 04:32 PM UTC

   We are investigating an issue where messages may not be displayed in Blip Desk. The impact may affect both messages sent by end users and, in some cases, messages sent by agents. Our technical teams are actively investigating the issue and working to restore normal behavior. We will provide another update within 30 minutes or sooner if new information becomes available.

3. investigating Aug 05, 2026, 05:16 PM UTC

   We continue investigating an issue where messages may not be displayed in Blip Desk. The impact may affect both messages sent by end users and, in some cases, messages sent by agents. In some situations, messages become visible after a page refresh. Our technical teams are actively investigating the issue and evaluating mitigation actions while working to restore normal service. We will provide another update within 30 minutes or sooner if new information becomes available.

4. investigating Aug 05, 2026, 05:47 PM UTC

   We continue investigating an intermittent issue where messages may not appear in Blip Desk in real time. The issue may affect both customer and agent messages, and in some cases the messages become visible after refreshing the page. As part of our mitigation efforts, we have performed a rollback of recent changes in the affected environment and continue monitoring the results while investigating the root cause. We will provide another update as soon as significant progress is made.

5. investigating Aug 05, 2026, 06:49 PM UTC

   We continue to investigate an intermittent issue in Blip Desk where some messages from contacts or agents may not be displayed immediately. Refreshing the page may restore message visibility in some cases. Additionally, we have identified that this instability may vary depending on the access URL used, with some channels experiencing higher intermittency. Our technical team is actively investigating the behavior differences to isolate the root cause.

6. investigating Aug 05, 2026, 07:39 PM UTC

   Our investigation is ongoing. The issue continues to occur intermittently and may prevent messages from being displayed in Blip Desk in real time for both customers and agents. In some cases, messages become visible after refreshing the page. As part of the investigation, we completed rollback tests for recent changes, but the behavior persisted. We have also validated infrastructure components without identifying evidence of degradation and continue performing additional tests while investigating the message processing flow. Our Engineering teams remain fully engaged and are working with the highest priority to identify the root cause and implement a permanent solution. We will provide another update as soon as significant progress is made.

7. investigating Aug 05, 2026, 08:16 PM UTC

   Our investigation remains ongoing. The issue continues to occur intermittently and may prevent messages from being displayed in Blip Desk in real time, affecting both customer and agent messages. In some cases, messages become visible after refreshing the page. As part of our latest investigation, we have ruled out network, DNS, and Cloudflare-related issues. Previous rollback actions and controlled restarts of platform components did not mitigate the behavior. Our Engineering teams are now focusing on identifying potential degraded instances and comparing affected and unaffected environments to isolate the root cause. We remain fully engaged in the investigation and will provide another update as soon as significant progress is made.

8. investigating Aug 05, 2026, 08:51 PM UTC

   Our investigation is ongoing. The issue continues to occur intermittently and may affect message visibility in Blip Desk for both customers and agents. At this time, we have confirmed that the behavior is not affecting all contracts equally. Our Engineering teams have expanded the investigation after identifying additional processing events in internal component logs, while infrastructure and messaging platform validations continue to show no evidence of system-wide degradation. The investigation is now focused on tracing the complete processing flow for affected messages and determining whether the issue is isolated to specific platform components. We remain fully engaged and will provide another update as soon as significant progress is made.

9. investigating Aug 05, 2026, 09:34 PM UTC

   We are continuing to investigate this issue.

10. investigating Aug 05, 2026, 10:04 PM UTC

    The intermittent behavior persists. Messages may fail to appear in Blip Desk in real time, affecting both messages sent by contacts and, in some cases, messages sent by the agents themselves. Investigation confirms that the behavior is not uniform, affecting only a portion of the contracts.

11. monitoring Aug 05, 2026, 10:55 PM UTC

    Our Engineering teams identified and corrected a configuration inconsistency in a component responsible for message processing. We are currently monitoring the environment and validating the impact of this change to confirm full service normalization. We will continue providing updates as the investigation progresses.

12. monitoring Aug 06, 2026, 02:56 AM UTC

    Our Engineering teams completed the restart of the affected applications and servers and continue monitoring the environment after the configuration correction previously applied. Current analyses indicate the issue affects only a subset of customers, and the investigation will resume tomorrow to validate the effectiveness of the implemented actions and continue identifying the root cause if the intermittent behavior persists.

13. monitoring Aug 06, 2026, 11:24 AM UTC

    Continuous monitoring of the operation began at 07:00 AM (GMT-3). Review of the previous investigation indicated that the behavior initially perceived as widespread was linked to a misconfigured test contract. Investigation into a potential delay in message queue processing. Evaluation of optimizations to increase processing capacity. We will continue to monitor the environment and validate the optimizations under review, and we will share another update within 30 minutes or as soon as new information becomes available.

14. monitoring Aug 06, 2026, 12:14 PM UTC

    We have not identified any new instances of instability regarding message sending or history. The environment is currently operating normally and remains stable. Following the fixes and capacity optimizations implemented by our technical team, processing queues have been normalized, and we have found no discrepancies. Please verify the platform's functionality. Should you notice any residual inconsistencies, kindly let us know. We are continuing to monitor the situation and will provide a further update within 30 minutes confirming the return to normal operations.

15. resolved Aug 06, 2026, 04:48 PM UTC

    The environment has been fully restored to normal and is stable, with message flow and history back to normal. Our technical teams increased the processing capacity of the messaging queues to eliminate bottlenecks and resolved discrepancies regarding message history persistence. Normal operations were restored at 9:50 PM yesterday, and the system remained under continuous monitoring until 9:30 AM today to fully validate performance. The emergency response has concluded, and the platform remains under standard preventive monitoring.

Read the full incident report →

Started Jul 24, 2026, 09:00 PM UTC· resolved Aug 12, 2026, 07:40 PM UTC

1. investigating Jul 24, 2026, 10:10 PM UTC

   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.

2. monitoring Jul 31, 2026, 07:17 PM UTC

   Foram realizadas alterações internas no serviço, mas a função de envio via BSUID segue temporariamente desativada nos canais Growth, Blip Desk e API. O time técnico mantém o monitoramento constante sobre o ambiente. Reforçamos que 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.

3. monitoring Aug 07, 2026, 05:40 PM UTC

   Restabelecido o envio de mensagens via BSUID atraves da API. Feature segue em monitoramento do comportamento e os disparos através da interface com previsão para a próxima semana.

4. resolved Aug 12, 2026, 07:40 PM UTC

   Informamos que o incidente foi concluído. O envio de mensagens via BSUID através da API foi totalmente restabelecido

Read the full incident report →

Started Jun 23, 2026, 11:09 PM UTC· resolved Jun 24, 2026, 12:40 AM UTC

1. investigating Jun 23, 2026, 11:09 PM UTC

   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.

2. monitoring Jun 23, 2026, 11:25 PM UTC

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

3. resolved Jun 24, 2026, 12:40 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 16, 2026, 02:40 PM UTC· resolved Jun 16, 2026, 07:03 PM UTC

1. investigating Jun 16, 2026, 04:10 PM UTC

   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.

2. investigating Jun 16, 2026, 04:37 PM UTC

   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.

3. monitoring Jun 16, 2026, 05:09 PM UTC

   We have observed a significant reduction in the errors associated with this incident, and recent tests involving media message delivery through the WhatsApp channel have been successful. While the service behavior indicates signs of recovery, we are still awaiting official confirmation from the service provider regarding the root cause and full resolution of the issue. Our teams continue to closely monitor the situation and will provide further updates as soon as additional information becomes available.

4. resolved Jun 16, 2026, 07:03 PM UTC

   The incident affecting media message delivery through the WhatsApp channel has been resolved. We observed a significant reduction in errors starting at approximately 13:50 (GMT-3), and subsequent validation tests were completed successfully without further issues. After further investigation, Meta informed us that an internal issue related to its Forward Proxy service had been identified and resolved. The service has remained stable since then, and no new impacts have been observed. This incident is now considered resolved.

Read the full incident report →

Started May 05, 2026, 06:51 PM UTC· resolved May 05, 2026, 07:05 PM UTC

1. identified May 05, 2026, 06:51 PM UTC

   We have identified degradation in platform services, affecting internal service communication. Our team is already working on the issue resolution. This page will be updated as progress is made.

2. resolved May 05, 2026, 09:12 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 22, 2026, 01:37 PM UTC· resolved Apr 23, 2026, 11:24 AM UTC

1. investigating Apr 23, 2026, 11:49 AM UTC

   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.

2. resolved Apr 23, 2026, 12:05 PM UTC

   The issue affecting AI agents has been resolved after reverting recent changes, restoring normal functionality. The root cause is still under investigation, and we are continuing internal analysis to fully understand the scenario. No further impact is expected.

Read the full incident report →

Started Apr 08, 2026, 12:26 PM UTC· resolved Apr 08, 2026, 02:06 PM UTC

1. investigating Apr 08, 2026, 12:26 PM UTC

   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.

2. investigating Apr 08, 2026, 01:02 PM UTC

   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.

3. monitoring Apr 08, 2026, 01:45 PM UTC

   The issue affecting ticket distribution and performance on Blip Desk has been mitigated. Customers may have experienced difficulties receiving or handling tickets, as well as slowness when accessing the platform. A fix has been applied and the environment is now stable. Our team is monitoring to ensure continued stability.

4. resolved Apr 08, 2026, 02:06 PM UTC

   The issue affecting ticket distribution and performance on Blip Desk has been resolved. Customers experienced difficulties handling tickets and slowness when accessing the platform. The root cause was identified and corrected, and the service is now fully operational.

Read the full incident report →

Started Apr 02, 2026, 11:19 AM UTC· resolved Apr 02, 2026, 01:40 PM UTC

1. investigating Apr 02, 2026, 11:19 AM UTC

   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

2. identified Apr 02, 2026, 12:29 PM UTC

   We identified an ongoing issue affecting AI-powered bots, where responses to user interactions are not being returned. Actions have been applied to stabilize the environment, and our team is currently running tests and analysis to understand the behavior and restore normal functionality. The issue is still under investigation and may continue to impact users. We will provide a new update within 30 minutes or as soon as more information is available.

3. monitoring Apr 02, 2026, 01:13 PM UTC

   The issue affecting AI-powered bots has been mitigated after corrective actions were applied. The service is now operating normally, and we are actively monitoring the environment to ensure stability. We will provide further updates if necessary.

4. resolved Apr 02, 2026, 01:40 PM UTC

   The issue affecting AI-powered bots has been resolved. During the incident, users may have experienced missing responses from bots. The service is now fully restored and operating normally.

Read the full incident report →

Started Mar 02, 2026, 12:56 AM UTC· resolved Mar 02, 2026, 01:19 AM UTC

1. investigating Mar 02, 2026, 12:56 AM UTC

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

2. resolved Mar 02, 2026, 01:19 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 23, 2026, 01:19 PM UTC· resolved Feb 23, 2026, 08:01 PM UTC

1. investigating Feb 23, 2026, 01:19 PM UTC

   We are currently investigating an issue affecting contact search functionality within bots. Customers may experience failures when accessing the contacts tab or attempting to send active messages through Desk, as contact queries may not return results. Our technical team is actively analyzing the situation and working to restore normal operations as quickly as possible. We will provide a new update within 30 minutes or sooner if significant progress is made.

2. investigating Feb 23, 2026, 01:25 PM UTC

   We are currently investigating an issue affecting contact search functionality within bots. Customers may experience failures when accessing the contacts tab or attempting to send active messages through Desk, as contact queries may not return results. Our technical team is actively analyzing the situation and working to restore normal operations as quickly as possible. We will provide a new update within 30 minutes or sooner if significant progress is made.

3. identified Feb 23, 2026, 02:00 PM UTC

   We are still experiencing an ongoing issue affecting contact search functionality within bots. Customers may continue to face failures when accessing the contacts tab or attempting to send active messages through Desk. An initial emergency deployment was performed; however, the issue persisted. A new redeployment is currently in progress, and our engineering team remains fully engaged. We will provide a new update within 30 minutes or sooner if significant progress is made.

4. investigating Feb 23, 2026, 02:30 PM UTC

   We continue to investigate the issue affecting contact search functionality in bots. Customers may still experience failures when accessing the contacts tab or attempting to send active messages via Desk. Technical adjustments were previously applied; however, the behavior persists intermittently. Our engineering teams remain fully engaged, and the war room remains active as we continue to analyze the environment and define the next steps. We will provide another update within 30 minutes or sooner if significant progress is made.

5. monitoring Feb 23, 2026, 03:07 PM UTC

   The environment experienced intermittent instability throughout the morning, impacting contact search functionality in bots. At this time, the platform appears stable. We remain actively monitoring the environment to ensure sustained stability and will provide further updates if any relevant changes occur.

6. resolved Feb 23, 2026, 08:01 PM UTC

   The incident affecting contact search functionality in bots has been resolved. The root cause was identified as high resource consumption in the search component. After technical adjustments, performance indicators have remained within expected levels. We will continue monitoring the platform to ensure ongoing stability.

Read the full incident report →

Started Feb 03, 2026, 07:21 PM UTC· resolved Feb 03, 2026, 07:59 PM UTC

1. investigating Feb 03, 2026, 07:21 PM UTC

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

2. resolved Feb 03, 2026, 07:59 PM UTC

   The incident has been resolved. We observed that the environment remained stable and we did not find any other errors.

Read the full incident report →

Started Jan 20, 2026, 01:31 PM UTC· resolved Jan 22, 2026, 05:16 PM UTC

1. investigating Jan 20, 2026, 01:31 PM UTC

   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.

2. resolved Jan 21, 2026, 09:01 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 19, 2026, 11:40 AM UTC· resolved Jan 20, 2026, 01:00 AM UTC

1. identified Jan 19, 2026, 12:37 PM UTC

   We have identified an instability that prevents the contacts tab from loading on the Portal and Desk

2. identified Jan 19, 2026, 12:42 PM UTC

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

3. identified Jan 19, 2026, 02:21 PM UTC

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

4. monitoring Jan 19, 2026, 03:54 PM UTC

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

5. monitoring Jan 19, 2026, 07:19 PM UTC

   We are continuing to monitor for any further issues.

6. resolved Jan 20, 2026, 08:52 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 19, 2025, 12:33 PM UTC· resolved Dec 19, 2025, 02:14 PM UTC

1. monitoring Dec 19, 2025, 12:33 PM UTC

   We have identified instability on the blip portal due to a failure in the provider's servers. Customers may experience slow speeds or failures accessing the blip and Desk portals

2. resolved Dec 19, 2025, 02:14 PM UTC

   The incident has been removed from the vendor's Status Page. The environment remains stable.

Read the full incident report →

Started Dec 11, 2025, 02:26 PM UTC· resolved Dec 11, 2025, 02:26 PM UTC

1. resolved Dec 11, 2025, 02:26 PM UTC

   What happened and what was the impact on customers: We identified a failure in the AI application. As a result, customers experienced a failure in the messages from the AI-powered bots. Actions taken: Update of the expired token Restart Rollout in all pods Monitoring of metrics after restarts Failure occurrences: Start of failure: 11/12/2025 8:10 AM (GMT-3) Fault resolution: 11/12/2025 10:10 AM (GMT-3) Root cause The failure was caused by instabilities resulting from expired credentials on an external service, which temporarily impacted the bot's operation.

Read the full incident report →

Started Dec 10, 2025, 01:46 PM UTC· resolved Dec 10, 2025, 04:00 PM UTC

1. investigating Dec 10, 2025, 03:48 PM UTC

   We are currently investigating this issue.

2. identified Dec 10, 2025, 03:57 PM UTC

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

3. monitoring Dec 10, 2025, 03:57 PM UTC

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

4. monitoring Dec 10, 2025, 04:21 PM UTC

   We are continuing to monitor for any further issues.

5. resolved Dec 10, 2025, 04:22 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 10, 2025, 12:15 PM UTC· resolved Dec 10, 2025, 01:05 PM UTC

1. investigating Dec 10, 2025, 01:48 PM UTC

   We are currently investigating this issue.

2. resolved Dec 10, 2025, 02:04 PM UTC

   This incident has been resolved.

Read the full incident report →