Live / Liquid Web / Incident
Liquid Web: Apache Service Disruptions
Liquid Web · liquidweb.comResolved2026-10-26 18:12 UTC
Public — what happened
Summary
Liquid Web said it began looking into service disruptions affecting Apache web servers on October 21, 2026 at 15:33 UTC. The company said early findings tied the problem to a compatibility issue with mod_security after a recent release. About two hours later, at 17:44 UTC, it said it had found the issue and applied a fix, and affected servers were running again while it watched for any recurrence. The incident was marked resolved on October 26 at 18:12.
Timeline
- Started — 2026-10-21 15:33 UTC
- Investigating — 2026-10-21 15:33 UTC
- Monitoring — 2026-10-21 17:44 UTC
- Resolved — 2026-10-26 18:12 UTC · 5 days 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 44, 2026, our weekly internet health report.