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.

Sep 29, 2026

Blip Desk [Low performance]
Resolved - We identified a service outage affecting Blip Desk operations.
This resulted in customer service difficulties: messages sent by customers failed to appear on the agent's screen, while responses sent by agents neither reached the customer nor were saved to the history; additionally, contact details and Desk history older than 90 days were not displayed.
Actions taken: Mapping of error/warning spikes on the server (approximately 60,000 records/min) related to processing failures and "Destination not found" errors. Analysis of infrastructure, WebSocket connections, pod integrity, and Starter component configurations. Controlled shutdown of Starter instances to isolate concurrency issues regarding message consumption from Confluent topics. Restoration and validation of normal message flow for Desk and WhatsApp. Restart and final real-time monitoring tests to confirm environment stability.
Sep 29, 11:04 GMT-03:00
Identified - Issues operating Blip Desk: messages sent by customers are logged but do not appear to the agent; agent responses neither reach customers nor save to the history; and contact data and history older than 90 days are unavailable. Actions taken: Identified spikes in server errors/warnings (approx. 60,000 records/min) related to processing failures and "Destination not found" errors. Mapped and defined the impact on the customer base and Desk workflows. Analyzed infrastructure, WebSocket communication, pod integrity, and the Starter component. Performed a controlled shutdown of Starter instances to isolate potential consumer concurrency issues in Confluent. Restored and normalized message flow for Desk and WhatsApp following the Starter shutdown.
Sep 29, 10:43 GMT-03:00
Update - Issues with support interactions via Blip Desk: messages sent by agents are neither displayed on the screen nor recorded in the history/threads.
Additionally, while messages sent by customers are logged, they do not appear to agents or encounter flow errors.
High volume of warnings and server processing errors identified (envelope processing failures and "Destination not found" errors).
Verification of Starter component configurations and instances, confirming isolated instances thus far.
Sep 29, 10:01 GMT-03:00
Investigating - We are currently experiencing low performance on Blip Desk.

Impact:
Slowness when using Blip Desk.

Update:
Our support team is actively working on it.
Sep 29, 09:21 GMT-03:00

Sep 28, 2026

No incidents reported.

Sep 27, 2026

No incidents reported.

Sep 26, 2026

No incidents reported.

Sep 25, 2026

No incidents reported.

Sep 24, 2026

No incidents reported.

Sep 23, 2026

No incidents reported.

Sep 22, 2026

No incidents reported.

Sep 21, 2026

No incidents reported.

Sep 20, 2026

No incidents reported.

Sep 19, 2026

No incidents reported.

Sep 18, 2026

No incidents reported.

Sep 17, 2026

No incidents reported.

Sep 16, 2026

No incidents reported.

Sep 15, 2026

Active Message Sending Instability
Resolved - The incident has been resolved. The issue was caused by a peak in the volume of individual campaign sends, which overloaded message processing and caused slowness. Adjustments were applied to improve processing performance, reduce excessive resource consumption, and separate individual and batch campaign processing. The service is now fully normalized.
Sep 15, 11:34 GMT-03:00
Identified - A correction has been applied, improving message processing performance and gradually clearing pending messages. We are monitoring the remaining pending messages and request volume to confirm full stabilization. A new update will be provided within 30 minutes or sooner if relevant information becomes available.
Sep 15, 10:39 GMT-03:00
Update - We are continuing to investigate an issue that may be causing difficulties when sending active messages, with some messages appearing as "NOT PROCESSED". Technical teams are performing sending tests and analyzing information to identify the cause of the processing errors. The next update is expected within 30 minutes or as soon as new information becomes available.
Sep 15, 10:30 GMT-03:00
Investigating - We are investigating an issue that may be causing difficulties when sending active messages, with some messages appearing as "NOT PROCESSED". Technical teams are actively analyzing the situation. The next update is expected within 30 minutes or as soon as new information becomes available.
Sep 15, 10:03 GMT-03:00
Incident History Powered by Atlassian Statuspage