Live

[SBG][Storage] - File storage maintenance notification

MaintenanceOfficial update

As part of our continuous improvement plan, a maintenance is scheduled on our file storage infrastructure. Start time : 24/11/2026 21:15 UTC End time : 25/11/2026 05:00 UTC Service impact : None. Service improvement : As part of our continuous improvement policy, we will be performing maintenance on our file storage 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, a maintenance is scheduled on our file storage infrastructure. Start time : 24/11/2026 21:15 UTC End time : 25/11/2026 05:00 UTC Service impact : None. Service improvement : As part of our continuous improvement policy, we will be performing maintenance on our file storage infrastructure. Thank you for your understanding.

Affected components

4
SBG5SBG7Storage || File storage - SBG5Storage || File storage - SBG7

OVHcloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

173

Days with an incident

90

Median duration

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

Other OVHcloud incidents

All incidents

OVHcloud·[RBX2][Dedicated Servers] - Rack 22A04 Incident Notification

Dedicated Servers in Rack 22A04 in the RBX region are unavailable. The provider OVHcloud reports a network equipment issue. OVHcloud states that the incident is resolved and that it lasted about 110 minutes.

Resolved

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

We would like to inform you that an incident affected our Public Cloud offering in the RBX-A region. This incident has since been resolved. Please find the details of this incident below : Start time : 21/11/2026 06:19 UTC End time : 21/11/2026 06:46 UTC Impacted Service(s) : Some instances in the RBX-A region were temporarily unavailable. Customers Impact : Customers were temporarily unable to access their instances located in the specified region. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We thank you for your understanding and patience throughout this incident.

Resolved

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

Dedicated Servers in rack R715B19 in RBX7 had a temporary availability problem, and some servers were unavailable. OVHcloud reports that the incident is resolved. The outage lasted about 58 minutes, from 22:25 to 23:23 UTC, and OVHcloud states that a cooling system issue caused it.

Resolved

OVHcloud·[US-WEST-LZ-LAX][LocalZones] - VPS Incident Notification

We had an incident on our Virtual Private Servers offer which has now been resolved. Here are some supplementary details : Start time : 20/11/2026 15:59 UTC End time : 20/11/2026 18:53 UTC Impacted Service(s) : Some VPS in the Los Angeles Local Zone experienced partial connectivity issues. Customers Impact : Customers may have experienced connectivity issues when accessing their VPS located in the specified Local Zone. Root Cause : A service disruption occurred due to an unexpected infrastructure malfunction. We thank you for your understanding and patience throughout this incident.

Resolved

OVHcloud·[RBX3][Dedicated Servers] - Rack 46N07 Incident Notification

Some Dedicated Servers in Rack 46N07 in the RBX region do not work. OVHcloud reports that the incident is resolved. The incident lasted 41 minutes, from 17:32 UTC to 18:13 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