Live status
A few seconds: the status is read the moment you open this page.
Read every 5 minutes from the official status page of OVHcloud. 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 OVHcloud is not responding? Here is what the host’s Web Cloud status page says (shared hosting, domains, DNS, databases), read every five minutes, 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 status-ovhcloud.com portal groups six pages; the one that matters for a showcase site or an online store is “Web Cloud”: shared hosting in the Gravelines (GRA) and Beauharnois (BHS) data centres, domains, DNS, databases, CDN. That is the one read here.
Source: OVHcloud, Web Cloud status27 October 2026
The “Filerz 956 Cluster129” incident was opened at 09:36 UTC with a major impact: “customers were temporarily unable to access their sites hosted on the affected filerz”. The same day, an incident on cluster 121 (10:28 to 13:59 UTC) did not affect access to the sites.
Source: OVHcloud, Web Cloud incident historyCluster
Each OVHcloud web hosting plan is attached to a cluster (cluster021, cluster121…) shown in the customer area, under Hosting plans. Incidents are announced per cluster: if yours is not mentioned, the outage is probably not that one.
Source: OVHcloud, diagnosing an unreachable sitePermanent maintenance
On the Web Cloud page, around ten clusters appear “under maintenance” continuously: these are background operations, not outages. This page does not count them as incidents; only the incidents declared by OVHcloud are.
Source: OVHcloud, Web Cloud statusOfficial support: the OVHcloud guide “What to do if my site is unreachable?” details the checks on the customer side (DNS, .htaccess, PHP, quotas) and how to open a ticket from the customer area. Phone support can be reached on 1007 from France.
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
Look at the status above first: an ongoing Web Cloud incident on your cluster explains everything, and all you can do is wait. If nothing is announced, open your customer area, under Hosting plans: an expired hosting plan, a domain that was not renewed or a quota alert are shown there. Then, a 500 error or a blank page point to your site (PHP, plugin, database); a timeout rather points to the DNS or the server.
From 21 to 23 October 2026, OVHcloud rolled out the PHP fixes on all its shared clusters. A site left on an old PHP version, or whose plugin is no longer compatible, may show a blank page or a 500 error after this change. The blog guide “changing the PHP version at OVH” explains where to read and change the version in the customer area.
The cluster incidents published in October 2026 lasted from a few minutes to a few hours: three and a half hours for cluster 121 on 27 October, a little over five hours for clusters 120, 126 and 131 on 26 October. File server (filerz) incidents can last longer, as they sometimes require a restore.
The specific terms of OVHcloud web hosting include an availability commitment and penalties in the form of a credit note, to be requested from support with the incident references. Nothing is automatic: keep the start and end time shown on the status page.
Blog
The guides written for sites hosted at OVHcloud, and what breaks a site without the host being at fault.
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.
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.
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.