[BHS/GRA][Web Hosting] - Cluster151, Cluster123, Cluster127 incident notification
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 updatesInvestigating
30 min 69%
Identified
14 min 31%
Updates
Times in UTCAs posted by OVHcloud
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.
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.
We are continuing to investigate this issue.
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
6OVHcloud in the last 90 days
Full historyIncidents in 90 days
195
Days with an incident
90
Median duration
1 h 41 min
This incident
56% shorter than the median
Other OVHcloud incidents
All incidentsOVHcloud·[GRA][Web Hosting] - Cluster129/Filerz956 incident notification
Web Hosting is slow on Cluster129 in the GRA datacenter. Filerz956 shows latency on Cluster129. OVHcloud reports the status as investigating.
OVHcloud·[GRA][Web Hosting] - Cluster129/Filerz956 incident notification
Web Hosting on Cluster129 and Filerz956 in the GRA datacenter had temporary latency. OVHcloud reports that the incident is resolved. The incident lasted 18 minutes.
OVHcloud·[LIM/FRA][Infrastructure] - Backbone incident notification
The OVHcloud backbone link between LIM and FRA had increased latency and packet loss. OVHcloud reports that the incident is resolved and lasted 50 minutes, from 14:55 to 15:45 UTC. The cause was a network equipment issue.
OVHcloud·[GRA1][Dedicated Servers] - Rack G125A23 incident notification
Some Dedicated Servers in rack G125A23 in the GRA region were temporarily unavailable. OVHcloud reports that the incident is resolved and lasted 3 hours and 55 minutes.
OVHcloud·[SBG5][Dedicated Servers] - Rack SBG0506B04C Incident Notification
The vRack Private Network does not work on Dedicated Servers in rack SBG0506B04C in the SBG region. OVHcloud reports that the incident is resolved and that it lasted from 11:54 UTC to 15:23 UTC.
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.
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.
https://outages.live/feed.xml?providers=ovhcloud/feed subscribe https://outages.live/feed.xml?providers=ovhcloudFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane