Live / Liquid Web / Incident
Liquid Web: eMudhra Certificate Authority Security Issue
Liquid Web · liquidweb.comidentified2026-10-28 22:05 UTC
Public — what happened
Summary
Liquid Web said it became aware on 2026-10-27 of a reported security problem involving compromised eMudhra Certificate Authority certificates that may be in the trust lists used in some of its environments. The company said it had found no service interruptions or confirmed customer impact, and its security and engineering teams were working out how to respond. On 2026-10-28 it said it would update its infrastructure to distrust the affected eMudhra intermediate certificates, with no downtime or reboots needed. Liquid Web said that afterward, outgoing secure connections to services depending on those certificates would be rejected, so customers using them should get certificates reissued by an unaffected authority. The incident was not marked resolved.
Timeline
- Started — 2026-10-27 15:40 UTC
- Investigating — 2026-10-27 15:40 UTC
- Identified — 2026-10-28 22:05 UTC
- Ongoing at last check.
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.