Live / Liquid Web / Incident
Liquid Web: Errors with Object Storage and Block Storage
Liquid Web · liquidweb.comMajor incidentResolved2026-10-27 13:20 UTC
Public — what happened
Summary
Liquid Web said it was looking into problems affecting its Cloud Object Storage and Block Storage services, which it classed as a major incident starting at 18:17 UTC on 2026-10-26. Its engineers began reviewing the systems, and the company did not state a cause in its updates. About half an hour later, at 18:52 UTC, Liquid Web said a fix was in place and it was watching the results, and the incident was marked resolved at 13:20 UTC on 2026-10-27.
Affected
Object Storage
Timeline
- Started — 2026-10-26 18:17 UTC
- Investigating — 2026-10-26 18:17 UTC
- Monitoring — 2026-10-26 18:52 UTC
- Resolved — 2026-10-27 13:20 UTC · 19h 04m 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 Liquid Web 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 Liquid Web: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Liquid Web report →
More from Liquid Web
Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.