Live

[GRA3][Infrastructure] - Rack GRA0313A05B maintenance notification

MaintenanceOfficial update

As part of our continuous improvement plan, we will be carrying out a maintenance on our electrical infrastructure. Start time : 18/11/2026 07:00 UTC End time : 18/11/2026 15:30 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

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 a maintenance on our electrical infrastructure. Start time : 18/11/2026 07:00 UTC End time : 18/11/2026 15:30 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

2
GRA3Infrastructure || GRA - GRA3

OVHcloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

250

Days with an incident

90

Median duration

1 h 41 min

This incident

Not comparable

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

41 days
median 1 h 41 min
90 days agoToday

Other OVHcloud incidents

All incidents

OVHcloud·[RBX7][Dedicated Servers] - Rack R715B08 incident notification

OVHcloud reports a partial outage on Dedicated Servers in rack R715B08 in the RBX region. The public network in that rack is unavailable. OVHcloud identified the cause as a network equipment issue and states that teams are working to restore service.

Partial outage

OVHcloud·[US][Infrastructure] - Backbone incident notification

OVHcloud reports a backbone incident in the US region. The US backbone has increased latency. OVHcloud identified the cause as a network equipment issue. The situation is mitigated, but latency can stay higher than usual while the network stabilizes.

Degraded

OVHcloud·[SGP1][Dedicated Servers] - Rack 040816B incident notification

The public network does not work for OVHcloud Dedicated Servers in rack 040816B in the SGP region. OVHcloud reports that this incident is resolved. The outage lasted 15 minutes, from 06:54 UTC to 07:09 UTC. A network equipment issue caused the incident.

Resolved

OVHcloud·[RBX8][Dedicated Servers] - Rack R809R07 incident notification

OVHcloud reports that some Dedicated Servers in rack R809R07 in the RBX region did not work. OVHcloud identified an electrical equipment issue. OVHcloud resolved the incident, which lasted 3 hours and 7 minutes.

Resolved

OVHcloud·[BHS1][Dedicated Servers] - Rack T01C28 incident notification

The public network does not work for Dedicated Servers in rack T01C28 in the BHS region. OVHcloud reports that this incident is resolved. It lasted from 02:28 UTC to 06:12 UTC.

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