[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: - E105C01,02,03 - E105C04,05,06 - E105C07,08,09 - E105C10,11,12 Start time : 04/11/2026 06:00 UTC End time : 04/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 2 d
2026-11-04 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: - E105C01,02,03 - E105C04,05,06 - E105C07,08,09 - E105C10,11,12 Start time : 04/11/2026 06:00 UTC End time : 04/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
217
Days with an incident
90
Median duration
1 h 35 min
This incident
Not comparable
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