[EU/CA/US][Control panel & API] - Control Panel incident notification
OVHcloud reports that the Control Panel was unavailable in the CA, EU, and US regions. Customers had errors when they accessed the Control Panel to order or manage services. Existing services were not affected. The incident is resolved and lasted 29 minutes.
State
Resolved
Started
Lasted
5 min
Worst impact
Partial outage
Timeline
2 updatesIdentified
5 min 100%
Updates
Times in UTCAs posted by OVHcloud
We would like to inform you that the incident affecting our Control Panel offering has now been resolved. Please find the details of this incident below : Start time : 06/11/2026 17:36 UTC End time : 06/11/2026 18:05 UTC Impacted Service(s) : The Control Panel was temporarily facing perturbations. Customers Impact : Customers may have experienced errors when accessing the Control Panel to order or manage their services. Existing services remained unaffected. Root Cause : This incident was caused by a software issue. We thank you for your understanding and patience throughout this incident.
We are currently experiencing an incident affecting our Control Panel offering. The root cause has been identified. Please find the details of this incident below : Start time : 06/11/2026 17:36 UTC Impacted Service(s) : The Control Panel is temporarily facing perturbations. Customers Impact : Customers may experience errors when accessing the Control Panel to order or manage their services. Existing services remain unaffected. In the meantime, customers can use the Beta version which does not have the same issue. Root Cause : This incident is caused by a software 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.
Affected components
6OVHcloud in the last 90 days
Full historyIncidents in 90 days
239
Days with an incident
90
Median duration
1 h 40 min
This incident
95% shorter than the median
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