Live / Blip / Incident
Blip: Blip Desk [Low performance]
Blip · blip.aiMajor incidentResolved2026-09-29 13:43 UTC
Public — what happened
Summary
Blip reported a major problem with its Blip Desk tool beginning at 12:21 UTC on September 29, 2026, in which customer messages were recorded but not shown to agents, agent replies failed to reach customers or be saved, and contact records and history older than 90 days could not be accessed. The company said it observed a large surge of server errors, around 60,000 per minute, tied to processing failures and "Destination not found" messages, and examined its infrastructure and a component called Starter. Blip said that after shutting down Starter instances in a controlled way to rule out a possible concurrency issue, message flow for Desk and WhatsApp returned to normal. The incident is listed as resolved at 13:43, though its status still reads as identified.
Timeline
- Started — 2026-09-29 12:21 UTC
- Resolved — 2026-09-29 13:43 UTC · 1h 23m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Blip against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Blip: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Blip report →
More from Blip
Covered in The Squid’s Ink, Week 41, 2026, our weekly internet health report.