[Global][Backup as a Service] - Veeam Backup Managed maintenance notification
As part of our continuous improvement plan, maintenance is scheduled on our Veeam Backup Managed offer. Start time : 17/12/2026 08:00 UTC End time : 17/12/2026 18:00 UTC Service impact : During the maintenance, the storage servers hosting your backup data will be updated. Your backup data will be temporarily unavailable during the update of each storage server, for approximately 50 minutes. Backup and restore jobs may be impacted during this period. Service improvement : As part of our continuous improvement policy, we are updating the storage servers hosting your backup data. This brings improvements to certain mechanisms, as well as some performance enhancements. 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 Veeam Backup Managed offer. Start time : 17/12/2026 08:00 UTC End time : 17/12/2026 18:00 UTC Service impact : During the maintenance, the storage servers hosting your backup data will be updated. Your backup data will be temporarily unavailable during the update of each storage server, for approximately 50 minutes. Backup and restore jobs may be impacted during this period. Service improvement : As part of our continuous improvement policy, we are updating the storage servers hosting your backup data. This brings improvements to certain mechanisms, as well as some performance enhancements. Thank you for your understanding.
Affected components
1OVHcloud in the last 90 days
Full historyIncidents in 90 days
196
Days with an incident
90
Median duration
1 h 40 min
This incident
Not comparable
Other OVHcloud incidents
All incidentsOVHcloud·[GRA1][Dedicated Servers] - Rack G125A23 incident notification
We are currently experiencing an incident affecting our Dedicated Servers offering in the rack G125A23. The root cause has been identified. Please find the details of this incident below : Start time : 18/11/2026 13:40 UTC Impacted Service(s) : Some servers in the rack G125A23 are temporarily unavailable. Customers Impact : Customers are temporarily unable to access their servers located on the specified rack. Root Cause : This incident is caused by a cooling system issue. 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.
OVHcloud·[SBG5][Dedicated Servers] - Rack SBG0506B04C Incident Notification
The vRack Private Network does not work for Dedicated Servers in rack SBG0506B04C in the SBG region. OVHcloud identified the incident and states that a network equipment issue causes it. OVHcloud teams work to restore service.
OVHcloud·[RBX][Public VMware Cloud Foundation] - Public VCFaaS Incident Notification
Public VMware Cloud Foundation as-a-Service has degraded network, management plane, compute and storage in the RBX region. Some customers can have high latency and packet loss on the vRack network. OVHcloud reports that the incident is under investigation.
OVHcloud·[RBX3][Dedicated Servers] - Rack 46G20 Incident Notification
Some Dedicated Servers in Rack 46G20 in the RBX region are temporarily unavailable. OVHcloud reported an electrical equipment issue and resolved the incident. The outage lasted 37 minutes, from 10:00 to 10:37 UTC.
OVHcloud·[US][Backbone] - Backbone Incident Notification
The OVHcloud Backbone infrastructure in the US region has packet loss and increased latency. OVHcloud reports the status as investigating. OVHcloud gives no cause, workaround, or resolution time.
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