[ERI1][Infrastructure] - Rows ERI0111E and ERI0111F maintenance notification
Scheduled maintenance is currently in progress. We will provide updates as necessary.
The latest update from OVHcloud.
State
In progress
Started
Ongoing for
3 h 50 min
Worst impact
Maintenance
Timeline
3 updatesScheduled
1 min 0%
In progress
3 h 50 min 100%
Updates
Times in UTCAs posted by OVHcloud
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Maintenance will begin as scheduled in 60 minutes.
As part of our continuous improvement plan, we will be carrying out maintenance on our electrical infrastructure. Start time : 17/11/2026 07:00 UTC End time : 17/11/2026 12:00 UTC List of concerned racks : - Racks located in row ERI0111E - Racks located in row ERI0111F Service impact : During this maintenance, the concerned racks will temporarily operate without electrical redundancy. In the worst case, customers could experience a temporary reboot or shutdown of their servers. IPMI management may also be temporarily unavailable for up to 5 minutes. Service improvement : As part of our continuous improvement policy, we will be performing maintenance on our electrical infrastructure. Thank you for your understanding.
Affected components
1OVHcloud in the last 90 days
Full historyIncidents in 90 days
232
Days with an incident
90
Median duration
1 h 40 min
This incident
Not comparable
Other OVHcloud incidents
All incidentsOVHcloud·[RBX8][Dedicated Servers] - Rack R831A07 incident notification
OVHcloud reports that all servers in rack R831A07 in the RBX region are temporarily unavailable. This affects the Dedicated Servers offering. OVHcloud identified an electrical equipment issue as the cause. A significant number of servers in that rack are now operational.
OVHcloud·[ERI1C][Backup as a Service] - Rack ERI0111E01A - Veeam Backup Managed incident notification
OVHcloud reports that some Veeam Backup Managed storage servers were temporarily unavailable in the ERI1 region. Some customers could not run or restore their VM backups. OVHcloud reports that the incident is resolved and that it lasted about 89 minutes.
OVHcloud·[RBX3][Dedicated Servers] - Rack 41A09 incident notification
An incident affected Dedicated Servers in rack 41A09 in the RBX region. Some servers became temporarily unavailable. OVHcloud reports that the incident is resolved. It lasted from 16/11/2026 18:47 UTC to 17/11/2026 00:30 UTC. OVHcloud identified an electrical equipment issue as the cause.
OVHcloud·[RBX6][Dedicated Servers] - Rack 46N07 incident notification
OVHcloud reports that some Dedicated Servers in rack 46N07 in the RBX region were temporarily unavailable. The cause was an electrical equipment issue. The incident is resolved. It lasted from 16/11/2026 17:35 UTC to 16/11/2026 23:00 UTC.
OVHcloud·[BHS/US][Infrastructure] - Backbone incident notification
OVHcloud reports packet loss and increased latency on its backbone infrastructure in the BHS and US regions. OVHcloud restored service at 02:51 UTC on 17 November 2026 and now monitors for stability. The incident started at 16:20 UTC on 16 November 2026.
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