All Systems Operational
Desk Operational
90 days ago
99.7 % uptime
Today
BLiP Platform Operational
90 days ago
99.94 % uptime
Today
CRM ? Operational
90 days ago
99.94 % uptime
Today
Core Operational
90 days ago
99.91 % uptime
Today
Analytics Operational
90 days ago
100.0 % uptime
Today
Artificial Intelligence Operational
90 days ago
100.0 % uptime
Today
Portal Operational
90 days ago
99.82 % uptime
Today
Cloud Infrastructure Operational
90 days ago
100.0 % uptime
Today
Channels Operational
90 days ago
99.92 % uptime
Today
WhatsApp ? Operational
90 days ago
99.88 % uptime
Today
Telegram Operational
90 days ago
100.0 % uptime
Today
Messenger Operational
90 days ago
99.85 % uptime
Today
BlipChat Operational
90 days ago
99.96 % uptime
Today
Workplace Chat Operational
BusinessChat Operational
Skype Operational
E-mail Operational
Hosting Enterprise Operational
90 days ago
99.98 % uptime
Today
Bot Builder Operational
90 days ago
99.97 % uptime
Today
Bot Router Operational
90 days ago
99.99 % 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
99.99 % uptime
Today
Hosting MAX 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 Standard Operational
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
Sep 29, 2020
Completed - The scheduled maintenance has been completed.
Sep 29, 06:00 GMT-03:00
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 28, 23:00 GMT-03:00
Scheduled - On this date we will have a maintenance on the WhatsApp channel.
During maintenance there will be degradation in the use of the channel, with periods of unavailability.
Sep 25, 12:29 GMT-03:00
Sep 28, 2020
Sep 27, 2020

No incidents reported.

Sep 26, 2020

No incidents reported.

Sep 25, 2020

No incidents reported.

Sep 24, 2020

No incidents reported.

Sep 23, 2020
Resolved - This incident has been resolved.
Sep 23, 21:26 GMT-03:00
Investigating - We are suffering a degradation in the performance of the BLiP platform, our technical team is already working on the case.

Impact: Access to the BLiP Desk and Portal tool
Sep 23, 20:16 GMT-03:00
Sep 22, 2020
Resolved - We found that some search commands for threads were failing, causing messages from some tickets not to be displayed on the attendants' screen. After the team's action, the environment is normalized. We are still investigating the root cause.
Sep 22, 17:27 GMT-03:00
Monitoring - We made an intervention in one of our applications and at the moment the scenario is normalized, we continue to monitor the environment.
Sep 22, 13:22 GMT-03:00
Update - Dear, we are still investigating the scenario. It is worth mentioning that the problem affects only the message history on the desk in just a few conversations.
Sep 22, 11:10 GMT-03:00
Investigating - Good morning dear, we identified that some conversations at the desk are coming in blank and our responsible team is already investigating the scenario.
Sep 22, 09:38 GMT-03:00
Sep 21, 2020
Resolved - This incident has been resolved.
Sep 21, 18:33 GMT-03:00
Update - After failover, the database is operational.

We continue to monitor the environment.

The root cause has not yet been identified and will be reported in Postmortem.
Sep 21, 16:34 GMT-03:00
Monitoring - The environment is normalized, we are monitoring.
Sep 21, 15:55 GMT-03:00
Update - Problem: Initially we noticed a slow search for contacts, but after investigating together with our infrastructure provider, we noticed an increase in requests in the database causing delay in the processing of messages, commands, notifications, etc.

Action plan: We registered a top priority ticket with our infrastructure supplier and we are working directly with the technical team, analyzing actions to mitigate the failure and identify the root cause.

Actions in progress:

1) The ScaleUp of the database was started around 10:45, but according to our infrastructure provider, due to the volume of data that database and also the impact during this process, the forecast for completion is many hours. Because of this, the action will be aborted.

2) The technical team is working together with our infrastructure provider to failover the database, in order to mitigate instabilities. The production bank, which is compromised, will no longer be used pointing to a copy of it.

Forecast: Unfortunately we still don't have a return from microsoft with an estimated deadline.

Date / time the problem started: 2020-09-21 at 09h20m
End date / time: No forecast
Sep 21, 13:40 GMT-03:00
Update - We are continuing to work on a fix for this issue.
Sep 21, 12:40 GMT-03:00
Update - We are in contact with an engineer from our infrastructure provider to verify the incident.

Impact verified due to slow message processing.
Sep 21, 11:53 GMT-03:00
Update - We identified that the failure appears to be related to the database infrastructure.

