Skip to main content

Is Liquid Web Down?

No — Liquid Web is up

Reachable from all 8 checked regions

Average response time: 90ms

Last checked · checks run every 6 hours

Official status page: https://status.liquidweb.com

Liquid Web uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
91ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 16 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

16-day clean streak
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: no data
Aug 4: no data
Aug 5: no data
Aug 6: no data
Aug 7: no data
Aug 8: 100.00% uptime, 16 checks
Aug 9: 100.00% uptime, 32 checks
Aug 10: 100.00% uptime, 32 checks
Aug 11: 100.00% uptime, 32 checks
Aug 12: 100.00% uptime, 40 checks
Aug 13: 100.00% uptime, 32 checks, 1 incident
Aug 14: 100.00% uptime, 32 checks
Aug 15: 100.00% uptime, 32 checks
Aug 16: 100.00% uptime, 26 checks
Aug 17: 100.00% uptime, 32 checks
Aug 18: 100.00% uptime, 32 checks
Aug 19: 100.00% uptime, 37 checks
Aug 20: 100.00% uptime, 32 checks
Aug 21: 100.00% uptime, 31 checks
Aug 22: 100.00% uptime, 32 checks
Aug 23: 100.00% uptime, 32 checks
Jul 25 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

gru
55ms
DNS 0ms TCP 2ms TLS 11ms TTFB 29ms
iad
57ms
DNS 0ms TCP 1ms TLS 9ms TTFB 31ms
jnb
312ms
DNS 0ms TCP 0ms TLS 10ms TTFB 293ms
lax
64ms
DNS 0ms TCP 2ms TLS 14ms TTFB 44ms
lhr
68ms
DNS 0ms TCP 2ms TLS 14ms TTFB 41ms
nrt
53ms
DNS 0ms TCP 2ms TLS 15ms TTFB 32ms
ord
59ms
DNS 0ms TCP 2ms TLS 13ms TTFB 35ms
sin
54ms
DNS 1ms TCP 2ms TLS 13ms TTFB 31ms
sjc
60ms
DNS 0ms TCP 3ms TLS 12ms TTFB 38ms

What Liquid Web does

Liquid Web is a managed hosting provider selling dedicated servers, cloud VPS, VMware private cloud and managed hosting, aimed at businesses that want someone else running the infrastructure. Customers reach their servers through a management portal and control panels such as cPanel, Plesk and InterWorx. A Liquid Web incident takes the sites hosted on it down with it.

What an outage looks like

Liquid Web reports DNS, API, Cloud Dedicated, Cloud VPS, VMware Cloud, object storage, load balancers, business email and the management portal separately, along with per-data-centre status for DC2, DC3, DC4 and EU-AMS. Symptoms follow the component: sites unreachable while the portal works, DNS resolution failing for hosted domains, control panels timing out, or email delivery stopping while websites stay up.

What to do about it

Check status.liquidweb.com and find your data centre, since incidents are frequently confined to one facility and the page reports DC2, DC3, DC4 and EU-AMS individually. Liquid Web posts scheduled maintenance there in advance, including network upgrades, so check whether the window was announced before treating it as a fault. Support chat, case and phone are tracked as components too.

Is it down for everyone, or just you?

If this page says Liquid Web is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

K
Kinsta
W
WP Engine
D
DreamHost
H
Hostinger

Liquid Web outage FAQ

Is my site down or is it the whole data centre?
Liquid Web's status page reports each data centre separately, so this is answerable in one look. If DC2, DC3, DC4 or EU-AMS is flagged and it is the one hosting your server, the outage is facility-wide and there is nothing to fix on your side. If every data centre reads normal, the problem is more likely your server, your application or DNS.
Does a Liquid Web outage affect email as well as websites?
Business Email is a separate component from the hosting services, so the two can fail independently. Sites can be unreachable while mail continues, or mail can stop while sites are fine. Incoming mail is generally queued by the sending server and retried rather than bounced outright, so a short outage delays delivery rather than losing messages.
How do I tell scheduled maintenance from an outage?
Liquid Web publishes maintenance windows on the same status page as incidents, and recent entries have included core network optimisation and a network infrastructure capacity upgrade. Announced work appears ahead of time with a window attached. If your site went down without a matching entry, treat it as an incident and open a support case rather than waiting it out.
Can I still manage my server when the portal is down?
Usually. The management portal and control panels are tracked separately from the servers themselves, so losing the portal does not mean your server has stopped. Direct access over SSH or an existing control panel session often still works. Liquid Web also reports support chat, case and phone as components, so if the portal and support are both flagged, escalation routes are limited until it clears.

How we measure this

  • We request Liquid Web's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Liquid Web publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Liquid Web goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required