[EU/CA][Web Hosting] - Clusters 100 to 151 maintenance notification
Scheduled maintenance is currently in progress. We will provide updates as necessary.
The latest update from OVHcloud.
State
In progress
Started
Ongoing for
1 h 50 min
Worst impact
Maintenance
Timeline
2 updatesScheduled
3 min 3%
In progress
1 h 46 min 97%
Updates
Times in UTCAs posted by OVHcloud
Scheduled maintenance is currently in progress. We will provide updates as necessary.
As part of our continuous improvement plan, maintenance is scheduled on our Web Hosting offer. Start time : 03/11/2026 08:45 UTC End time : 03/11/2026 16:00 UTC Service impact : During the maintenance window, customers may experience minor slowness on their websites and scheduled tasks. Service improvement : As part of our continuous improvement policy, we are deploying a kernel update on our infrastructure to strengthen security. Thank you for your understanding.
Affected components
48OVHcloud in the last 90 days
Full historyIncidents in 90 days
228
Days with an incident
90
Median duration
1 h 37 min
This incident
Not comparable
Other OVHcloud incidents
All incidentsOVHcloud·[DE1][Network] - Network API incident notification
The Network API for the public network and the private network (vRack) is unstable in the DE1 region. OVHcloud reports that network configuration tasks in DE1 can give API errors. OVHcloud is investigating the cause.
OVHcloud·[EU-WEST-PAR][Storage] - Object Storage incident notification
OVHcloud Object Storage does not work at full speed in the EU-WEST-PAR region. The incident affects EU-WEST-PAR-A, EU-WEST-PAR-B, and EU-WEST-PAR-C. OVHcloud reports that the problem causes temporary latency and that its teams are investigating.
OVHcloud·[Global][AI & Machine Learning] - AI Notebooks, AI Training, AI Deploy incident notification
We would like to inform you that an incident affected our AI & Machine Learning offering. This incident has since been resolved. Please find the details of this incident below : Start time : 31/10/2026 07:08 UTC End time : 31/10/2026 07:58 UTC Impacted Service(s) : AI Notebooks, AI Training and AI Deploy services were temporarily unavailable. Customers Impact : Customers were temporarily unable to create, manage or access their notebooks, training jobs and AI applications. Root Cause : This incident was caused by a software issue. We thank you for your understanding and patience throughout this incident.
OVHcloud·[BHS5][Dedicated Servers] - Racks T05B28, T05B29 incident notification
OVHcloud reports that some Dedicated Servers in racks T05B28 and T05B29 in BHS5 were temporarily unavailable. OVHcloud states that the incident is resolved. It lasted about 60 minutes.
OVHcloud·[RBX8][Dedicated Servers] - Rack R809R19 Incident Notification
OVHcloud reports that Dedicated Servers in Rack R809R19 in the RBX region were temporarily unavailable. OVHcloud reports that the incident is resolved. The incident lasted from 03:33 UTC to 04:49 UTC. OVHcloud states the cause was an electrical equipment issue.
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.cc/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.cc/feed.xml?providers=ovhcloud/feed subscribe https://outages.cc/feed.xml?providers=ovhcloudFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane