Blip Status

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

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

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

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

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

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

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

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

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

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

Investigating: Engineering teams continue to treat this as a top priority and have made progress in their investigation, expanding their analysis of the components responsible for message processing.

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

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

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

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

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

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

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

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

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