All Systems Operational
Desk ? Operational
90 days ago
99.72 % uptime
Today
Take Blip Platform Operational
90 days ago
99.93 % uptime
Today
CRM ? Operational
90 days ago
99.89 % uptime
Today
Core Operational
90 days ago
99.97 % uptime
Today
Analytics Operational
90 days ago
99.92 % uptime
Today
Artificial Intelligence Operational
90 days ago
100.0 % uptime
Today
Portal Operational
90 days ago
99.93 % uptime
Today
Cloud Infrastructure ? Operational
90 days ago
99.91 % uptime
Today
Channels Operational
90 days ago
99.99 % uptime
Today
WhatsApp ? Operational
90 days ago
99.91 % uptime
Today
Telegram Operational
90 days ago
100.0 % uptime
Today
Messenger Operational
90 days ago
100.0 % uptime
Today
BlipChat Operational
90 days ago
100.0 % uptime
Today
Workplace Chat Operational
90 days ago
100.0 % uptime
Today
BusinessChat Operational
90 days ago
100.0 % uptime
Today
Skype Operational
90 days ago
100.0 % uptime
Today
E-mail Operational
90 days ago
100.0 % uptime
Today
Instagram Operational
90 days ago
100.0 % uptime
Today
Hosting Enterprise Operational
90 days ago
99.99 % uptime
Today
Bot Builder Operational
90 days ago
99.99 % uptime
Today
Bot Router Operational
90 days ago
100.0 % uptime
Today
Hosting Business Operational
90 days ago
99.99 % uptime
Today
Bot Builder Operational
90 days ago
99.99 % uptime
Today
Bot Router Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Past Incidents
Feb 1, 2023
Resolved - This incident has been resolved.
Feb 1, 17:10 GMT-03:00
Monitoring - Status: The environment is back to normal and the team continues to monitor.

Impact: High CPU usage on the database responsible for all user management.

Reflection for the customer: All components of the smart contact and usability have degraded or are currently unavailable.

What generated the failure: Identified that the consumers of the application responsible for updating the Data that are on the monitoring page of the Blip portal.

Mitigation action:

Three actions were carried out:

-Switched off the consumers of the application that was causing the high consumption in the database responsible for all user management;

- Scale Up of the Database in order to support the load until the Rollback action is completed;

- Return of the change executed yesterday (01/31/2023 at 10:00 pm) was carried out in the application that presented the failure.

NOTE: For customers who consume data from Analytics applications, they may still experience a delay, since we had a queue during the period in which we needed to stop consumers.

Start time: 11:10 AM
End time: 12:45 PM

Feb 1, 15:21 GMT-03:00
Update - - Scale has been finished
- Rollback has been completed now we are returning consumers to what it was before the crisis

Next update: in 30 min or when a relevant new fact is presented;

Feb 1, 14:34 GMT-03:00
Identified - - We continue to monitor the finalization of the scale of resources;
- Preparation for the rollback done, let's start in a moment.
Regarding the impact on analytics pages, the impact should last until 8 pm today, as consumers have been stopped and requests are queued.

Next update: in 30 min or when a relevant new fact is presented;

Feb 1, 14:06 GMT-03:00
Update - - We continue to monitor the finalization of the scale of resources
- Let's start the rollback of a change made the day before, then we'll go up the services

Next update: in 15 minutes or when a relevant new fact is presented;

Feb 1, 13:50 GMT-03:00
Update - - We are still waiting for the finalization of the scale of the resources
- Services are still stopped so that the impact does not occur again, we are checking what actions are necessary to return services
Some customers have already signaled normalization after the actions, but we are still investigating.

Next update: in 15 minutes or when a relevant new fact is presented;

Feb 1, 13:28 GMT-03:00
Update - - We are in the process of scaling some features to temporarily mitigate the issue while we continue to analyze the issue.
- In addition, some services are being stopped momentarily to reduce the impact. With the actions reported above, the impact is already being mitigated and an improvement in the platform scenario was observed. The only point to note is that, at the moment, the platform's analytics pages will not show updated data.

Next update: in 15 min or when a relevant new fact is presented;

Feb 1, 13:12 GMT-03:00
Investigating - We are experiencing a partial degradation in our CRM application.

Impact:

CRM is responsible for all user management, so all smart contact components and usability that are tied to it will be degraded or unavailable at the moment.

Update:

Our technical team is already working on the case.

Feb 1, 11:23 GMT-03:00
Resolved - This incident has been resolved.
Feb 1, 09:20 GMT-03:00
Investigating - Our partner Meta is experiencing a degradation that is affecting the visualization of managed WABAs in Meta Bussines Manager.

