All Systems Operational
Desk Operational
90 days ago
99.58 % uptime
Today
Take Blip Platform Operational
90 days ago
99.87 % uptime
Today
CRM ? Operational
90 days ago
100.0 % uptime
Today
Core Operational
90 days ago
99.69 % uptime
Today
Analytics Operational
90 days ago
100.0 % uptime
Today
Artificial Intelligence Operational
90 days ago
99.93 % uptime
Today
Portal Operational
90 days ago
99.75 % uptime
Today
Cloud Infrastructure Operational
90 days ago
99.88 % uptime
Today
Channels Operational
90 days ago
100.0 % uptime
Today
WhatsApp ? Operational
90 days ago
100.0 % 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
BusinessChat Operational
Skype Operational
E-mail Operational
Hosting Enterprise Operational
90 days ago
100.0 % uptime
Today
Bot Builder Operational
90 days ago
100.0 % uptime
Today
Bot Router Operational
90 days ago
100.0 % uptime
Today
Hosting Business Operational
90 days ago
100.0 % uptime
Today
Bot Builder Operational
90 days ago
100.0 % 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
Apr 11, 2021

No incidents reported today.

Apr 10, 2021

No incidents reported.

Apr 9, 2021

No incidents reported.

Apr 8, 2021

No incidents reported.

Apr 7, 2021
Resolved - In our monitoring, we identified a failure to access the Blip Desk service tool. Failed to return "Service is not available".

Details of the analysis: We identified a large volume of requests to the Desk application, which were normalized shortly thereafter.

We have not identified the root cause of the requests.
Our team continues to investigate the root cause and we will post it in the postmortem.

Start date / time: 07/04 18:55 hours
End date / time: 07/04 19:51 hours
Apr 7, 21:07 GMT-03:00
Investigating - Through our monitoring we have identified a degradation in our platform causing failure to access the Desk portal.

Our technical team is already analyzing what is causing the failure

impact for the customer: Failure to access the Desk portal. The fault is intermittent.
Apr 7, 19:07 GMT-03:00
Resolved - Failure identified: We identified a failure in the commands related to the transfer and distribution of tickets, changing the status of the ticket and defining the closing tag.

Impact for the client: Slowness in the display of messages inside the Branch and distribution of tickets.

Applied solution: Scaleup of the database was carried out, this action was carried out at 12: 58h. Soon after the failures were healed and we no longer identified any failures in our monitoring.

Root cause: We continue to investigate the root cause and we will inform you in the postmortem.

Start date: April 7, 10:30 am
End date: April 7, 12:58 pm
Apr 7, 15:26 GMT-03:00
Monitoring - After scale up action in the Desk database, completed at 12: 58h, the consumption of resources that was causing the reported scenario is stable.

We are monitoring the environment.
Apr 7, 13:30 GMT-03:00
Update - We are working with some changes and monitoring the behavior of the Desk and distribution of tickets.
Apr 7, 12:55 GMT-03:00
Identified - We identified a failure in the commands related to the transfer and distribution of tickets, changing the status of the ticket and defining the closing tag.

Impact for the client: Slowness in the display of messages inside the Desk and distribution of tickets.
Apr 7, 10:30 GMT-03:00
Apr 6, 2021
Resolved - This incident has been resolved.
Apr 6, 22:40 GMT-03:00
Investigating - Through our monitoring we have identified a degradation in our platform causing failure to access the Desk portal.

Our technical team is already analyzing what is causing the failure

impact for the customer: Failure to access the Desk portal. The fault is intermittent.
Apr 6, 21:53 GMT-03:00
Resolved - This incident has been resolved.
Apr 6, 21:00 GMT-03:00
Monitoring - Slow message exchange
Lentidão e timeout em comandos (blip e desk)
Problemas de publicação de fluxo

Fault identified:

An increase in the time of requests was identified within responsible for the traffic of messages in the intelligent contact (Bot).

