All Systems Operational

Uptime over the past 90 days. View historical uptime.
Desk Operational
Blip Platform Operational
CRM Operational
Core Operational
Analytics Operational
Artificial Intelligence Operational
Portal Operational
Cloud Infrastructure Operational
Agendador Operational
Channels Operational
WhatsApp Operational
Telegram Operational
Messenger Operational
BlipChat Operational
Workplace Chat Operational
BusinessChat Operational
Skype Operational
E-mail Operational
Instagram Operational
SMS Operational
Hosting Enterprise Operational
Bot Builder Operational
Bot Router Operational
Hosting Business Operational
Bot Builder Operational
Bot Router Operational
Packs Operational
Blip Go Personal 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.

No incidents or maintenance related to this downtime.

Oct 28, 2026

No incidents reported today.

Oct 27, 2026

Issue affecting access to the Portal and the Desk
Resolved - We identified an issue affecting access to the Portal and the Desk across certain clusters. Our external infrastructure and edge provider implemented a permanent fix at 11:52 BRT and continued to monitor the results. Affected clients have confirmed that access to the Portal and Desk has been successfully restored, and validation tests conducted by our technical team have verified the full recovery of network routes and the stabilization of the platform.
Oct 27, 14:22 GMT-03:00
Monitoring - We have identified an issue affecting access to the Portal and the Desk across certain clusters. The external provider applied a fix at 11:52 BRT and continues to monitor the outcome. Our support team has provided testing instructions to the affected clients, and we are currently in the validation phase, awaiting feedback from users to confirm that access has been fully stabilized for them.
Oct 27, 12:31 GMT-03:00
Update - We have identified an issue affecting access to the Portal and the Desk across certain clusters. This behavior is linked to an external infrastructure problem involving a partner/vendor; it does not directly impact the platform as a whole, but rather affects specific networks and locations. Our technical team is currently validating measures to provide a workaround for clients while the vendor works on a definitive resolution.
Oct 27, 11:34 GMT-03:00
Identified - We have identified an issue affecting access to the Portal and the Desk across certain clusters. This behavior is linked to an external infrastructure problem involving a partner/vendor; it does not directly impact the platform as a whole, but rather affects specific networks and locations. Our technical team is currently validating measures to provide a workaround for clients while the vendor works on a definitive resolution.
Oct 27, 11:07 GMT-03:00
Update - We have identified an issue affecting access to the Portal and the Desk across certain clusters. Our team?s internal tests continue to function normally, which confirms that the root cause of the problem does not lie within Blip?s internal infrastructure. Technical analysis indicates that the timeout errors are linked to incompatibilities with edge partners or third-party firewall/routing rules within the networks of specific service providers and clients.
Oct 27, 10:44 GMT-03:00
Update - We have identified an issue affecting access to the Portal and the Desk across certain clusters.
An analysis of routes and connectivity reveals that traffic from clients in specific regions or units is being redirected to different servers, while access remains normal in other locations. Since our internal team is experiencing no such instability, our primary hypothesis is that the issue stems from a failure within edge services or third-party network/infrastructure providers.
Oct 27, 10:14 GMT-03:00
Investigating - We have identified an issue affecting access to the Portal and the Desk across certain clusters. Clients report that screens remain in a continuous loading state, preventing them from viewing or using the services.
This slowness/freezing during loading has been observed in specific environments. The technical team has been alerted, and a crisis response team (SWAT) has been immediately mobilized to diagnose the issue.
Oct 27, 09:54 GMT-03:00

Oct 26, 2026

No incidents reported.

Oct 25, 2026

No incidents reported.

Oct 24, 2026

No incidents reported.

Oct 23, 2026

No incidents reported.

Oct 22, 2026

No incidents reported.

Oct 21, 2026

No incidents reported.

Oct 20, 2026

No incidents reported.

Oct 19, 2026

No incidents reported.

Oct 18, 2026

No incidents reported.

Oct 17, 2026

No incidents reported.

Oct 16, 2026

No incidents reported.

Oct 15, 2026

Unavailability in the operation of the bots
Resolved - The issue affecting bot operations has been resolved. The failure, which originated at the external provider of the database service used by the platform, affected the message flow of bots, including message reception, processing, and response delivery, message routing, and conversation history. We worked together with the provider on the fix, restarted some services, and validated the environment, which remains under monitoring. We ask customers to validate that their operations are working normally and, if any behavior persists, to contact support with the bot, the affected contact, and the date and time of the occurrence.
Oct 15, 18:29 GMT-03:00
Update - Most of the environment is already recovering gradually. The service responsible for message routing and for associating notifications with received messages, the service responsible for conversation context and history, and the completion of history loading in some specific databases are still awaiting full restoration. Until these items are completed, failures or delays may occur in message routing, message status updates, and the display of conversation history. We are working together with the database service provider to complete the restoration and validating services as they are normalized. We will provide another update within 30 minutes or as soon as new information becomes available.
Oct 15, 17:41 GMT-03:00
Update - We are still awaiting the full restoration of services affected by a failure at the external provider of the database service used by the platform. Part of the environment is already recovering gradually, while other services are still awaiting the completion of corrective actions to resume operation. The impact continues to affect the message flow of bots, including message reception, processing, and response delivery for both automated interactions and Desk. We are working together with the provider to resolve the issue and validating services as they are restored. We will provide another update within 30 minutes or as soon as new information becomes available.
Oct 15, 17:11 GMT-03:00
Monitoring - Some services are already recovering gradually, while others remain unavailable. The instability is caused by a failure at the external provider of the database service used by the platform, and we are working together with the provider to resolve the issue. The impact affects the message flow of bots, including message reception, processing, and response delivery for both automated interactions and Desk. We continue tracking the recovery and validating restored services until the environment is fully normalized. We will provide another update within 30 minutes or as soon as new information becomes available.
Oct 15, 16:39 GMT-03:00
Update - We have identified that the instability is caused by a failure at the external provider of the database service used by the platform. The inconsistency originated in the provider's environment, not in our infrastructure, and affects the overall message flow of bots, including message reception, processing, and response delivery for both automated interactions and Desk. Normalization depends on corrective actions being carried out by the provider, and recovery is progressing gradually. We continue following up with the provider and, once the service is restored, we will validate the message flow and operational stability. We will provide another update within 30 minutes or as soon as new information becomes available.
Oct 15, 16:11 GMT-03:00
Update - We continue working on the incident related to an external component used in our database infrastructure. The impact is not limited to Desk and affects the overall message flow of bots, including message reception, processing, and response delivery for both automated and human-assisted interactions. Corrective measures are still being applied and services are recovering gradually. As recovery progresses, our technical teams will validate the end-to-end message flow and the operational stability of the affected environments. We will provide another update within 30 minutes or as soon as new information becomes available.
Oct 15, 15:46 GMT-03:00
Update - We have identified inconsistencies in an external component used within our database infrastructure, which integrates various resources required for our operations. This issue may affect message processing and the functionality of bots. An investigation is underway. Measures to address the identified inconsistencies are already being implemented, and we are awaiting a gradual resumption of services to validate operational stability.
Oct 15, 15:36 GMT-03:00
Investigating - We have identified an issue that is causing the bots to be unavailable. Our engineering team is currently working to investigate the situation, determine the root cause of the failure, and define the necessary steps to restore bot functionality.During our investigation, we identified connection issues and problems with database operations. Our technical teams are continuing to analyze the situation; we have observed the restoration of connections, the recovery of conversation history, and the return to normal operation for some bots.
Oct 15, 14:58 GMT-03:00

Oct 14, 2026

No incidents reported.

Incident History Powered by Atlassian Statuspage