Identified - We are continuing to work on a fix for this issue.
Apr 30, 01:06 GMT-03:00
Monitoring - We are continuing to work on a fix for this issue.
Apr 30, 01:05 GMT-03:00
Update - We are continuing to work on a fix for this issue.
Apr 11, 12:08 GMT-03:00
Update - We are continuing to work on a fix for this issue.
Apr 11, 12:02 GMT-03:00
Identified - We have identified instability in the Direct Ticket Transfer Desk and Ticket Prioritization features and they have been disabled. For those of you who use one of these features and are impacted, our commercial area is available to answer any questions you may have.
Our team keeps checking to come back with these features as soon as possible.

Feb 22, 20:34 GMT-03:00
Identified - We Identified that the SalesForce endpoint (ChatApiEndpoint), used in the Salesforce integration with Blip, in some cases is not responding, since there is no response from the SalesForce endpoint, tickets are not assigned to any attendant and the user is left without overflow , going back to the bot flow.

In analysis, we saw that the endpoint was changed by SalesForce itself, so, to solve the problem, you must access the SalesForce admin page, get the new URL available and manually change it in the Blip settings.

Step by step :

To access the Salesforce Portal and get the new URL for the SalesForce endpoint, as per the Salesforce documentation:

In Basic Settings click on the option:

The Chat endpoint hostname

1. To get this parameter from Salesforce, click on the gear and then on Setup.
2. In the quick search type "Chat settings"
3. Copy the Endpoint URL.

• Access the bot where the channel is used (Service / Service Channels / Salesforce / Basic Settings) and update the endpoint information (chat endpoint hostname).

Complete documentation: https://help.blip.ai/hc/pt-br/articles/4474398500503-Configurando-o-atendimento-via-chat-no-Salesforce.

May 9, 17:53 GMT-03:00
Desk ? Operational
90 days ago
99.97 % uptime
Today
Take Blip Platform Operational
90 days ago
99.93 % uptime
Today
CRM ? Operational
90 days ago
100.0 % uptime
Today
Core Operational
90 days ago
99.84 % 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.99 % uptime
Today
Cloud Infrastructure Operational
90 days ago
99.79 % uptime
Today
Channels Operational
90 days ago
99.99 % 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
99.99 % uptime
Today
Workplace Chat Operational
BusinessChat Operational
Skype Operational
E-mail Operational
Instagram Operational
90 days ago
100.0 % uptime
Today
Hosting Enterprise Operational
90 days ago
99.81 % uptime
Today
Bot Builder Operational
90 days ago
99.62 % uptime
Today
Bot Router Operational
90 days ago
100.0 % uptime
Today
Hosting Business Operational
90 days ago
99.81 % uptime
Today
Bot Builder Operational
90 days ago
99.62 % 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 18, 2022
Resolved - Some customers reported occasional problems, which were fixed in the morning. During the rest of the day the environment was monitored and no new problems were found or reported, we are considering the problem solved.
May 18, 19:54 GMT-03:00
Monitoring - We mitigated the issues found by restarting the Whatsapp service on the numbers with errors. The monitoring team will be observing the environment for the next few hours.
May 17, 23:19 GMT-03:00
Update - We have errors in specific numbers of clients, on which we are executing restarts of the service, because even after the problem with the Meta Whatsapp API was fixed, the connection did not return automatically.
May 17, 21:59 GMT-03:00
Update - Meta's return declared the services as healthy, but we have customers reporting errors in the channel and that's why we consider that this evaluation is still under way.
May 17, 17:26 GMT-03:00
Update - With the declaration of problems in the Whatsapp API, we are waiting for Meta's return on the correction of the problem in the service, the team is ready to test and validate the total reestablishment of the channel.
May 17, 13:46 GMT-03:00
Identified - Meta declared a Major level issue that is impacting the sending of messages, we have an open ticket and are following the correction for channel health assessment on the blip platform.
May 17, 11:16 GMT-03:00
Update - We are continuing to investigate the issue and location to find the source, as it is currently reaching customers randomly. We didn't find any problem in the channel infrastructure, in the take.
May 17, 11:08 GMT-03:00
Investigating - Identified failure to send messages on our platform, our technical team is already working on the case.
May 17, 10:14 GMT-03:00
Resolved - After mitigating the crisis, a slowdown was noticed by occasional customers, we continued monitoring and no new unavailability was found, so we are considering the problem solved.
May 18, 19:46 GMT-03:00
Monitoring - The issue has been mitigated, the affected services are responsive again.
May 18, 15:36 GMT-03:00
Identified - The service returned to respond partially and is being stabilized, some customers already report that it is ok.
May 18, 15:32 GMT-03:00
Update - We're investigating a bug that's causing issues with logging in to the Platform's Portal and Desk.
May 18, 15:10 GMT-03:00
Investigating - we have identified failure to access the portal and desk
May 18, 14:48 GMT-03:00
May 17, 2022
May 16, 2022

No incidents reported.

May 15, 2022
Completed - We have successfully completed our maintenance. We carry out all the validations, the production environment and the smart contact interaction are operational.
May 15, 04:32 GMT-03:00
Verifying - we finished the database service migration process ahead of schedule. We are currently validating the production environment.
May 15, 03:51 GMT-03:00
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 14, 22:00 GMT-03:00
Update - We will be undergoing scheduled maintenance during this time.
May 11, 11:53 GMT-03:00
Update - We will be undergoing scheduled maintenance during this time.
May 11, 11:47 GMT-03:00
Scheduled - One of our pillars is the continuous improvement of our services, aiming to improve your experience with Take Blip.

As part of this evolution process, we inform you that we have programmed a migration of our database service, so that there will no longer be a physical limitation of storing this data, generating greater resilience and in line with the growth of the Blip platform.

Attention: maintenance will result in unavailability of the platform from 22:00 on 05/14 to 06:00 on 05/15.

The service is expected to be back to normal after this period.

What do you need to do

If you have a transfer for human service, it is essential that you finish all calls in service at least 20 minutes before the stoppage, that is, until 21:40.

We reiterate that it is our purpose to work to ensure that you, our customer, can enjoy the integrality of our solution with increasingly secure, faster and more efficient systems.

We count on your understanding and make ourselves available in our service channels in case of questions.

Take Blip Team

May 10, 15:35 GMT-03:00
May 14, 2022
May 13, 2022

No incidents reported.

May 12, 2022

No incidents reported.

May 11, 2022

No incidents reported.

May 10, 2022

No incidents reported.

May 9, 2022

Unresolved incident: Failed to handle tickets for the SalesForce integration.

May 8, 2022

No incidents reported.

May 7, 2022

No incidents reported.

May 6, 2022
Resolved - This incident has been resolved.
May 6, 18:35 GMT-03:00
Monitoring - A fix has been implemented and we are monitoring the results.
May 6, 18:29 GMT-03:00
Update - It was identified that a problem in a backup routine was causing overcrowding on disk, which caused the database service to be unavailable. The process causing the error was stopped and the disk space freed up, the database services started working again.
May 6, 18:18 GMT-03:00
Update - An issue has been identified with the database infrastructure resource managed by our cloud provider. We are continuing to work on a fix for this issue.
May 6, 17:54 GMT-03:00
Identified - It was identified through tests that several bots were unresponsive. We are with the responsible team to identify what happened.
May 6, 17:27 GMT-03:00
May 5, 2022

No incidents reported.

May 4, 2022

No incidents reported.