Blip Outage History

Blip is up right now

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

There were 45 Blip outages since November 28, 2024 totaling 167h 14m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.blip.ai

Major June 9, 2025

Blip Desk [Fail while sending messages]

Detected by Pingoru
Jun 09, 2025, 12:15 PM UTC
Resolved
Jun 09, 2025, 02:30 PM UTC
Duration
2h 15m
Affected: Desk
Timeline · 6 updates
  1. investigating Jun 09, 2025, 01:01 PM UTC

    Blip Desk is not responding. Impact: Blip Desk may fail while sending messages. Update: Our support team is actively working on it.

  2. investigating Jun 09, 2025, 01:20 PM UTC

    We are continuing to investigate this issue.

  3. identified Jun 09, 2025, 01:55 PM UTC

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

  4. monitoring Jun 09, 2025, 01:55 PM UTC

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

  5. monitoring Jun 09, 2025, 01:55 PM UTC

    We are continuing to monitor for any further issues.

  6. resolved Jun 09, 2025, 02:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 6, 2025

Chatbot Builder [Low performance]

Detected by Pingoru
May 06, 2025, 11:00 AM UTC
Resolved
May 06, 2025, 01:30 PM UTC
Duration
2h 29m
Affected: Bot BuilderBot Builder
Timeline · 3 updates
  1. investigating May 06, 2025, 01:15 PM UTC

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

  2. identified May 06, 2025, 01:22 PM UTC

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

  3. resolved May 06, 2025, 01:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 17, 2025

[INFORMATIVE] -WhatsApp Business API Status

Detected by Pingoru
Apr 17, 2025, 12:21 AM UTC
Resolved
Apr 21, 2025, 06:45 AM UTC
Duration
4d 6h
Timeline · 2 updates
  1. identified Apr 17, 2025, 12:21 AM UTC

    Our engineering teams have identified the root cause of the low disruptions impacting WhatsApp Android app crashes for catalogs on WHATSAPP BUSINESS CLOUD API. We are currently deploying the fix and will provide another update within 24 hours or sooner if additional information is available. Official status Partner: https://metastatus.com/ Official status Partner: https://metastatus.com/whatsapp-business-api

  2. resolved Apr 21, 2025, 06:45 AM UTC

    The service is up and running with no known issues. Official status Partner: https://metastatus.com/whatsapp-business-api

Read the full incident report →

Major March 26, 2025

Blip - [Failure to use Growth]

Detected by Pingoru
Mar 26, 2025, 11:25 AM UTC
Resolved
Mar 26, 2025, 03:37 PM UTC
Duration
4h 12m
Affected: Agendador
Timeline · 3 updates
  1. investigating Mar 26, 2025, 02:02 PM UTC

    We have identified an error when uploading spreadsheets via Growth. Impact: Failure to send bulk active messages via Growth. Update: Our support team is actively working on this.

  2. identified Mar 26, 2025, 02:02 PM UTC

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

  3. resolved Mar 26, 2025, 03:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 25, 2025

Slowness and instability on the Blip platform.

Detected by Pingoru
Mar 25, 2025, 03:44 PM UTC
Resolved
Mar 25, 2025, 02:30 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Mar 25, 2025, 03:44 PM UTC

    Start Time: 25/03/2025 ~11:38 (GMT-3) End Time: 25/03/2025 ~11:47 (GMT-3) Incident Summary: Slowness and instability on the Blip platform. Impact Analysis: Slowness and instability, both in the service monitoring tools and in the Desk itself. Mitigation Measures: To reduce the high processing consumption of the Desk system, it was necessary to temporarily switch to a backup environment and optimize the database. These actions help stabilize performance and minimize impacts to users. Root Cause Analysis: In the face of the normalization of the environment, we classify the incident as resolved and now enter the root cause analysis stage. This process will be conducted internally, as quickly as the situation requires, and will be published here on the status page as soon as possible. If you have any questions or need additional clarification, we recommend that you contact the CSM of your account for support.

Read the full incident report →

Major March 20, 2025

Builder - [Failed to publish stream]

Detected by Pingoru
Mar 20, 2025, 07:00 AM UTC
Resolved
Mar 20, 2025, 10:50 AM UTC
Duration
3h 50m
Affected: Bot BuilderBot Builder
Timeline · 3 updates
  1. investigating Mar 20, 2025, 10:44 AM UTC

    Dear Customers, We are currently experiencing an issue with Builder. Impact: The attempt to publish the flow failed. Update: Our support team is actively working on it.

  2. identified Mar 20, 2025, 10:44 AM UTC

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

  3. resolved Mar 20, 2025, 11:00 AM UTC

    This incident has been resolved.

