Live

[SBG5][Cooling System] - Rack SBG0506B02C

MaintenanceOfficial update

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

180

Days with an incident

90

Median duration

1 h 45 min

This incident

Not comparable

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

7 days
median 1 h 45 min
90 days agoToday

Other OVHcloud incidents

All incidents

OVHcloud·[RBX5][Dedicated Servers] - Rack 45D18 incident notification

The vRack network is unavailable for Dedicated Servers in rack 45D18 in the RBX region. OVHcloud reports that the incident is identified and that a network equipment issue is the cause. OVHcloud teams work to restore service.

Partial outage

OVHcloud·[EU/US/APAC][Infrastructure] - Backbone incident notification

OVHcloud reports packet loss on some backbone links between Europe and APAC, and between North America and APAC. The incident is resolved. OVHcloud gives the start time as 08:15 UTC and the end time as 09:15 UTC on 20/11/2026.

Resolved

OVHcloud·[GLOBAL][AI & Machine Learning] - AI Endpoint Incident Notification

The AI Endpoint component of OVHcloud AI & Machine Learning has a partial outage. OVHcloud reports that the service was fully restored at 07:12 UTC on 20/11/2026 and that monitoring is in place. The incident started at 06:25 UTC.

Partial outage

OVHcloud·[Global][Identity, Security & Operations] - Logs Data Platform incident notification

We would like to inform you that the incident affecting our Identity, Security & Operations offering has now been resolved. Please find the details of this incident below : Start time : 19/11/2026 17:31 UTC End time : 19/11/2026 20:50 UTC Impacted Service(s) : The OpenSearch API of the Logs Data Platform service was temporarily unavailable. Customers Impact : Customers were temporarily unable to query or access their logs through the OpenSearch API. Log ingestion remained unaffected. Root Cause : This incident was caused by a network equipment issue. We thank you for your understanding and patience throughout this incident.

Resolved

OVHcloud·[US-WEST-OR][Storage] - Cloud Archive incident notification

The Cloud Archive service in the US-WEST-OR region has an increased error rate. Storing or retrieving archived data may fail. OVHcloud reports the root cause as identified.

Partial outage

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