Reflection for the client:

Customers will observe slowness in the exchange of messages, with registration in some periods of response by the Bot.

Correction applied:

We carried out some actions related to the database improvements.
At 3:19 pm we found that the database performance normalized.

Root Cause:

We continue to analyze together several times to identify a root cause.

Start date 05/04/2021 time: 10:39
Apr 6, 16:01 GMT-03:00
Update - Update:

We have performed some actions, with no improvement in the database overload scenario.

We are currently working on a hotfix and will update it when it is finished.

Actions: The technical team is already working and we will update in 30 minutes
Apr 6, 14:38 GMT-03:00
Identified - Slow message exchange
Slowness and timeout in commands (blip and desk)
Stream publishing issues

Fault identified:

An increase in the time of requests was identified within responsible for the traffic of messages in the intelligent contact (Bot).

Reflection for the client:

Customers will observe slowness in the exchange of messages, with registration in some periods of response by the Bot.

Actions: The technical team is already working and we will update in 30 minutes

Start date 05/04/2021 / time: 10:39
Apr 6, 10:39 GMT-03:00
Resolved - After the actions taken, the scenario was normalized.
Apr 6, 13:29 GMT-03:00
Update - We have identified the fault and have resolved it so that it no longer occurs. We noticed that the failures have decreased, after the necessary actions.
Apr 6, 12:12 GMT-03:00
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 6, 12:01 GMT-03:00
Update - We continue investigating this problem with full priority
Apr 6, 11:27 GMT-03:00
Identified - We identified a failure in the commands related to the transfer and distribution of tickets, changing the status of the ticket and defining the closing tag.

Impact for the client: Slowness in the display of messages inside the Desk and error distribution of tickets.
Apr 6, 10:39 GMT-03:00
Apr 5, 2021

No incidents reported.

Apr 4, 2021

No incidents reported.

Apr 3, 2021

No incidents reported.

Apr 2, 2021

No incidents reported.

Apr 1, 2021
Resolved - Incident location: Cloud vendor;
Affected services: Access to the portal and Desk, cloud infrastructure;
Preliminary root cause: We continue to investigate the underlying cause of the DNS outage, but note that the cloud provider's DNS servers have seen an increase in DNS traffic.

We will inform in the postmortem
Apr 1, 22:02 GMT-03:00
Monitoring - We had normalization of the environment, however the cloud provider continues with its infrastructure flagged with DNS failure.
Apr 1, 19:50 GMT-03:00
Investigating - We identified a failure in the cloud provider, our team is mobilized on the case.

At the moment there will be a failure to access the portal and failures to send messages.
Apr 1, 19:05 GMT-03:00
Mar 31, 2021

No incidents reported.

Mar 30, 2021

No incidents reported.

Mar 29, 2021
Resolved - Context:
We identified a failure in the commands related to the transfer of tickets, changing the status of the ticket and defining the closing tag.

Solution:
The development team uploaded a hotfix to resolve this failure.
The scenario has been normalized and the postmortem will be filled with more information about the root cause.

Start date / time: 3/29/2021 2:00 PM
End date / time: 3/29/2021 10:10 PM
Mar 29, 22:58 GMT-03:00
Identified - Our team generated a hotfix to adjust the commands and ensure correct processing.

However we saw that we have an average rate of 5% failure in the commands and possible unavailability during the update, we chose to deploy the hotfix in the maintenance window today (03/29/2021) at 10 pm.
Mar 29, 19:44 GMT-03:00
Update - We continue investigating this problem with full priority
Mar 29, 17:13 GMT-03:00
Update - We continue investigating this problem with full priority
Mar 29, 16:03 GMT-03:00
Investigating - We have identified a degradation in the application of the desk and so far we have noticed the following impacts:
Failed to transfer ticket, failed to change status, failed to set tag
Mar 29, 15:36 GMT-03:00
Mar 28, 2021

No incidents reported.