Blip Outage History

Blip is up right now

Blip had 45 outages in the last 2 years totaling 151h 47m of downtime — averaging 1.8 incidents per month.

There were 45 Blip outages since December 5, 2024 totaling 151h 47m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.blip.ai

Major June 23, 2026

Slow message sending and media sending failures

Detected by Pingoru
Jun 23, 2026, 11:09 PM UTC
Resolved
Jun 24, 2026, 12:40 AM UTC
Duration
1h 30m
Affected: WhatsApp
Timeline · 3 updates
  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 →

Minor June 16, 2026

WhatsApp Media Sending Instability

Detected by Pingoru
Jun 16, 2026, 02:40 PM UTC
Resolved
Jun 16, 2026, 07:03 PM UTC
Duration
4h 23m
Affected: WhatsAppDesk
Timeline · 4 updates
  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 →

Minor June 12, 2026

Degradation in WhatsApp message delivery service

Detected by Pingoru
Jun 12, 2026, 01:30 PM UTC
Resolved
Jun 12, 2026, 06:15 PM UTC
Duration
4h 45m
Affected: WhatsApp
Timeline · 4 updates
  1. 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.

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

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

  4. resolved Jun 12, 2026, 06:30 PM UTC

    The Meta API has been restored: https://metastatus.com/whatsapp-business-api

Read the full incident report →

Notice May 5, 2026

Degradation in platform services

Detected by Pingoru
May 05, 2026, 06:51 PM UTC
Resolved
May 05, 2026, 07:05 PM UTC
Duration
13m
Affected: Core
Timeline · 2 updates
  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 →

Critical April 22, 2026

Instability in AI Agents Responses

Detected by Pingoru
Apr 22, 2026, 01:37 PM UTC
Resolved
Apr 23, 2026, 11:24 AM UTC
Duration
21h 47m
Affected: Artificial Intelligence
Timeline · 2 updates
  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 →

Critical April 8, 2026

Ticket Distribution Instability on Blip Desk

Detected by Pingoru
Apr 08, 2026, 12:26 PM UTC
Resolved
Apr 08, 2026, 02:06 PM UTC
Duration
1h 39m
Affected: Desk
Timeline · 4 updates
  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 →

Critical April 2, 2026

AI Response Failure on Blip Studio Bots

Detected by Pingoru
Apr 02, 2026, 11:19 AM UTC
Resolved
Apr 02, 2026, 01:40 PM UTC
Duration
2h 20m
Affected: Artificial Intelligence
Timeline · 4 updates
  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 →

Major March 2, 2026

BlipChat [Low performance]

Detected by Pingoru
Mar 02, 2026, 12:56 AM UTC
Resolved
Mar 02, 2026, 01:19 AM UTC
Duration
23m
Affected: BlipChat
Timeline · 2 updates
  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 →

Notice February 3, 2026

WhatsApp [Low performance]

Detected by Pingoru
Feb 03, 2026, 07:21 PM UTC
Resolved
Feb 03, 2026, 07:59 PM UTC
Duration
38m
Affected: WhatsApp
Timeline · 2 updates
  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 →

Minor January 20, 2026

Slow Loading Time - Contact Tab

Detected by Pingoru
Jan 20, 2026, 01:31 PM UTC
Resolved
Jan 22, 2026, 05:16 PM UTC
Duration
2d 3h
Affected: DeskPortal
Timeline · 2 updates
  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 →

Minor January 19, 2026

Problem loading contacts

Detected by Pingoru
Jan 19, 2026, 11:40 AM UTC
Resolved
Jan 20, 2026, 01:00 AM UTC
Duration
13h 19m
Affected: CRMDeskPortal
Timeline · 6 updates
  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 →

Minor December 19, 2025

Instability on the blip portal due to a failure in the provider's servers

Detected by Pingoru
Dec 19, 2025, 12:33 PM UTC
Resolved
Dec 19, 2025, 02:14 PM UTC
Duration
1h 41m
Affected: DeskPortal
Timeline · 2 updates
  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 →