Read the full incident report →

Major March 5, 2025

Blip Desk [Failed to save queues and pause appointments]

Detected by Pingoru
Mar 05, 2025, 11:45 PM UTC
Resolved
Mar 06, 2025, 02:55 AM UTC
Duration
3h 9m
Timeline · 4 updates
  1. investigating Mar 06, 2025, 01:20 AM UTC

    Incident summary: When trying to save queues and pause appointments in the application Desk, customers are met with an error return, which makes it impossible to take action. Start time: 03/05/2025 Impact for customers: Error to save queues and pause appointments in the application Desk Next update: In one hour or when a new relevant fact is identified.

  2. identified Mar 06, 2025, 01:44 AM UTC

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

  3. monitoring Mar 06, 2025, 02:53 AM UTC

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

  4. resolved Mar 06, 2025, 02:55 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 26, 2025

Failed to extract data in the report manager

Detected by Pingoru
Feb 26, 2025, 04:35 PM UTC
Resolved
Feb 26, 2025, 06:03 PM UTC
Duration
1h 27m
Affected: Analytics
Timeline · 3 updates
  1. investigating Feb 26, 2025, 04:35 PM UTC

    Incident summary: When attempting to generate reports in report manager, customers encounter an error return, making it impossible to generate the reports. Start time: 02/25/2025 Impact for customers: Error to generate report in report manager Next update: In one hour or when a new relevant fact is identified.

  2. monitoring Feb 26, 2025, 05:22 PM UTC

    We have identified that the current scenario was occurring as a result of a change in the read access permissions of the user in the data tool from which the report is extracted. Actions to be carried out: The mentioned read user access privilege has been corrected. We are validating and monitoring the environment

  3. resolved Feb 26, 2025, 06:03 PM UTC

    Incident summary: When attempting to generate reports in report manager, customers encounter an error return, making it impossible to generate the reports. We have identified that the current scenario was occurring as a result of a change in the read access permissions of the user in the data tool from which the report is extracted. Start time: 02/25/2025 10:30 AM (GMT -3) End time: 02/26/2025 2:00 PM (GMT -3) Impact for customers: Error to generate report in report manager Actions performed: The mentioned read user access privilege has been corrected at 01:56 PM and finished at 2:00 PM. Current state: At the moment, all resources and applications are fully operational and within operability standards. Next steps: We will continue with internal investigations to determine the root cause that led to this incident and will make the details available in the postmortem right here on our status page.

Read the full incident report →

Minor February 25, 2025

Blip [Fail while sending active messages]

Detected by Pingoru
Feb 25, 2025, 11:20 AM UTC
Resolved
Feb 25, 2025, 01:25 PM UTC
Duration
2h 4m
Affected: Desk
Timeline · 4 updates
  1. investigating Feb 25, 2025, 01:27 PM UTC

    Dear customers, We've identified intermittent errors when sending active messages via Growth/Desk. Our support team is actively working on it.

  2. identified Feb 25, 2025, 01:27 PM UTC

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

  3. resolved Feb 25, 2025, 01:48 PM UTC

    This incident has been resolved.

  4. postmortem Feb 27, 2025, 05:54 PM UTC

    Start time: 02/25/2025 07:10 AM \(GMT -3\) End time: 02/25/2025 10:26 AM \(GMT -3\) Incident summary: The agents were encountering errors when trying to send messages through the Growth and the Desk application. Root cause Analysis: The root cause is related to a specific change in the Active Messages application. To address this, we rolled back the change and then implemented a correction.

Read the full incident report →

Minor February 5, 2025

Blip Speech [Degradation]

Detected by Pingoru
Feb 05, 2025, 03:00 AM UTC
Resolved
Feb 05, 2025, 07:50 PM UTC
Duration
16h 50m
Affected: Artificial Intelligence
Timeline · 2 updates
  1. investigating Feb 05, 2025, 04:21 AM UTC

    Dear Customer, We have identified an inconsistency in Blip Speech related to audio transcription. The responsible team is already investigating the issue and working to resolve it as quickly as possible. During this period, unexpected responses may occur when sending audio.

  2. resolved Feb 05, 2025, 07:50 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 29, 2025

Channel WhatsApp Instability

