Update - Our team continues working to solve the problem, however it was identified that there are new template specifications in the channel that are demanding a greater effort than initially planned. We continue to work to solve the problem as soon as possible.
Jun 11, 22:01 GMT-03:00
Investigating - Below is information about the reported failure, regarding the disapproval of WhatsApp's media message template when submitted by the blip Portal, with the entire context of the scenario.

What generated the scenario?
A change made by Whatsapp regarding the ‘media message template’ made it mandatory a parameter that is currently not available in the Portal blip template submission process, causing the registration of these templates to be disapproved.

What is the impact?
As stated above, the ‘media message template’ entries made by Portal blip are rejected by Whatsapp.

What is the palliative solution?
While we work to make the Portal blip compliant with the change made by Whatsapp, users who need to submit media templates must register a task-type ticket so that we can submit them directly on the Whatsapp Platform.

What about the definitive solution?

We at Take blip are working with priority so that the adjustment in the Portal is carried out as soon as possible and users regain autonomy in the submission of media message templates. A study of the changes needed to adjust is being carried out and we still do not have a forecast of the deadline for finalizing the final solution. As soon as we have any news we will update you on the progress.
May 28, 18:31 GMT-03:00
Desk Operational
90 days ago
99.75 % uptime
Today
Take Blip Platform Operational
90 days ago
99.94 % uptime
Today
CRM ? Operational
90 days ago
100.0 % uptime
Today
Core Operational
90 days ago
99.89 % 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.88 % 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
Jun 18, 2021

No incidents reported today.

Jun 17, 2021
Completed - The scheduled maintenance has been completed.
Jun 17, 06:00 GMT-03:00
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 17, 04:01 GMT-03:00
Scheduled - Please be advised that on June 17th, our team will perform maintenance on some features of the Take Blip platform.

During this period, it is possible that Blip may have some downtime. These moments should be brief and, as soon as maintenance is complete, they will cease completely.

In addition, we are on hand to help with whatever you need! Just open a ticket or make a post on the Forum, where we communicate with the entire user community.

Start: 06/17/2020, Thursday, at 4 am
End: 06/17/2020, Thursday, at 6 am
Jun 15, 20:32 GMT-03:00
Jun 16, 2021
Resolved - Impact: The app was not displaying trafficked messages while interacting with the bot.

Solution: Our team worked to resolve the failure and the platform returned to normal. We are investigating the reason for the failure and will inform you on postmortem.
Jun 16, 14:57 GMT-03:00
Investigating - We identified in our monitoring an issue related to viewing ticket history.
Jun 16, 14:14 GMT-03:00
Jun 15, 2021
Resolved - Fault identified: high memory consumption on some servers.

Analysis Details: A scale-up was performed on all machines that were consuming high volume of memory.

An internal investigation is being carried out to verify the root cause.
Jun 15, 15:55 GMT-03:00
Identified - We identified in our monitoring an issue related to viewing ticket history.
Jun 15, 14:14 GMT-03:00
Jun 14, 2021
Resolved - Solução aplicada: Our team worked to solve the failure and the platform is normalized. We also opened an internal issue to investigate the root cause.
Jun 14, 19:15 GMT-03:00
Update - Impacto: The application was not displaying messages trafficked during interaction with the bot.

Solução aplicada: Our team worked to solve the failure and the platform is normalized. We also opened an internal issue to investigate the root cause.
Jun 14, 19:00 GMT-03:00
Investigating - We identified in our monitoring an issue related to viewing ticket history.
Jun 14, 18:15 GMT-03:00
Jun 13, 2021

No incidents reported.

Jun 12, 2021

No incidents reported.

Jun 11, 2021

Unresolved incident: [Informative] Problem in creating media message template by Portal blip.

Jun 10, 2021
Resolved - This incident has been resolved.
Jun 10, 23:41 GMT-03:00
Update - We registered an instability in our platform affecting the access to the Desk portal.

Impact:

Customers who attempted to access the Portal between 8:20 pm to 8:40 pm and 8:50 pm to 9:10 pm experienced access failures. It is noteworthy that all customers who were already logged in did not notice the impact.

Applied solution:

Our team worked to solve the failure and the platform is normalized and is under monitoring. We also opened an internal issue to investigate the root cause.
Jun 10, 21:59 GMT-03:00
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 10, 20:53 GMT-03:00
Investigating - We identified in Monitoring, a degradation (or instability) of the platform
Jun 10, 20:35 GMT-03:00
Resolved - What generated the failure:

The failure was due to an update performed in the scheduled maintenance window.

Impact to the customer: Issue triggering broadcast by plugin

Solution applied: Our team has already identified the issue in the published version, so a rollback of the current Plugin version was performed and the scenario was normalized.

Start date/time: 08:20 AM

End date/time: 10:45 AM

Actions after bug fix: It will be evaluated internally as the issue was not fully identified in the tests before implementing the version to production.
Based on this analysis, actions will be mapped to improve the testing process.
Jun 10, 10:45 GMT-03:00
Investigating - We are currently unavailable to send a broadcast by the Portal Plugin.

Our team is already working on it and we will give an update soon.
Jun 10, 08:15 GMT-03:00
Jun 9, 2021

No incidents reported.

Jun 8, 2021

No incidents reported.

Jun 7, 2021

No incidents reported.

Jun 6, 2021

No incidents reported.

Jun 5, 2021

No incidents reported.

Jun 4, 2021

No incidents reported.