All Systems Operational
Desk Operational
90 days ago
99.68 % uptime
Today
Take Blip Platform Operational
90 days ago
99.89 % 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.83 % uptime
Today
Cloud Infrastructure Operational
90 days ago
99.88 % uptime
Today
Channels Operational
90 days ago
99.88 % 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
99.72 % uptime
Today
BlipChat Operational
90 days ago
99.91 % 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
May 13, 2021
Resolved - Updating status - 00:19:

The corrections were applied by our technical team responsible for maintenance, and our production environment is now normalized. We conducted tests and all channels are already responding in the exchange of messages within the smart contact.

Start date / time: 12/05/2021 10:00 PM
End Date / Time: 12/05/2021 11:50 PM
May 13, 00:20 GMT-03:00
Identified - The identified failure was due to an update that occurred within the scheduled maintenance window in our production environment.

Impact: Failed messages on all channels to Smart Contacts (Bots).

Action in progress: Our technical team is applying the necessary corrections to restore the failure caused by maintenance.
May 12, 23:26 GMT-03:00
Investigating - We are experiencing an unavailability on our platform.

Impact: The smart contacts are unavailable and are not responding in all channels.

Our team is already working and we will soon update.
May 12, 22:31 GMT-03:00
May 12, 2021
Resolved - Updating status: Correction applied by the Facebook engineering team.

After the solution was applied, the technical team at Take Blip carried out tests for creating and viewing templates on the Blip Portal, sending active messages and validating access to Facebook Messenger.

All validations were successful.

We still don't have information from the partner Facebook which action was taken to solve the problem.

It will be updated directly on the Facebook status: page:https://developers.facebook.com/status/issues/194089685886014/
May 12, 14:52 GMT-03:00
Update - Facebook's engineering team is working with the highest priority to resolve the failure.

We are sharing here the status link provided by the partner Facebook: https://developers.facebook.com/status/issues/194089685886014/

Impact: Failure to create and view the firing template within the Blip portal, failure trigger active messages, logging into Facebook Messenger accounts.
May 12, 14:24 GMT-03:00
Update - We are continuing to work on a fix for this issue.
May 12, 10:20 GMT-03:00
Update - Updating status: It was identified by the technical team that the failure is due to a permission and login limitation by our partner Facebook.

Impact: Failure in the creation and visualization of the firing template within the Blip portal and login to Facebook Messenger accounts.

Action taken: Registered ticket along with Facebook and staggered with top priority given the impact on the client's business.
May 12, 10:18 GMT-03:00
Identified - We have identified a failure in the active message triggering model on the Blip Portal.

Impact: Failure in the creation and visualization of the firing template within the Blip portal.

Action: Our technical team has already identified the fault and are working to correct the failure.
May 12, 09:23 GMT-03:00
May 11, 2021

No incidents reported.

May 10, 2021

No incidents reported.

May 9, 2021

No incidents reported.

May 8, 2021

No incidents reported.

May 7, 2021

No incidents reported.

May 6, 2021

No incidents reported.

May 5, 2021

No incidents reported.

May 4, 2021
Resolved - This incident has been resolved.
May 4, 14:37 GMT-03:00
Monitoring - Fault identified:

We had a high CPU consumption on three of our servers with one of our clusters of six servers. We have not yet been able to identify which offender caused the high requisition volume in a short period of time. The environment is already restored.

Reflection for the client:

Slowness in accessing the portal and desk, failure to load conversations on the desk, disconnection on the desk, problems with forwarding messages between the attendant and the customer.

Action in progress: The technical team is evaluating what caused the high volume of requests culminating in the high consumption of CPU and memory resources. The Post Mortem for customers will be updated on this Here on the status page as soon as we have an update on the root cause.

Start date 04/05/2021 time: 10:07
End date 04/05/2021 time: 10:30
May 4, 10:30 GMT-03:00
Update - We are continuing to work on a fix for this issue.
May 4, 10:20 GMT-03:00
Identified - In our monitoring, we identified a degradation in the Desk.

The team is already verifying this degradation.
May 4, 10:07 GMT-03:00
May 3, 2021

No incidents reported.

May 2, 2021

No incidents reported.

May 1, 2021

No incidents reported.

Apr 30, 2021

No incidents reported.

Apr 29, 2021
Resolved - This incident has been resolved.
Apr 29, 22:59 GMT-03:00
Identified - Status Update: Due to an update carried out in the scheduled maintenance window (carried out on April 28, 2020 at around 11: 30 pm) in the Desk application, we had problems when returning the value contained in the variables used in the “Custom reply” ​​within the screen service desk.

Impact: In the Desk attendant screen, when using the “custom reply” feature that uses a variable in the text, only the name of the field is returned and not the value of the variable. It is worth mentioning that the impact is low since only one resource is not being filled in automatically, and can be filled in manually.

Correction action: Given that the identified failure is due to an update in production Rollback mapping as a solution action.

For this specific scenario, the maneuver involves a restart in the Desk Application service. This action may cause an even greater impact if performed during business hours, since disconnection and subsequent connection of all the attendants who are logged in occurs, so it was defined that the rollback will be performed within the maintenance window on today's date (29/04/2021) at 10 pm.
Apr 28, 23:30 GMT-03:00
Postmortem - Read details
May 4, 21:54 GMT-03:00
Resolved - This incident has been resolved

Start date: 28/04 22:00
End date: 29/04 09:51
Apr 29, 10:38 GMT-03:00
Monitoring - We identified that an update carried out on the WhatsApp gateway impacted the sending of media on the channel. The update has already been rolled back.

Our technical team is already investigating what happened.
Apr 29, 10:00 GMT-03:00
Update - We are continuing to work on a fix for this issue.
Apr 29, 09:31 GMT-03:00
Identified - We have identified degradation in the sending of media by WhatsApp and our technical team is already analyzing what is causing the failure
Apr 29, 09:31 GMT-03:00