A ticket has been registered with our cloud provider for verification.
Sep 21, 11:21 GMT-03:00
Update - We are carrying out the Scale Up of the database in order to mitigate the degradation. The forecast for completion is a few hours.

The root cause of the degradation remains under analysis by the Take team.
Sep 21, 11:12 GMT-03:00
Identified - We are experiencing a degradation in the CRM application, 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.

Reflection for the client: The messages are not being delivered.
Sep 21, 09:20 GMT-03:00
Completed - The technical team organized together with our infrastructure provider to fail over the database, in order to mitigate instabilities. The current database, which is compromised, will no longer be used and how it was changed to copy this database.
Sep 21, 16:37 GMT-03:00
Update - Scheduled maintenance is still in progress. We will provide updates as necessary.
Sep 21, 11:48 GMT-03:00
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 21, 11:10 GMT-03:00
Scheduled - We will perform the Database Scale Up, as it was identified that the limit of established requests is being reached generating an impact.

During the process, there may be times when the Database is not available.

Scale Up start: 10:45h (GMT-3)
Sep 21, 11:08 GMT-03:00
Completed - The scheduled maintenance has been completed.
Sep 21, 11:00 GMT-03:00
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 21, 10:45 GMT-03:00
Scheduled - We will perform the Database Scale Up, as it was identified that the limit of established requests is being reached generating an impact.

During the process, there may be times when the Database is not available.

Scale Up start: 10:45h (GMT-3)
Estimated duration: 10 to 15 minutes
Sep 21, 10:44 GMT-03:00
Sep 20, 2020

No incidents reported.

Sep 19, 2020

No incidents reported.

Sep 18, 2020
Resolved - This incident has been resolved.
Sep 18, 20:08 GMT-03:00
Update - We inform you that our cloud provider is already applying a mitigation to the problem and our customers can see improvement. Soon we will have a new update on the definitive solution
Sep 18, 16:14 GMT-03:00
Update - We are continuing to work on a fix for this issue.
Sep 18, 13:57 GMT-03:00
Update - We are continuing to work on a fix for this issue.
Sep 18, 13:56 GMT-03:00
Identified - Identified - The problem is due to a cloud provider outage. The situation is being discussed with the provider.
Sep 18, 12:30 GMT-03:00
Investigating - Investigation - We identified a failure to receive media on the Whatsapp channel
Sep 18, 11:45 GMT-03:00
Sep 17, 2020
Resolved - Failure identified: We identified constant falls in the database responsible for the Blip Chat channel, causing unavailability / instability in the period.

Impact to the customer: Due to the failure mentioned above, the Blip chat channel was not loading.
Applied solution: The failure was due to an unavailability in the Database by our cloud supplier, it was restored without any action on the part of Take.

A ticket has been registered so that they can report the root cause to us.
Sep 17, 11:19 GMT-03:00
Update - We are continuing to investigate this issue.
Sep 17, 11:09 GMT-03:00
Investigating - We identified an outage on our BlipChat channel

Impact: Customers using the Blip Chat channel will be impacted.
Sep 17, 11:07 GMT-03:00
Sep 16, 2020
Resolved - After analysis, we identified that a specific query generated an overload.

This query has already been canceled and the problem no longer occurs.
Sep 16, 15:16 GMT-03:00
Update - The environment is normalized and we continue to monitor.
Sep 16, 14:46 GMT-03:00
Monitoring - The error no longer occurs we are monitoring
Sep 16, 14:44 GMT-03:00
Investigating - Slowness has been identified in the Builder platform.
Sep 16, 14:10 GMT-03:00
Resolved - We identified a partial absence in the message history within the Desk service channel.

Impact:
1) The history is not being viewed by the attendant.
2) When using the Scroll functionality within the tool, it does not bring messages.

Cause: The failure was due to an update in production.

Correction: The update was rollback.
Sep 16, 11:53 GMT-03:00
Identified - We identified a partial absence in the message history within the Desk service channel.

Impact:
1) The history is not being viewed by the attendant.
2) When using the Scroll functionality within the tool, it does not bring messages.
Sep 16, 11:18 GMT-03:00
Completed - The scheduled maintenance has been completed.
Sep 16, 11:48 GMT-03:00
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 16, 11:30 GMT-03:00
Scheduled - To correct the absence in the partial flow of message history in the Desk reported on the status page, there was a need for emergency maintenance.
Emergency maintenance in the Desk application due to the possibility of instability in the Desk Web.

Any questions, we are available.
Sep 16, 11:24 GMT-03:00
Sep 15, 2020

No incidents reported.