[GLOBAL][Storage] - Block Storage Maintenance notification
As part of our continuous improvement plan, maintenance is scheduled on our Block Storage offer. Start time : 09/11/2026 07:00 UTC End time : 10/11/2026 14:00 UTC List of concerned regions: - BHS5 - DE1 - EU-SOUTH-MIL-A - EU-SOUTH-MIL-B - EU-SOUTH-MIL-C - EU-WEST-PAR-A - EU-WEST-PAR-B - EU-WEST-PAR-C - GRA1 - GRA3 - GRA5 - GRA7 - GRA9 - GRA11 - RBX-A - SBG5 - SGP1 - SYD1 - UK1 - US-EAST-VA - US-WEST-OR - WAW1 Service impact : During the maintenance window, customers may experience a temporary performance degradation. Service improvement : As part of our continuous improvement policy and to improve service quality, we will be doing a software upgrade on our Block Storage servers. Thank you for your understanding.
The latest update from OVHcloud.
State
Scheduled
Starts
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by OVHcloud
As part of our continuous improvement plan, maintenance is scheduled on our Block Storage offer. Start time : 09/11/2026 07:00 UTC End time : 10/11/2026 14:00 UTC List of concerned regions: - BHS5 - DE1 - EU-SOUTH-MIL-A - EU-SOUTH-MIL-B - EU-SOUTH-MIL-C - EU-WEST-PAR-A - EU-WEST-PAR-B - EU-WEST-PAR-C - GRA1 - GRA3 - GRA5 - GRA7 - GRA9 - GRA11 - RBX-A - SBG5 - SGP1 - SYD1 - UK1 - US-EAST-VA - US-WEST-OR - WAW1 Service impact : During the maintenance window, customers may experience a temporary performance degradation. Service improvement : As part of our continuous improvement policy and to improve service quality, we will be doing a software upgrade on our Block Storage servers. Thank you for your understanding.
Affected components
48OVHcloud in the last 90 days
Full historyIncidents in 90 days
238
Days with an incident
90
Median duration
1 h 40 min
This incident
Not comparable
Other OVHcloud incidents
All incidentsOVHcloud·[GRA][Storage and Backups] - NasHA incident notification
OVHcloud reports that the NAS HA service in the GRA region had a temporary availability problem in Cluster614. OVHcloud states that the incident is resolved and lasted from 06/11/2026 06:48 UTC to 06/11/2026 11:03 UTC. OVHcloud reports that a hardware issue caused the incident.
OVHcloud·[BHS6][Dedicated Servers] - Rack T06F27 incident notification
OVHcloud reports that the vRack network did not work in rack T06F27 in the BHS region. This affected Dedicated Servers. OVHcloud identified a network equipment issue. OVHcloud replaced the faulty equipment. The incident is resolved and lasted about 3 hours and 10 minutes.
OVHcloud·[RBX8][Dedicated Servers] - Rack R808L04 incident notification
The vRack network was unavailable in rack R808L04 in the RBX region. This affected Dedicated Servers network in RBX. A cooling system issue caused the incident. OVHcloud reports that the incident is resolved. The outage lasted 130 minutes.
OVHcloud·[GRA6][Virtual Private Servers] - VPS incident notification
OVHcloud reports that backup and image management for Virtual Private Servers did not work correctly in the GRA6 region. The incident is resolved. It started at 15:26 UTC and ended at 18:35 UTC on 05 November 2026.
OVHcloud·[GRA6][Storage] - Instance Backup incident notification
OVHcloud reports that Instance Backup and image management were unstable in the GRA6 region. Customers may have had failures when they created backups or managed images. OVHcloud states that the incident is resolved and lasted 1 hour and 39 minutes.
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.
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.
https://outages.live/feed.xml?providers=ovhcloud/feed subscribe https://outages.live/feed.xml?providers=ovhcloudFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane