[ERI1][Infrastructure] - Room E105 maintenance notification
As part of our continuous improvement plan, we will be carrying out a maintenance on our electrical infrastructure. List of concerned racks: -E105B01,02,03 -E105B04,05,06 -E105B07,08,09 -E105B10,11,12 Start time : 03/11/2026 06:00 UTC End time : 03/11/2026 15:00 UTC Service impact : Customers could still experience a temporary reboot or shutdown in the worst case of their servers. Service improvement : As part of our continuous improvement policy, we will be doing a maintenance on our electrical infrastructure. Thank you for your understanding.
The latest update from OVHcloud.
State
Scheduled
Starts
in 1 d
2026-11-03 06:00 UTC
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by OVHcloud
As part of our continuous improvement plan, we will be carrying out a maintenance on our electrical infrastructure. List of concerned racks: -E105B01,02,03 -E105B04,05,06 -E105B07,08,09 -E105B10,11,12 Start time : 03/11/2026 06:00 UTC End time : 03/11/2026 15:00 UTC Service impact : Customers could still experience a temporary reboot or shutdown in the worst case of their servers. Service improvement : As part of our continuous improvement policy, we will be doing a maintenance on our electrical infrastructure. Thank you for 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
Not comparable
Other OVHcloud incidents
All incidentsOVHcloud·[SBG5][Virtual Private Servers] - VPS Incident Notification
Some Virtual Private Servers in the SBG5 region are temporarily unreachable. OVHcloud has identified the incident. OVHcloud reports that a network equipment issue is the cause and that its 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
OVHcloud reports a partial outage. Some Compute Instance services in the SBG5 region do not work. Some instances in SBG5 are temporarily unreachable. OVHcloud has identified the incident and 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