Live / Blip / Incident
Blip: Issue affecting access to the Portal and the Desk
Blip · blip.aiMajor incidentResolved2026-10-27 17:22 UTC
Public — what happened
Summary
Blip reported a major problem that left some customers unable to use the Portal and the Desk, with screens stuck loading in certain clusters. The company said it began at 12:54 UTC on 2026-10-27, affected only specific regions and networks, and that its own internal tests worked normally. Blip said it traced the problem to an external partner or vendor, not its own infrastructure, and was working on a workaround while the vendor handled a lasting fix. By 15:31 UTC Blip said the provider had applied a fix and it was waiting on customer feedback, and the incident was marked resolved at 17:22 UTC.
Affected
Desk, Portal
Timeline
- Started — 2026-10-27 12:54 UTC
- Investigating — 2026-10-27 12:54 UTC (3 updates)
- Identified — 2026-10-27 14:07 UTC (2 updates)
- Monitoring — 2026-10-27 15:31 UTC
- Resolved — 2026-10-27 17:22 UTC · 4h 28m 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 45, 2026, our weekly internet health report.