We are aware of an issue that may be impacting managing message templates.

The responsible teams are already looking for a way to solve the problem as soon as possible.


Official Source:
https://metastatus.com/whatsapp-business-api

Jan 19, 14:17 GMT-03:00
Jan 31, 2023

No incidents reported.

Jan 30, 2023

No incidents reported.

Jan 29, 2023

No incidents reported.

Jan 28, 2023

No incidents reported.

Jan 27, 2023

No incidents reported.

Jan 26, 2023
Resolved - We made a change to the infrastructure. After the change, we monitored the environment and did not identify new slowdown scenarios.
Jan 26, 17:52 GMT-03:00
Update - Since the last update, we have not identified slowdowns on the platform, we will keep the monitoring status.
Jan 25, 16:43 GMT-03:00
Monitoring - We identified some moments of slowness on the platform that were normalized and we continue to monitor the environment.
Jan 25, 12:22 GMT-03:00
Resolved - Updating status:
What happened? I had an outage with a general impact on our platform.
What reflection for the customer? Failed to exchange messages with bots on all channels. Platform unavailable for attendants.
What was the performance?
The environment was automatically restored. The technical team is investigating what caused the momentary interruption.

Jan 26, 17:08 GMT-03:00
Update - We are continuing to investigate this issue.
Jan 26, 16:35 GMT-03:00
Update - We are continuing to investigate this issue.
Jan 26, 16:26 GMT-03:00
Investigating - At 15:55 we identified an outage on the Blip platform

Impact:

Fail on exchanging messages with bots on all channels. Platform unavailable to attendants

Update:

Our technical team is already working to resolve the issue.

Jan 26, 16:23 GMT-03:00
Jan 25, 2023
Resolved - After acting on the initially identified scenario, we monitored the platform, as informed, and didn't identify new slowdown scenarios.
Jan 25, 00:14 GMT-03:00
Update - Since the last update, we have not identified slowdowns on the platform, we will keep the monitoring status until 12:00AM tomorrow.
Jan 24, 17:33 GMT-03:00
Update - The actions we executed they brought the platform to a state of stability; the affected customers are not reporting issues. We closed the incident, but continue monitoring the environment closely.
Jan 24, 12:47 GMT-03:00
Monitoring - We identified some offender what is possible that are affecting the availability of the platform, we cutoff the process and we are evaluate the impact, but our monitoring tools are indicating a normalization.
Jan 24, 12:17 GMT-03:00
Update - After investigating some possibilities, we continuing analysing the cause of the slowness on platform.
Jan 24, 11:35 GMT-03:00
Investigating - We are experiencing a partial degradation on BLiP Desk application and Portal.

Impact:

Slowness when using the Desk application

Update:

Our technical team is already working on the case.

Jan 24, 10:24 GMT-03:00
Jan 24, 2023
Jan 23, 2023
Resolved - This incident has been resolved
Jan 23, 16:57 GMT-03:00
Monitoring - We found the part that was overloading the system and restrict to avoid new problems
Jan 23, 16:41 GMT-03:00
Update - We found some commands to our platform that are causing this error and we are investigating.
Jan 23, 16:17 GMT-03:00
Investigating - We are experiencing a partial degradation on BLiP Desk application and Portal.

Impact:

Slowness when using the Desk

Update:

Our technical team is already working on the case.

Jan 23, 15:10 GMT-03:00
Resolved - The incident has been resolved. We observed that the environment remained stable and we did not find any other errors
Jan 23, 12:58 GMT-03:00
Monitoring - A fix has been implemented and we are monitoring the results.
Jan 23, 12:26 GMT-03:00
Update - We are continuing to investigate this issue.
Jan 23, 12:10 GMT-03:00
Update - We are continuing to investigate this issue.
Jan 23, 10:36 GMT-03:00
Investigating - We are experiencing a partial degradation on BLiP Desk application.

Impact: Slowness when using the Desk

Jan 23, 10:31 GMT-03:00
Jan 22, 2023

No incidents reported.

Jan 21, 2023

No incidents reported.

Jan 20, 2023

No incidents reported.

Jan 19, 2023
Resolved - We identified an unexpected behavior in the database, caused by a query.

We perform the correction.

Jan 19, 12:31 GMT-03:00
Update - We are continuing to investigate this issue.
Jan 19, 11:49 GMT-03:00
Investigating - We are experiencing a partial degradation on BLiP Portal

Impact:

Slowness when using BLiP Portal.

Update:

Our technical team is already working on the case.

Jan 19, 11:23 GMT-03:00
Jan 18, 2023

No incidents reported.