Live

[BHS/GRA][Web Hosting] - Cluster151, Cluster123, Cluster127 incident notification

Major outageOfficial update
0

Web Hosting Cluster151 in BHS is temporarily unavailable, and customers cannot access websites hosted on it. OVHcloud reports that the root cause is a software issue and that the cause is identified. Cluster123 and Cluster127 are operational again.

State

Identified

Started

Ongoing for

44 min

Worst impact

Major outage

Timeline

4 updates
01:0901:2001:3101:4201:53
Major outageUpdate postedTimes in UTC

Investigating

30 min 69%

Identified

14 min 31%

Updates

Times in UTC

As posted by OVHcloud

Identified

Please find an update of this incident below : Update : Cluster123 has been operational again since 19/11/2026 01:01 UTC and Cluster127 since 19/11/2026 01:27 UTC. Impacted Service(s) : Web Hosting Cluster151 is temporarily unavailable. Customers Impact : Customers are temporarily unable to access their websites hosted on the affected cluster. Root Cause : This incident is caused by a software issue. Ongoing Actions : Our teams are actively working to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

Identified

We are currently experiencing an incident affecting our Web Hosting offering in the Cluster151 and Cluster127. The root cause has been identified. Please find the details of this incident below : Start time : 19/11/2026 00:30 UTC Update : Cluster123 has been operational again since 19/11/2026 01:01 UTC. Impacted Service(s) : Web Hosting Cluster151 and Cluster127 are temporarily unavailable. Customers Impact : Customers are temporarily unable to access their websites hosted on the affected clusters. Root Cause : This incident is caused by a software issue. Ongoing Actions : Our teams are actively working to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

Investigating

We are continuing to investigate this issue.

Investigating

We are currently experiencing an incident affecting our Web Hosting offering, which is causing temporary availability issues in the Cluster151 in BHS and Cluster123 in GRA. Please find the details of this incident below : Start time : 19/11/2026 00:30 UTC Impacted Service(s) : Web Hosting Cluster151 and Cluster123 are temporarily unavailable. Customers Impact : Customers are temporarily unable to access their websites hosted on the affected clusters. Ongoing Actions : Our teams are investigating to determine the origin of the incident to fix it. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

Affected components

6
Cluster151Cluster123Cluster127Web Hosting || Datacenter GRA - Cluster123Web Hosting || Datacenter GRA - Cluster127Web Hosting || Datacenter BHS - Cluster151

OVHcloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

195

Days with an incident

90

Median duration

1 h 41 min

This incident

56% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

24 days
median 1 h 41 min
90 days agoToday

Other OVHcloud incidents

All incidents

Follow OVHcloud

Your coding agent knows when OVHcloud is down, and tells you when a failure is theirs, not yours. You can also get OVHcloud incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "ovhcloud" and tell me if OVHcloud has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=ovhcloud
Slack
/feed subscribe https://outages.live/feed.xml?providers=ovhcloud

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane