[SGP2][Infrastructure] - Rack SGP0202A03B Electrical background work
As part of our continuous improvement plan, a maintenance is scheduled on our electrical infrastructure. Start time : 11/11/2026 02:30 UTC End time : 11/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
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 : 11/11/2026 02:30 UTC End time : 11/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
230
Days with an incident
90
Median duration
1 h 37 min
This incident
Not comparable
Other OVHcloud incidents
All incidentsOVHcloud·[Global][Dedicated Servers] - Delivery incident notification
OVHcloud reports delays to suspension and reactivation request processing for Dedicated Servers in the Europe, APAC, and Canada zones. OVHcloud says the incident is resolved. It lasted about 7 hours and 25 minutes.
OVHcloud·[RBX][Storage and Backups] - NAS HA Cluster11003 incident notification
We would like to inform you that an incident affected our NAS HA offering on the Cluster11003 in the RBX region. This incident has since been resolved. Please find the details of this incident below : Start time : 03/11/2026 10:10 UTC End time : 03/11/2026 10:24 UTC Impacted Service(s) : Some NAS HA services on the Cluster11003 were temporarily unavailable. Customers Impact : Customers were temporarily unable to access their data located on the Cluster11003. Root Cause : This incident was caused by a hardware issue. We thank you for your understanding and patience throughout this incident.
OVHcloud·[DE1][Network] - Network API incident notification
OVHcloud reports that the Network API for the public network and the private network (vRack) in the DE1 region does not work correctly. The Managed Kubernetes Service in DE1 is also affected. OVHcloud reports that the incident is resolved, and it lasted 4 hours and 43 minutes.
OVHcloud·[EU-WEST-PAR][Storage] - Object Storage incident notification
OVHcloud Object Storage S3 has slow uploads and retrievals in the EU-WEST-PAR region. The affected components are EU-WEST-PAR-A, EU-WEST-PAR-B, and EU-WEST-PAR-C. OVHcloud reports that the service was fully restored as of 03/11/2026 09:53 UTC, and monitoring continues.
OVHcloud·[Global][AI & Machine Learning] - AI Notebooks, AI Training, AI Deploy incident notification
We would like to inform you that an incident affected our AI & Machine Learning offering. This incident has since been resolved. Please find the details of this incident below : Start time : 31/10/2026 07:08 UTC End time : 31/10/2026 07:58 UTC Impacted Service(s) : AI Notebooks, AI Training and AI Deploy services were temporarily unavailable. Customers Impact : Customers were temporarily unable to create, manage or access their notebooks, training jobs and AI applications. Root Cause : This incident was caused by a software 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