Detected by Pingoru
Jan 29, 2025, 02:35 AM UTC
Resolved
Jan 29, 2025, 03:53 AM UTC
Duration
1h 18m
Affected: WhatsApp
Timeline · 3 updates
  1. investigating Jan 29, 2025, 02:35 AM UTC

    Identified instability affecting WhatsApp channel, The technical team is assessing the source of the fault.

  2. identified Jan 29, 2025, 03:41 AM UTC

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

  3. resolved Jan 29, 2025, 03:53 AM UTC

    Our technical team identified and fixed the error that was affecting the WhatsApp channel. We apologize for the inconvenience caused!

Read the full incident report →

Minor January 22, 2025

Blip Desk [Low performance]

Detected by Pingoru
Jan 22, 2025, 10:20 AM UTC
Resolved
Jan 22, 2025, 05:16 PM UTC
Duration
6h 55m
Affected: Desk
Timeline · 4 updates
  1. investigating Jan 22, 2025, 11:24 AM UTC

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

  2. identified Jan 22, 2025, 11:33 AM UTC

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

  3. monitoring Jan 22, 2025, 11:34 AM UTC

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

  4. resolved Jan 22, 2025, 05:16 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 16, 2025

Blip Desk [Slowness in sending messages]

Detected by Pingoru
Jan 16, 2025, 11:00 AM UTC
Resolved
Jan 16, 2025, 01:42 PM UTC
Duration
2h 42m
Affected: Desk
Timeline · 5 updates
  1. investigating Jan 16, 2025, 11:23 AM UTC

    Dear customers, We identified that Blip Desk is experiencing slow forwarding and failure to exchange messages. We also noticed that message history loading was impacted. To update: Our support and engineering team has been activated and is actively working on this.

  2. investigating Jan 16, 2025, 11:23 AM UTC

    We are continuing to investigate this issue.

  3. identified Jan 16, 2025, 12:22 PM UTC

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

  4. monitoring Jan 16, 2025, 12:29 PM UTC

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

  5. resolved Jan 16, 2025, 01:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice December 11, 2024

[INFORMATIVE] - WhatsApp Possible Unavailability

Detected by Pingoru
Dec 11, 2024, 06:00 PM UTC
Resolved
Dec 12, 2024, 04:21 AM UTC
Duration
10h 21m
Timeline · 4 updates
  1. investigating Dec 11, 2024, 06:44 PM UTC

    Dear customers, We noticed a high volume of crashes reported in Downdetector coming from META services. Official Downdetector Source: -WhatsApp https://downdetector.com.br/fora-do-ar/whatsapp/?_gl=1*1wbmqru*_up*MQ..*_ga*NTUwOD UxNjQ2LjE3MzM5NDEyMzE.*_ga_0PZM58H213*MTczMzk0MTIzMC4xLjAuMTczMzk0MTIzMC4wLjAuMA.. So far, we do not have an official position on it. However, we will continue to monitor. Official Meta Source: https://metastatus.com/?trk=public_post-text

  2. identified Dec 11, 2024, 09:17 PM UTC

    Dear customers, last updates. Partner information: We are currently experiencing major disruptions impacting message delivery on WhatsApp Business Management API. This issue started at 9:58 AM PST. Our engineering teams are investigating the issue. We will provide another update within 1 hour or sooner if additional information is available. https://metastatus.com/ https://metastatus.com/whatsapp-business-api

  3. monitoring Dec 12, 2024, 01:57 AM UTC

    Dear customers, last updates META. We will following monitoring. Partner information: We have recovered from an earlier outage impacting Cloud API, and services have now been restored. We apologize for any inconvenience that this may have caused. Official status Partner: https://metastatus.com/ Official status Partner: https://metastatus.com/whatsapp-business-api

  4. resolved Dec 12, 2024, 04:21 AM UTC

    We have recovered from previous disruptions affecting the service. We apologize for the inconvenience. https://metastatus.com/ctx

Read the full incident report →

Notice December 10, 2024

Desk and WhatsApp failures

Detected by Pingoru
Dec 10, 2024, 06:00 PM UTC
Resolved
Dec 10, 2024, 06:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Dec 10, 2024, 07:39 PM UTC

    Start Time: 10/12/2024 15:15 (GMT-3) End Time: 10/12/2024 15:19 (GMT-3) Incident Summary: Failure to send message on Desk and crash during interaction with chatbots via WhatsApp. Impact Analysis: From 15:15 to 15:19 (GMT -3) today, 10/12, we noticed that smart contacts connected to the WhatsApp channel crashed during interaction with users and on Desk, Blip's customer service tool, agents experienced "Failed to send message" errors. Mitigation Measures: The application was restored without direct intervention from Blip. Root Cause Analysis: In the face of the normalization of the environment, we classify the incident as resolved and now enter the root cause analysis stage. This process will be conducted internally, as quickly as the situation requires, and will be published here on the status page as soon as possible.

