Live

[SBG3][Cooling System] - Rack S350B09

MaintenanceOfficial update

As part of our continuous improvement plan, we will be carrying out a maintenance on our cooling infrastructure. Start time: 30/11/2026 07:00 UTC End time: 30/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 doing a maintenance on our cooling 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 cooling infrastructure. Start time: 30/11/2026 07:00 UTC End time: 30/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 doing a maintenance on our cooling infrastructure. Thank you for your understanding.

Affected components

1
Infrastructure || SBG

OVHcloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

230

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·[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

OVHcloud·[RBX][Public Cloud] - Compute Instance incident notification

OVHcloud reports that some Compute Instances in the RBX region are unavailable. The affected components are RBX-A and Compute - Instance RBX - RBX-A. OVHcloud is investigating the incident.

Partial outage

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

OVHcloud Dedicated Servers in rack R831A07 in the RBX region did not work. Some servers were unavailable from 17/11/2026 08:18 UTC to 17/11/2026 10:23 UTC. OVHcloud reports that the incident is resolved and the cause was an electrical equipment issue.

Resolved

OVHcloud·[ERI1C][Backup as a Service] - Rack ERI0111E01A - Veeam Backup Managed incident notification

OVHcloud reports that some Veeam Backup Managed storage servers were temporarily unavailable in the ERI1 region. Some customers could not run or restore their VM backups. OVHcloud reports that the incident is resolved and that it lasted about 89 minutes.

Resolved

OVHcloud·[RBX3][Dedicated Servers] - Rack 41A09 incident notification

An incident affected Dedicated Servers in rack 41A09 in the RBX region. Some servers became temporarily unavailable. OVHcloud reports that the incident is resolved. It lasted from 16/11/2026 18:47 UTC to 17/11/2026 00:30 UTC. OVHcloud identified an electrical equipment issue as the cause.

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