[SGP2][Dedicated Servers] - Rack SGP0201D03C servers relocation maintenance notification
As part of our continuous improvement plan, we will be carrying out maintenance on our infrastructure. Start time : 02/12/2026 06:00 UTC End time : 02/12/2026 10:00 UTC Service impact : During the maintenance window, the concerned servers will be gracefully shut down beforehand, then physically relocated before being restarted. Services hosted on these servers will be unavailable for the duration of the operation, then restored once the maintenance is complete. Service improvement : As part of our continuous improvement policy, we are optimizing our infrastructure by relocating servers to new facilities. 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, we will be carrying out maintenance on our infrastructure. Start time : 02/12/2026 06:00 UTC End time : 02/12/2026 10:00 UTC Service impact : During the maintenance window, the concerned servers will be gracefully shut down beforehand, then physically relocated before being restarted. Services hosted on these servers will be unavailable for the duration of the operation, then restored once the maintenance is complete. Service improvement : As part of our continuous improvement policy, we are optimizing our infrastructure by relocating servers to new facilities. Thank you for your understanding.
Affected components
2OVHcloud in the last 90 days
Full historyIncidents in 90 days
235
Days with an incident
90
Median duration
1 h 37 min
This incident
Not comparable
Other OVHcloud incidents
All incidentsOVHcloud·[US/SYD][Infrastructure] - Backbone incident notification
We would like to inform you that an incident affected our Infrastructure offering. This incident has since been resolved. Please find the details of this incident below : Start time : 04/11/2026 13:37 UTC End time : 04/11/2026 14:00 UTC Impacted Service(s) : Increased latency was observed on the link between US and SYD. Customers Impact : Customers may have experienced increased latency when accessing their services passing from US and SYD. Root Cause : This incident was caused by our provider. We thank you for your understanding and patience throughout this incident.
OVHcloud·[DE1][Network] - Load Balancer incident notification
OVHcloud reports that Load Balancer creation and modification did not work in the DE1 region. The Network API in DE1 was unstable. OVHcloud reports that the incident is resolved. It lasted about 11 hours.
OVHcloud·[GRA][Web Hosting] - Some Filerz incident notification
OVHcloud reports that some websites on some Filerz storage clusters were temporarily unavailable in the GRA region. The incident affected 20 clusters. OVHcloud resolved the incident. It lasted about 45 minutes.
OVHcloud·[GLOBAL][Dedicated Servers] - Administrative network task incident notification
OVHcloud reported that administrative changes to public and private network settings did not work on Dedicated Servers in BHS, CCH, ERI and other listed regions. The affected servers were RISE and SCALE servers delivered after 03/11/2026 at 09:00 UTC. OVHcloud resolved the incident at 21:18 UTC on 03/11/2026, about 13 hours after the start at 08:00 UTC.
OVHcloud·[DE1][Network] - Load balancer incident notification
The load balancer delivery service in the DE1 region did not work. OVHcloud reports that the incident is resolved. The incident lasted from 17:00 UTC to 19:13 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.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