Live

[SBG5][Cooling System] - Rack SBG0505B05B maintenance notification

MaintenanceOfficial update

Please find an update of this maintenance below : Update : This maintenance is currently causing an incident affecting our Dedicated Servers offering in the rack SBG0505B05B. You can follow its progress here : https://bare-metal-servers.status-ovhcloud.com/incidents/2ss88n4z3pqb Ongoing Actions : Our teams are actively working to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

The latest update from OVHcloud.

State

In progress

Started

2 h ago

2026-11-02 09:00 UTC

Ongoing for

1 h 49 min

Worst impact

Maintenance

Timeline

3 updates
09:0009:2709:5410:2110:48
MaintenanceUpdate postedTimes in UTC

Scheduled

3 min 3%

In progress

1 h 45 min 97%

Updates

Times in UTC

As posted by OVHcloud

In progress2026-11-02 10:06 UTC

Please find an update of this maintenance below : Update : This maintenance is currently causing an incident affecting our Dedicated Servers offering in the rack SBG0505B05B. You can follow its progress here : https://bare-metal-servers.status-ovhcloud.com/incidents/2ss88n4z3pqb Ongoing Actions : Our teams are actively working to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

In progress2026-11-02 09:03 UTC

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

Scheduled2026-11-02 08:54 UTC

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

2
SBG5Infrastructure || SBG - SBG5

OVHcloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

218

Days with an incident

90

Median duration

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

Other OVHcloud incidents

All incidents

OVHcloud·[Global][Domains] - .TOP Domains Name incident notification

The .TOP domain operations do not work. Registration, Renew, Transfer, Restore, and Delete are affected in all regions. OVHcloud reports the state as identified. The cause comes from a provider.

Partial outageupdated 10 min ago

OVHcloud·[SBG5][Dedicated Servers] - Rack SBG0505B05B incident notification

Some Dedicated Servers in rack SBG0505B05B in the SBG region do not work. OVHcloud reports that it identified the cause and that teams are working to restore service. The incident started at 09:50 UTC on 02/11/2026.

Partial outageupdated 48 min ago

OVHcloud·[Global][Domains] - .MG Domains Name incident notification

OVHcloud reports that Registration, Renew, Transfer, Restore, and Delete do not work for .MG domains. OVHcloud identified the cause and states that the cause comes from its provider. OVHcloud teams are working to restore service.

Partial outageupdated 2 h ago

OVHcloud·[Global][Domains] - .CO Domains Name incident notification

OVHcloud reports that multiple .CO domain operations do not work. Registration, Renew, Transfer, Restore, and Delete for .CO domains are affected. OVHcloud identified the cause and works with its provider to restore service.

Partial outageupdated 2 h ago

OVHcloud·[ERI1][Dedicated Servers] - Rack E105A01 incident notification

OVHcloud reports that Dedicated Servers in rack E105A01 in the ERI region were unavailable. The incident is resolved. It lasted 5 minutes, from 07:38 to 07:43 UTC.

Resolvedresolved 3 h ago

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