outages.live
Live
OVHcloudMaintenance ·

[RBX8][Cooling System] - Rack R806R02 maintenance notification

ResolvedOfficial update

Scheduled maintenance is currently in progress. We will provide updates as necessary.

The latest update from OVHcloud.

State

Resolved

Started

Lasted

9 min

Worst impact

Maintenance

Timeline

3 updates
13:1213:1413:1613:1913:21
MaintenanceUpdate postedTimes in UTC

Scheduled

3 min 36%

In progress

6 min 64%

Updates

Times in UTC

As posted by OVHcloud

Resolved
In progress

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Scheduled

As part of our continuous improvement plan, we will be carrying out maintenance on our cooling infrastructure. Start time : 03/11/2026 13:10 UTC End time : 03/11/2026 16:00 UTC Service impact : During this maintenance, the cooling system's efficiency may be temporarily reduced for some servers, potentially lowering performance. Despite ongoing mitigation efforts, customers could still experience a temporary reboot or shutdown in the worst case. Service improvement : As part of our continuous improvement policy, we will be performing maintenance on our cooling infrastructure. Thank you for your understanding.

Affected components

1
RBX8

OVHcloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

227

Days with an incident

90

Median duration

1 h 37 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 37 min
90 days agoToday

Other OVHcloud incidents

All incidents

OVHcloud·[GRA11][Network] - Network API incident notification

The Network API for the public network and the private network (vRack) is unstable in the GRA11 region. Customers can get API errors when they create, change, or manage network configurations in GRA11. OVHcloud reports that the incident is under investigation.

Degraded

OVHcloud·[Global][Dedicated Servers] - Delivery incident notification

OVHcloud Dedicated Servers delivery was degraded. The processing of suspension and reactivation requests was delayed in Zone Europe, Zone APAC, and Zone Canada. OVHcloud reports that the incident is resolved. It lasted about 7 hours and 25 minutes.

Resolved

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.

Resolved

OVHcloud·[DE1][Network] - Network API incident notification

The Network API for the public network and the private network (vRack) did not work in the DE1 region. The Managed Kubernetes Service in DE1 was also affected. OVHcloud reports that the incident is resolved. It lasted about 4 hours and 43 minutes.

Resolved

OVHcloud·[EU-WEST-PAR][Storage] - Object Storage incident notification

OVHcloud Object Storage S3 in the EU-WEST-PAR region had increased response times. The service was fully restored at 09:53 UTC on 03/11/2026, and OVHcloud keeps monitoring in place.

Degraded

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