Notice December 11, 2025

Failure in the AI application

Detected by Pingoru
Dec 11, 2025, 02:26 PM UTC
Resolved
Dec 11, 2025, 02:26 PM UTC
Duration
—
Affected: Artificial Intelligence
Timeline · 1 update
  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 →

Minor December 10, 2025

Lentidão no fluxo de mensagens do Whatsapp

Detected by Pingoru
Dec 10, 2025, 01:46 PM UTC
Resolved
Dec 10, 2025, 04:00 PM UTC
Duration
2h 14m
Affected: WhatsApp
Timeline · 5 updates
  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 →

Minor December 10, 2025

Lentidão para acesso ao portal e desk

Detected by Pingoru
Dec 10, 2025, 12:15 PM UTC
Resolved
Dec 10, 2025, 01:05 PM UTC
Duration
49m
Affected: WhatsAppDeskPortal
Timeline · 2 updates
  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 →

Minor December 5, 2025

Instability on the Blip portal due to a provider outage.

Detected by Pingoru
Dec 05, 2025, 09:24 AM UTC
Resolved
Dec 05, 2025, 11:01 AM UTC
Duration
1h 36m
Affected: WhatsAppBot BuilderCRMDeskBot BuilderTelegramCoreBot RouterBot RouterMessengerAnalyticsBlipChatArtificial IntelligenceWorkplace ChatBusinessChatPortalSkypeCloud InfrastructureE-mailInstagram
Timeline · 3 updates
  1. investigating Dec 05, 2025, 09:24 AM UTC

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

  2. monitoring Dec 05, 2025, 09:47 AM UTC

    Back to normal! We are monitoring the situation. We will provide updates soon.

  3. resolved Dec 05, 2025, 11:01 AM UTC

    This incident has been resolved.

Read the full incident report →

Major December 4, 2025

Problema na busca pelo histórico de contatos

Detected by Pingoru
Dec 04, 2025, 11:30 AM UTC
Resolved
Dec 04, 2025, 02:10 PM UTC
Duration
2h 40m
Affected: Desk
Timeline · 2 updates
  1. investigating Dec 10, 2025, 02:41 PM UTC

    We are currently investigating this issue.

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

    This incident has been resolved.

Read the full incident report →

Minor November 24, 2025

Problema na busca por contatos

Detected by Pingoru
Nov 24, 2025, 01:11 PM UTC
Resolved
Nov 24, 2025, 07:27 PM UTC
Duration
6h 15m
Affected: CRMDeskPortal
Timeline · 4 updates
  1. investigating Nov 24, 2025, 01:12 PM UTC

    We are currently investigating this issue.

  2. investigating Nov 24, 2025, 02:09 PM UTC

    We are continuing to investigate this issue.

  3. identified Nov 24, 2025, 02:58 PM UTC

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

  4. resolved Nov 24, 2025, 07:27 PM UTC

    O cenário foi normalizado e uma solução para mitigar problemas futuros está sendo desenvolvida.

Read the full incident report →

Minor November 6, 2025

Duplicate messages being delivered on Whatsapp

Detected by Pingoru
Nov 06, 2025, 11:00 AM UTC
Resolved
Nov 06, 2025, 03:27 PM UTC
Duration
4h 27m
Affected: Desk
Timeline · 4 updates
  1. investigating Nov 06, 2025, 12:46 PM UTC

    We are currently investigating this issue.

  2. investigating Nov 06, 2025, 01:42 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Nov 06, 2025, 02:28 PM UTC

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

  4. resolved Nov 06, 2025, 03:27 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical October 29, 2025

Portal and Desk Outage

