[RBX6][Dedicated Servers] - Racks R622A10/R622A11 incident notification
We would like to inform you that the incident affecting our Dedicated Servers offering has now been resolved. Please find the details of this incident below : Start time : 28/10/2026 14:55 UTC End time : 28/10/2026 22:13 UTC Impacted Service(s) : Some servers in the racks R622A10 and R622A11 were temporarily unavailable. Customers Impact : Some customers were temporarily unable to access their servers located on the specified racks. Root Cause : This incident was caused by this maintenance : https://network.status-ovhcloud.com/incidents/ddsymc3z1npl We thank you for your understanding and patience throughout this incident.
The latest update from OVHcloud.
State
Resolved
Started
4 d ago
2026-10-28 16:41 UTC
Lasted
5 h 34 min
until 2026-10-28 22:15 UTC
Worst impact
Partial outage
Timeline
3 updatesIdentified
5 h 34 min 100%
Updates
Times in UTCAs posted by OVHcloud
We would like to inform you that the incident affecting our Dedicated Servers offering has now been resolved. Please find the details of this incident below : Start time : 28/10/2026 14:55 UTC End time : 28/10/2026 22:13 UTC Impacted Service(s) : Some servers in the racks R622A10 and R622A11 were temporarily unavailable. Customers Impact : Some customers were temporarily unable to access their servers located on the specified racks. Root Cause : This incident was caused by this maintenance : https://network.status-ovhcloud.com/incidents/ddsymc3z1npl We thank you for your understanding and patience throughout this incident.
Please find an update of this incident below : Update : Our teams are still working on the restoration of the servers located in the racks R622A10 and R622A11. 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 are currently experiencing an incident affecting our Dedicated Servers offering in the racks R622A10 and R622A11. The root cause has been identified. Please find the details of this incident below : Start time : 28/10/2026 14:55 UTC Impacted Service(s) : Some servers in the racks R622A10 and R622A11 are temporarily unavailable. Customers Impact : Some customers are temporarily unable to access their servers located on the specified racks. Root Cause : This incident is caused by this maintenance : https://network.status-ovhcloud.com/incidents/ddsymc3z1npl 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.
Affected components
2OVHcloud in the last 90 days
Full historyIncidents in 90 days
216
Days with an incident
90
Median duration
1 h 35 min
This incident
3.5× the median
Other OVHcloud incidents
All incidentsOVHcloud·[SBG6/8][Virtual Private Servers] - VPS Incident Notification
Some Virtual Private Servers in the SBG5, SBG6 and SBG8 regions are temporarily unreachable. OVHcloud states that the incident is identified and that a network equipment issue causes it. OVHcloud teams work to restore service.
OVHcloud·[RBX3][Dedicated Servers] - Rack 46E19 Incident Notification
Servers in Rack 46E19 in the RBX region are not accessible through the IPMI interface. The Dedicated Servers network in RBX is affected. OVHcloud reports that the incident is identified. The cause is a network equipment issue, and teams work to restore service.
OVHcloud·[SBG5][Compute - Instance] - Compute Instance Incident Notification
Some Compute Instance services in the SBG5 and SBG7 regions do not work. Some instances in these regions are temporarily unreachable. OVHcloud reports that it identified the incident and that teams work to restore service.
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.
OVHcloud·[ERI1][Network] - Rack ERI0102C03B Incident Notification
We had an incident on our Dedicated Servers offer which has now been resolved. Here are some supplementary details : Start time : 31/10/2026 14:36 UTC End time : 31/10/2026 14:57 UTC Impacted Service(s) : Public Network in Rack ERI0102C03B was temporarily unavailable. Customers Impact : Customers were temporarily unable to access their servers via Public Network in the specified rack. Root Cause : This incident was caused by a network equipment issue. We thank you for your understanding and patience throughout this incident.
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