Live

[GRA1][Dedicated Servers] - Servers relocation maintenance notification

MaintenanceOfficial update

As part of our continuous improvement plan, we will be carrying out maintenance on our infrastructure. Start time : 03/12/2026 21:00 UTC End time : 04/12/2026 05:00 UTC List of concerned racks : - Rack G127A24 - Rack G127A25 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 UTC

As posted by OVHcloud

Scheduled

As part of our continuous improvement plan, we will be carrying out maintenance on our infrastructure. Start time : 03/12/2026 21:00 UTC End time : 04/12/2026 05:00 UTC List of concerned racks : - Rack G127A24 - Rack G127A25 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

2
GRADedicated Servers || Global Infrastructure - GRA

OVHcloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

214

Days with an incident

90

Median duration

1 h 39 min

This incident

Not comparable

How long each incident lasted, on the day it started. The outlined bar is this incident.

26 days
median 1 h 39 min
90 days agoToday

Other OVHcloud incidents

All incidents

OVHcloud·[EU-WEST-OR1][Containers & Orchestration] - Managed Kubernetes Service incident notification

OVHcloud reports that the Managed Kubernetes Service control planes are unreachable in the EU-WEST-OR1 region. Customers cannot access or manage their Kubernetes clusters. Deployed workloads are not affected. OVHcloud is investigating the cause.

Partial outage

OVHcloud·[RBX6][Dedicated Servers] - Rack 46C06 incident notification

OVHcloud reports that some Dedicated Servers in rack 46C06 in the RBX region were unavailable. OVHcloud identified an electrical equipment issue as the cause. The incident is resolved, and it lasted 1 hour and 28 minutes.

Resolved

OVHcloud·[GRA][Containers & Orchestration] - Managed Private Registry incident notification

We would like to inform you that an incident affected our Managed Private Registry offering. This incident has since been resolved. Please find the details of this incident below : Start time : 17/11/2026 09:27 UTC End time : 17/11/2026 09:40 UTC Impacted Service(s) : Some Registries in the GRA region were temporarily unavailable. Customers Impact : Customers were temporarily unable to access their Registries located in the specified region. Root Cause : This incident was caused by a software issue. We thank you for your understanding and patience throughout this incident.

Resolved

OVHcloud·[EU][Dedicated Servers] - IP Failover/VMAC incident notification

OVHcloud reports delays to Additional IP move, virtual MAC creation, and server delivery operations on Dedicated Servers in the Europe zone, including CCH, ERI, GRA, IEB, LIM, MR9, RBX, SBG, and WAW. Network traffic was not impacted. The incident is resolved. It lasted about 3 hours and 33 minutes.

Resolved

OVHcloud·[US-CENTRAL-LZ-SLC][LocalZones] - Salt Lake City incident notification

OVHcloud reports that public network and resource management did not work in the US-CENTRAL-LZ-SLC-A Local Zone. OVHcloud states that the incident is resolved. The incident lasted about one hour.

Resolved

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.

Prompt
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.

RSS
https://outages.live/feed.xml?providers=ovhcloud
Slack
/feed subscribe https://outages.live/feed.xml?providers=ovhcloud

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane