Blip Outage History
Blip is up right nowBlip had 46 outages in the last 2 years totaling 626h 25m of downtime — averaging 1.9 incidents per month.
There were 46 Blip outages since December 10, 2024 totaling 626h 25m of downtime. Each is summarised below — incident details, duration, and resolution information.
Slowness or delays in bot responses
Timeline · 2 updates
- 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.
- 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.
Message visibility issues in Blip Desk and Portal
Timeline · 15 updates
Pausa temporária no envio de mensagens via BSUID
Timeline · 4 updates
- 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.
- 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.
- 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.
- 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
Slow message sending and media sending failures
Timeline · 3 updates
- 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.
- monitoring Jun 23, 2026, 11:25 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 24, 2026, 12:40 AM UTC
This incident has been resolved.
WhatsApp Media Sending Instability
Timeline · 4 updates
- 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.
- 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.
- 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.
- 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.
Degradation in WhatsApp message delivery service
Timeline · 4 updates
- investigating Jun 12, 2026, 02:31 PM 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.
- identified Jun 12, 2026, 02:34 PM UTC
We are currently experiencing high disruptions impacting WhatsApp Cloud API. Our engineering teams are investigating the issue. We will provide another update within 1 hour or sooner if additional information is available.
- identified Jun 12, 2026, 03:57 PM UTC
We are experiencing instability on Meta's end, as reported by the provider itself in its official communications. We are continuing to monitor the incident's progress with Meta and tracking the impact on customers.
- resolved Jun 12, 2026, 06:30 PM UTC
The Meta API has been restored: https://metastatus.com/whatsapp-business-api
Degradation in platform services
Timeline · 2 updates
- 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.
- resolved May 05, 2026, 09:12 PM UTC
This incident has been resolved.
Instability in AI Agents Responses
Timeline · 2 updates
- 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.
- 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.
Ticket Distribution Instability on Blip Desk
Timeline · 4 updates
- 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.
- 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.
- 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.
- 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.
AI Response Failure on Blip Studio Bots
Timeline · 4 updates
- 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
- 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.
- 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.
- 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.
BlipChat [Low performance]
Timeline · 2 updates
- 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.
- resolved Mar 02, 2026, 01:19 AM UTC
This incident has been resolved.
Contact Search Failure on Bots
Timeline · 6 updates
WhatsApp [Low performance]
Timeline · 2 updates
- 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.
- 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.
Slow Loading Time - Contact Tab
Timeline · 2 updates
- 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.
- resolved Jan 21, 2026, 09:01 PM UTC
This incident has been resolved.
Problem loading contacts
Timeline · 6 updates
- 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
- identified Jan 19, 2026, 12:42 PM UTC
We are continuing to work on a fix for this issue.
- identified Jan 19, 2026, 02:21 PM UTC
We are continuing to work on a fix for this issue.
- monitoring Jan 19, 2026, 03:54 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Jan 19, 2026, 07:19 PM UTC
We are continuing to monitor for any further issues.
- resolved Jan 20, 2026, 08:52 AM UTC
This incident has been resolved.
Instability on the blip portal due to a failure in the provider's servers
Timeline · 2 updates
- 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
- resolved Dec 19, 2025, 02:14 PM UTC
The incident has been removed from the vendor's Status Page. The environment remains stable.
Failure in the AI application
Timeline · 1 update
- 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.
Lentidão no fluxo de mensagens do Whatsapp
Timeline · 5 updates
- investigating Dec 10, 2025, 03:48 PM UTC
We are currently investigating this issue.
- identified Dec 10, 2025, 03:57 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Dec 10, 2025, 03:57 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Dec 10, 2025, 04:21 PM UTC
We are continuing to monitor for any further issues.
- resolved Dec 10, 2025, 04:22 PM UTC
This incident has been resolved.
Lentidão para acesso ao portal e desk
Timeline · 2 updates
- investigating Dec 10, 2025, 01:48 PM UTC
We are currently investigating this issue.
- resolved Dec 10, 2025, 02:04 PM UTC
This incident has been resolved.
Instability on the Blip portal due to a provider outage.
Timeline · 3 updates
- investigating Dec 05, 2025, 09:24 AM UTC
We have identified an instability in the Blip portal due to a service provider failure.
- monitoring Dec 05, 2025, 09:47 AM UTC
Back to normal! We are monitoring the situation. We will provide updates soon.
- resolved Dec 05, 2025, 11:01 AM UTC
This incident has been resolved.
Problema na busca pelo histórico de contatos
Timeline · 2 updates
- investigating Dec 10, 2025, 02:41 PM UTC
We are currently investigating this issue.
- resolved Dec 10, 2025, 02:41 PM UTC
This incident has been resolved.
Problema na busca por contatos
Timeline · 4 updates
- investigating Nov 24, 2025, 01:12 PM UTC
We are currently investigating this issue.
- investigating Nov 24, 2025, 02:09 PM UTC
We are continuing to investigate this issue.
- identified Nov 24, 2025, 02:58 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Nov 24, 2025, 07:27 PM UTC
O cenário foi normalizado e uma solução para mitigar problemas futuros está sendo desenvolvida.
Duplicate messages being delivered on Whatsapp
Timeline · 4 updates
- investigating Nov 06, 2025, 12:46 PM UTC
We are currently investigating this issue.
- investigating Nov 06, 2025, 01:42 PM UTC
We are continuing to investigate this issue.
- monitoring Nov 06, 2025, 02:28 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Nov 06, 2025, 03:27 PM UTC
This incident has been resolved.
Portal and Desk Outage
Timeline · 6 updates
- investigating Oct 29, 2025, 04:18 PM UTC
We are currently investigating this issue.
- identified Oct 29, 2025, 04:26 PM UTC
Global problem with Azure Cloud
- identified Oct 29, 2025, 04:32 PM UTC
Global problem with Azure Cloud affecting Blip Portal and Blip Desk
- monitoring Oct 29, 2025, 09:24 PM UTC
We are monitoring our provider's performance in restoring the services. During this period, access may work intermittently. We will continue monitoring until complete normalization.
- monitoring Oct 29, 2025, 11:14 PM UTC
We are continuing to monitor for any further issues.
- resolved Oct 30, 2025, 12:41 AM UTC
This incident has been resolved.