Detected by Pingoru
Oct 29, 2025, 04:26 PM UTC
Resolved
Oct 30, 2025, 12:05 AM UTC
Duration
7h 38m
Affected: DeskPortal
Timeline · 6 updates
  1. investigating Oct 29, 2025, 04:18 PM UTC

    We are currently investigating this issue.

  2. identified Oct 29, 2025, 04:26 PM UTC

    Global problem with Azure Cloud

  3. identified Oct 29, 2025, 04:32 PM UTC

    Global problem with Azure Cloud affecting Blip Portal and Blip Desk

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

  5. monitoring Oct 29, 2025, 11:14 PM UTC

    We are continuing to monitor for any further issues.

  6. resolved Oct 30, 2025, 12:41 AM UTC

    This incident has been resolved.

Read the full incident report →

Major August 30, 2025

Conversational Flow [Low Performace]

Detected by Pingoru
Aug 30, 2025, 09:30 PM UTC
Resolved
Aug 30, 2025, 11:26 PM UTC
Duration
1h 56m
Affected: Bot BuilderBot Router
Timeline · 4 updates
  1. investigating Aug 30, 2025, 10:32 PM UTC

    We're currently experiencing poor performance in conversational flow. Impact: Offline Bots

  2. investigating Aug 30, 2025, 10:32 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Aug 30, 2025, 10:54 PM UTC

    A fix has been implemented and we are monitoring.

  4. resolved Aug 30, 2025, 11:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 22, 2025

Blip Desk & Growth [Low performance]

Detected by Pingoru
Aug 22, 2025, 11:30 AM UTC
Resolved
Aug 22, 2025, 03:55 PM UTC
Duration
4h 25m
Affected: DeskBlipChat
Timeline · 3 updates
  1. investigating Aug 22, 2025, 02:01 PM UTC

    We are currently experiencing low performance on Blip Desk and Growth. Impact: Inability to forward active messages Update: Our support team is actively working on it.

  2. investigating Aug 22, 2025, 02:02 PM UTC

    We are continuing to investigate this issue.

  3. resolved Aug 22, 2025, 03:55 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 11, 2025

Blip Desk [Degradation]

Detected by Pingoru
Aug 11, 2025, 12:05 PM UTC
Resolved
Aug 11, 2025, 06:27 PM UTC
Duration
6h 21m
Affected: CRMDesk
Timeline · 5 updates
  1. investigating Aug 11, 2025, 12:42 PM UTC

    We are currently experiencing low performance on Blip Desk. Impact: Failures in active message delivery. Update: Our support team is actively working on it.

  2. investigating Aug 11, 2025, 04:22 PM UTC

    Dear Customers, We are continuing to investigate the matter and will provide updates shortly regarding the current situation.

  3. investigating Aug 11, 2025, 05:37 PM UTC

    Dear Customers, The issue currently persists on a small scale; however, the Blip Desk environment remains stable. Our team continues to investigate, and we will share further updates shortly.

  4. monitoring Aug 11, 2025, 05:53 PM UTC

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

  5. resolved Aug 11, 2025, 06:27 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 30, 2025

Desk & BlipChat [Degradation]

Detected by Pingoru
Jul 30, 2025, 02:30 PM UTC
Resolved
Jul 30, 2025, 04:38 PM UTC
Duration
2h 8m
Affected: Desk
Timeline · 5 updates
  1. investigating Jul 30, 2025, 03:08 PM UTC

    We are currently experiencing degradatin on BlipChat and Desk. Impact: Degradation in BlipChat and Desk. Update: Our support team is actively working on it.

  2. identified Jul 30, 2025, 03:33 PM UTC

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

  3. identified Jul 30, 2025, 03:55 PM UTC

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

  4. monitoring Jul 30, 2025, 04:11 PM UTC

    We are currently experiencing degradation in BlipChat and Desk. Impact: Users may experience degraded performance in BlipChat and Desk. Update: Our support team has acted to stabilize the environment, and we are now monitoring the situation.

  5. resolved Jul 30, 2025, 04:38 PM UTC

    Incident Resolved ? BlipChat and Desk Impact: Users may have experienced degraded performance in BlipChat and Desk. Final Update: The issue has been fully resolved. Our team has stabilized the environment, and BlipChat and Desk are operating normally. We will continue to monitor to ensure continued stability.

Read the full incident report →