Take Blip Status

Take Blip

Take Blip Status

Track Take Blip platform status

All Systems Operational

Uptime over the past 90 days. View historical uptime.

Desk Operational

90 days ago

99.86 % uptime

Today

Take Blip Platform Operational

90 days ago

99.97 % uptime

Today

CRM Operational

90 days ago

100.0 % uptime

Today

Core Operational

90 days ago

100.0 % 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.87 % uptime

Today

Cloud Infrastructure Operational

90 days ago

100.0 % uptime

Today

Channels Operational

90 days ago

99.85 % uptime

Today

WhatsApp Operational

90 days ago

99.44 % 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.97 % 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

Past Incidents

Jan 23, 2021

No incidents reported today.

Jan 22, 2021

No incidents reported.

Jan 21, 2021

Desk e Portal.blip.ai unavailable

Postmortem - Read details
Jan 21, 18:03 GMT-03:00

Resolved - This incident has been resolved.
Jan 21, 18:03 GMT-03:00

Update - We are continuing to monitor for any further issues.
Jan 21, 17:18 GMT-03:00

Update - We are continuing to monitor for any further issues.
Jan 21, 17:13 GMT-03:00

Monitoring - Status: Monitoring

Scenario: The service webapp instance was increased from 6 to 10 and all the accesses have normalized. Our team is monitoring the scenario to guarantee Blip’s stability for all customers. The main cause of the problem is still under investigation. When we have identified the reason for this error, we will be reporting in the postmortem

Incident Location: Blip Desk and Portal

Affected Users: Enterprise, Business and Standard
Jan 21, 17:04 GMT-03:00

Update - Status: Under investigation

Scenario: The service webapp instance was increased and related components restarted. A good part of the accesses have already normalized. However, because of the large volume of inputs, isolated failure occurrences persist.

Incident Location: Blip Desk and Portal

Affected Users: Enterprise, Business and Standard

Next Update: in 30 minutes
Jan 21, 16:38 GMT-03:00

Identified - Status: Identified

Scenario: Our monitoring identified a connection failure with the database responsible for authenticating the users of the blip, causing failure in accessing the Portal and Desk.

Incident Location: Blip Desk and Portal

Affected Users: Enterprise, Business and Standard

Next Update: in 15 minutes
Jan 21, 16:13 GMT-03:00

Update - We are continuing to investigate this issue.
Jan 21, 15:33 GMT-03:00

Investigating - We identified unavailability of access to the Portal and Desk.
Jan 21, 15:15 GMT-03:00

Jan 20, 2021

No incidents reported.

Jan 19, 2021

No incidents reported.

Jan 18, 2021

No incidents reported.

Jan 17, 2021

No incidents reported.

Jan 16, 2021

No incidents reported.

Jan 15, 2021

No incidents reported.

Jan 14, 2021

No incidents reported.

Jan 13, 2021

No incidents reported.

Jan 12, 2021

No incidents reported.

Jan 11, 2021

Portal Blip and Blip Desk - Account Issue

Resolved - Fault identified:

It was identified in the application of the account, which is responsible for the administration of customer accounts within the platform.

Reflection for the client:

The client had a login failure within the portal and blipdesk

Correction applied:

‌We made a scale up on the database to resolver this issue.
We are investigating the failure that caused this error.

Root Cause:

Unfortunately it was not possible to identify the root cause, but we have an internal problem on investigation.

Start date / time: 16:56
End date / time: 17:30
Jan 11, 17:30 GMT-03:00

Investigating - We identified a failure to access the portal and the service tool.
Jan 11, 16:56 GMT-03:00

Jan 10, 2021

No incidents reported.

Jan 9, 2021

No incidents reported.

Related