[RBX8][Infrastructure] - Rack R824A08 maintenance notification
As part of our continuous improvement plan, we will be carrying out a maintenance on our electrical infrastructure. Start time : 10/11/2026 05:00 UTC End time : 10/11/2026 16:00 UTC Service impact : During the maintenance window, the servers in the specified rack will be gracefully shut down to allow the maintenance activities to be performed safely. As a result, the services hosted on these servers will be unavailable before being restored once the maintenance is complete. 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 7 d
2026-11-10 05: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. Start time : 10/11/2026 05:00 UTC End time : 10/11/2026 16:00 UTC Service impact : During the maintenance window, the servers in the specified rack will be gracefully shut down to allow the maintenance activities to be performed safely. As a result, the services hosted on these servers will be unavailable before being restored once the maintenance is complete. 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
223
Days with an incident
90
Median duration
1 h 37 min
This incident
Not comparable
Other OVHcloud incidents
All incidentsOVHcloud·[DE1][Network] - Public network incident notification
OVHcloud reports that public network management operations were unstable in the DE1 region. Customers had errors or delays when they created or changed the network configuration of their instances. OVHcloud resolved the incident, which lasted from 09:22 UTC to 18:32 UTC.
OVHcloud·[Global][Domains] - .TOP Domains Name incident notification
The .TOP domain operations do not work. Registration, Renew, Transfer, Restore, and Delete are affected. OVHcloud reports that it identified the cause. The cause is from a provider. OVHcloud works with the provider to restore service.
OVHcloud·[SBG5][Dedicated Servers] - Rack SBG0505B05B incident notification
OVHcloud reports that some Dedicated Servers in rack SBG0505B05B in the SBG region were temporarily unavailable. OVHcloud identified the cause and resolved the incident. The incident lasted from 09:50 UTC to 12:42 UTC on 02/11/2026.
OVHcloud·[Global][Domains] - .MG Domains Name incident notification
The .MG domain service does not work for Registration, Renew, Transfer, Restore, and Delete operations. OVHcloud has identified the incident. The cause comes from a provider, and OVHcloud teams work to restore the service.
OVHcloud·[Global][Domains] - .CO Domains Name incident notification
The .CO domain registration, renew, transfer, restore, and delete operations do not work for OVHcloud customers. OVHcloud identified the cause as its provider and works with that provider to restore service.
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