[GRA][Web Hosting] - Filerz 956 Cluster029/129 incident notification
We are pleased to inform you that the incident affecting our Web Hosting offering has been resolved. Start time : 27/10/2026 09:00 UTC End time : 27/10/2026 12:00 UTC Root Cause : This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.
The latest update from OVHcloud.
State
Resolved
Started
6 d ago
2026-10-27 09:36 UTC
Lasted
2 days
until 2026-10-29 15:20 UTC
Worst impact
Partial outage
Timeline
6 updatesInvestigating
4 h 31 min 8%
Monitoring
26 h 30 min 49%
Identified
22 h 43 min 42%
Updates
Times in UTCAs posted by OVHcloud
We are pleased to inform you that the incident affecting our Web Hosting offering has been resolved. Start time : 27/10/2026 09:00 UTC End time : 27/10/2026 12:00 UTC Root Cause : This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.
We are currently experiencing an incident affecting our Web Hosting offering in the Cluster129. The root cause has been identified. Please find the details of this incident below : Start time : 27/10/2026 09:00 UTC Impacted Service(s) : Filerz956 on Cluster129 is experiencing instability. Customers Impact : Customers may experience latency when accessing their websites hosted on Filerz956. 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.
Please find an update of this incident below : Update : Filerz956 on the Cluster029/129 is still experiencing instability. Ongoing Actions : Our teams are still working on this issue and remain mobilised 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.
Please find an update of this incident below : Update : Filerz956 on the Cluster029/129 is experiencing instability again. Ongoing Actions : Our teams are mobilised 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 would like to inform you that our service has been fully restored as of 27/10/2026 12:00 UTC. Monitoring is still in place to ensure long-term stability. Please find the details of this incident below : Start time : 27/10/2026 09:00 UTC Impacted Service(s) : Filerz 956 was unreachable on Web Hosting Cluster129. Customers Impact : Customers were temporarily unable to access their websites hosted on the affected filerz. Root Cause : This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.
We are currently investigating an incident affecting our Web Hosting offering, which is causing temporary availability issue in the Filerz 956 Cluster129. Here are some supplementary details : Start time : 27/10/2026 09:00 UTC Impacted Service(s) : Filerz 956 is unreachable on the Cluster129. Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
Affected components
2OVHcloud in the last 90 days
Full historyIncidents in 90 days
217
Days with an incident
90
Median duration
1 h 35 min
This incident
34× the median
Other OVHcloud incidents
All incidentsOVHcloud·[SBG8][Virtual Private Servers] - VPS Incident Notification
Some Virtual Private Servers in the SBG8 region were temporarily unreachable. The incident affected some VPS in the SBG region. OVHcloud identified a network equipment issue as the cause. OVHcloud resolved the incident. The incident started at 17:55 UTC and ended at 19:54 UTC.
OVHcloud·[SBG6/8][Virtual Private Servers] - VPS Incident Notification
Some Virtual Private Servers in the SBG5, SBG6 and SBG8 regions were unreachable. OVHcloud reports that the incident is resolved. It lasted from 17:55 UTC to 19:30 UTC.
OVHcloud·[RBX3][Dedicated Servers] - Rack 46E19 Incident Notification
OVHcloud reports that servers in Rack 46E19, RBX3, were not accessible through the IPMI interface. The incident was caused by a network equipment issue. The incident is resolved and it lasted 2 hours and 23 minutes.
OVHcloud·[SBG5/7][Compute - Instance] - Compute Instance Incident Notification
OVHcloud Compute Instance service did not work for some instances in the SBG5 and SBG7 regions. OVHcloud reports that the incident is resolved. The incident lasted from 17:55 UTC to 19:30 UTC.
OVHcloud·[RBX2][Dedicated Servers] - Rack 21D12 Incident Notification
We are pleased to inform you that the incident affecting our Dedicated Servers offering has been resolved. Start time : 31/10/2026 19:38 UTC End time : 31/10/2026 22:10 UTC Root Cause : This incident was caused by an electrical equipment issue. We apologize for any inconvenience caused and appreciate your understanding.
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.cc/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.cc/feed.xml?providers=ovhcloud/feed subscribe https://outages.cc/feed.xml?providers=ovhcloudFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane