Live / Blip / Incident
Blip: Unavailability in the operation of the bots
Blip · blip.aiCritical outageResolved2026-10-15 21:29 UTC
Public — what happened
Summary
Blip reported a critical outage beginning at 17:58 UTC on 2026-10-15 that left its bots unavailable, disrupting how messages were received, processed and answered for both automated conversations and its Desk human-support tool. Blip said the problem came from a failure at the outside company that provides its database service, and that fixing it depended on that provider's work. Services came back in stages, with message routing, status updates and conversation history among the last pieces still being restored. The incident was marked resolved at 21:29.
Affected
Desk, BlipChat
Timeline
- Started — 2026-10-15 17:58 UTC
- Investigating — 2026-10-15 17:58 UTC (4 updates)
- Monitoring — 2026-10-15 19:39 UTC (3 updates)
- Resolved — 2026-10-15 21:29 UTC · 3h 30m 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 43, 2026, our weekly internet health report.