[SGP2][Infrastructure] - Rack SGP0202B02B Electrical background work
As part of our continuous improvement plan, a maintenance is scheduled on our electrical infrastructure. Start time : 10/11/2026 02:30 UTC End time : 10/11/2026 10:30 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 8 d
2026-11-10 02:30 UTC
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by OVHcloud
As part of our continuous improvement plan, a maintenance is scheduled on our electrical infrastructure. Start time : 10/11/2026 02:30 UTC End time : 10/11/2026 10:30 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
218
Days with an incident
90
Median duration
1 h 35 min
This incident
Not comparable
Other OVHcloud incidents
All incidentsOVHcloud·[Global][Domains] - .TOP Domains Name incident notification
The .TOP domain operations do not work. Registration, Renew, Transfer, Restore, and Delete are affected in all regions. OVHcloud reports the state as identified. The cause comes from a provider.
OVHcloud·[SBG5][Dedicated Servers] - Rack SBG0505B05B incident notification
Some Dedicated Servers in rack SBG0505B05B in the SBG region do not work. OVHcloud reports that it identified the cause and that teams are working to restore service. The incident started at 09:50 UTC on 02/11/2026.
OVHcloud·[Global][Domains] - .MG Domains Name incident notification
OVHcloud reports that Registration, Renew, Transfer, Restore, and Delete do not work for .MG domains. OVHcloud identified the cause and states that the cause comes from its provider. OVHcloud teams are working to restore service.
OVHcloud·[Global][Domains] - .CO Domains Name incident notification
OVHcloud reports that multiple .CO domain operations do not work. Registration, Renew, Transfer, Restore, and Delete for .CO domains are affected. OVHcloud identified the cause and works with its provider to restore service.
OVHcloud·[ERI1][Dedicated Servers] - Rack E105A01 incident notification
OVHcloud reports that Dedicated Servers in rack E105A01 in the ERI region were unavailable. The incident is resolved. It lasted 5 minutes, from 07:38 to 07:43 UTC.
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