Live status
A few seconds: the status is read the moment you open this page.
Read every 5 minutes from the service status page of LWS. Open the status page
Your site is unreachable and you do not know where it comes from? Send me its link, I take a look and reply within 24 hours.
Send the link to my siteYour site hosted at LWS is not responding? Here is what the host’s service status page says (web, mail, SQL, DNS, cPanel, Plesk, VPS), read every five minutes, with the events of the last seventy-two hours, and how to tell whether the outage comes from the host or from your site.
Page maintained by Léo Guillaume, freelance developer near Rennes, France, who has been bringing websites and software hosted with these providers back online since 2019.
Updated on
You or the host?
When the status page is green, the outage is almost always on the site, the domain or the cache.
If another site hosted in the same place responds, the outage does not come from the host but from your site, your domain name or your cache.
“This site can’t be reached” or a timeout point to the server or the DNS; a 500 error or a blank page point to the site itself (PHP, plugin, database).
An expired domain or DNS records changed the day before give the same symptoms as an outage. The host’s customer area or the registrar shows the expiry date.
What you need to know
Re-read on 27 October 2026 on the host’s official pages.
Status page
The “Service status” page of the LWS help centre shows a global status and a status per service (network, web, mail, SQL, VPS, DNS, data centre, cPanel, Plesk, backups) with four levels: all good, scheduled maintenance, ongoing disruption, ongoing incident. It only keeps the events of the last 72 hours: this page keeps the ones it has seen.
Source: LWS, service status27 October 2026
On 27 October 2026, LWS carried out a maintenance on the Plesk service from 08:00 to 11:35 and an improvement of the mail service from 08:00 to 08:32, both announced then closed on the status page.
Source: LWS, service statusSince 23 October 2026
On 23 October 2026 at 18:09, LWS applied a Node.js security fix on its cPanel servers, closed on 27 October at 17:10. The same week, the page reported support response delays, classified as a “disruption”.
Source: LWS, service statusHTTP errors
When the server responds but the site shows an error, LWS documents the troubleshooting of HTTP codes and the diagnosis of a 500 error on a cPanel hosting plan: error log, .htaccess, PHP version, extensions.
Source: LWS, diagnosing a 500 errorOfficial support: the LWS help centre details the troubleshooting of HTTP errors and 500 errors on cPanel. LWS support answers by ticket from the customer area and by phone during business hours.
During the outage
In order, without breaking anything.
Open your site from another network (4G rather than your router) and in private browsing. If it works elsewhere, the problem is local: cache, router DNS, firewall.
An incident announced by the host gets fixed without you: no need to touch the site. Note the start time for your own communication.
A word on your Google listing, your social networks or your voicemail avoids the phone calls. Give the return time announced by the host rather than a promise.
One isolated outage is no reason to change host. Three outages in a quarter, or a support team that stays silent, are: a migration takes a week to prepare.
Frequently asked questions
Read the status above: “ongoing incident” or “ongoing disruption” on the web, SQL or DNS service concerns you; a scheduled maintenance is announced in advance with its end time. If all is well on the LWS side, the outage is on your site: the LWS help centre explains how to read the error log from cPanel.
LWS only shows the events of the last three days. This page keeps in memory the events it has read and the changes of state it has observed, so that you can find the date and duration of a past outage.
The PHP fixes of October 2026 were rolled out on the shared servers. A site left on an old PHP version, or a plugin incompatible with the version chosen in cPanel, may show a blank page since then. The version is set from the “Select PHP Version” tool in cPanel.
LWS’s general terms include an availability guarantee and a goodwill gesture on request, not an automatic refund. Note the start and end time of the downtime as it appears on the status page, and attach it to your ticket.
Blog
The guides written for sites hosted at LWS, and what breaks a site without the host being at fault.
Two critical vulnerabilities in PHP were patched on October 21, 2026. Are your WordPress sites, PrestaShop or WooCommerce stores, custom applications, or internal networks at risk? Learn who is impacted, what your hosting provider is doing, and what actions you should take today.
Since October 18, 2026, stolen UpdraftCentral keys have been used to install fake plugins and hidden accounts on WordPress sites—even those kept up to date. Here are the seven checks to perform today, in the exact order I follow them on a client’s site.
Restoring a backup isn’t enough: if done too late, it may still contain the backdoor; if restored without patching the vulnerability, the site will likely be compromised again within days. Here’s how to select the right backup, restore it properly, and seal the breach immediately afterward.
OVHcloud web hosting: Where to find your PHP version, how to switch to 8.3 or 8.4 from the customer portal or the .ovhconfig file, which version to select, and what OVH announced on October 21st.
At o2switch, the default cPanel PHP version is 8.1, which no longer receives official patches. Where to navigate to switch to 8.3 or 8.4, which version to choose, and what o2switch did on October 21st.
Send me the link to your site: I find out where the outage comes from (domain, certificate, PHP, plugin, database) and tell you what to do within 24 hours. Free, no commitment.