Read the full incident report →

Minor December 10, 2024

Builder [Low performance]

Detected by Pingoru
Dec 10, 2024, 12:10 PM UTC
Resolved
Dec 10, 2024, 01:32 PM UTC
Duration
1h 22m
Affected: Bot BuilderBot Builder
Timeline · 5 updates
  1. investigating Dec 10, 2024, 12:50 PM UTC

    Conversational flow failure. Impact: An instability was identified in the Builder, causing errors in sending messages and responses. Status: Our support team is actively working on it.

  2. identified Dec 10, 2024, 12:51 PM UTC

    Impact Analysis: In short, the platform presented flaws in the conversational flow between the client and the bot and vice versa. It is important to highlight that the situation did not affect all users.

  3. monitoring Dec 10, 2024, 01:26 PM UTC

    Mitigation Measures: We identified the reason for the failure in our application and corrected it immediately. Soon after, we noticed that the error logs stopped, reducing the recovery time of the application.

  4. resolved Dec 10, 2024, 01:32 PM UTC

    This incident has been resolved.

  5. postmortem Dec 10, 2024, 01:33 PM UTC

    **Start Time:** 09/12/2024 22:02 \(GMT-3\) **End Time:** 10/12/2024 ~09:49 \(GMT-3\) **Incident Summary:** Conversational flow failure. **Impact Analysis:** In short, the platform presented flaws in the conversational flow between the client and the bot and vice versa. It is important to highlight that the situation did not affect all users. **Mitigation Measures:** We identified the reason for the failure in our application and corrected it immediately. Soon after, we noticed that the error logs stopped, reducing the recovery time of the application. **Root Cause Analysis:** In the face of the normalization of the environment, we classify the incident as resolved and now enter the root cause analysis stage. This process will be conducted internally, as quickly as the situation requires, and will be published here on the status page as soon as possible.

Read the full incident report →

Minor December 6, 2024

Ação de exclusão no builder

Detected by Pingoru
Dec 06, 2024, 05:44 PM UTC
Resolved
Dec 06, 2024, 08:02 PM UTC
Duration
2h 17m
Affected: Portal
Timeline · 3 updates
  1. investigating Dec 06, 2024, 05:44 PM UTC

    Incident summary: We identified that the delete action within builder blocks is not working correctly Start time: ~08:45 am (GMT -3) Impact for customers: The failure causes the absence of the option to delete certain content. Next update: Our support team is actively working on this.

  2. identified Dec 06, 2024, 06:08 PM UTC

    We validate that the current scenario is occurring as a result of an update to one of our components responsible for applying the builder. Actions to be carried out: A correction update will be made so that the scenario is normalized. Next update: In thirty minutes or when a new relevant fact is identified.

  3. resolved Dec 06, 2024, 08:02 PM UTC

    Resumo do incidente: We validate that the current scenario is occurring as a result of an update to one of our components responsible for applying the builder Start time: ~08:45 am (GMT -3) End time:~16:45 pm (GMT -3) Impact for customers: Actions performed: We rolled back the application to a previous version due to the reported scenario. This action was necessary to ensure continuity of service Current state: At the moment, all of the construction company's resources are fully operational and within operational standards. Next steps: Given the normalization of the environment, we classified the incident as resolved and now we enter the root cause analysis stage. This process will be conducted internally, as quickly as the situation requires, and will be published here on the status page as soon as possible. If you have any questions or need additional clarification, we recommend that you contact your account CSM for support.

Read the full incident report →

Notice December 6, 2024

Blank Custom Reports

Detected by Pingoru
Dec 06, 2024, 02:44 PM UTC
Resolved
Dec 06, 2024, 11:30 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Dec 06, 2024, 02:44 PM UTC

    Start Time: 06/12/2024 ~08:30 (GMT-3) End Time: 06/12/2024 11:05 (GMT-3) Incident Summary: Event log data was not appearing in custom reports under the analysis tab. Impact Analysis: Inability to view records and personalized data within the Bot Portal. Mitigation Measures: We identified the reason for the failure in our application and immediately corrected it. In testing, we validated that the data was displayed again, as expected. Root Cause Analysis: In the face of the normalization of the environment, we classify the incident as resolved and now enter the root cause analysis stage. This process will be conducted internally, as quickly as the situation requires, and will be published here on the status page as soon as possible. If you have any questions or need additional clarification, we recommend that you contact the CSM of your account for support.

Read the full incident report →