outages.live
Live
OVHcloudIncident ·

[GLOBAL][Dedicated Servers] - Administrative network task incident notification

DegradedOfficial update
0

OVHcloud reports a problem with administrative changes to public and private network settings on Dedicated Servers. The affected servers are RISE and SCALE servers that OVHcloud delivered after 03 November 2026 at 09:00 UTC. OVHcloud identified the cause as a software issue and teams work to restore service.

State

Identified

Started

Ongoing for

1 h 32 min

Worst impact

Degraded

Timeline

1 update
19:1119:3419:5720:2020:43
DegradedUpdate postedTimes in UTC

Identified

1 h 32 min 100%

Updates

Times in UTC

As posted by OVHcloud

Identified

We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Dedicated Servers offer. Here are some supplementary details : Start time : 03/11/2026 08:00 UTC Impacted Service(s) : Administrative changes to the public and private network settings are temporarily unavailable for RISE and SCALE servers delivered after 03/11/2026 at 09:00 UTC. Customers Impact : Some customers are temporarily unable to modify the network configuration of their servers delivered after the incident date. Root Cause : This incident is caused by a software issue. Ongoing Actions : The incident has been identified and our teams are mobilised 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

34
BHSCCHERIGRAIEBLIMMR9RBX

OVHcloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

228

Days with an incident

90

Median duration

1 h 36 min

This incident

About the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

41 days
median 1 h 36 min
90 days agoToday

Other OVHcloud incidents

All incidents

OVHcloud·[DE1][Network] - Load balancer incident notification

The load balancer delivery service in the DE1 region did not work. OVHcloud reports that the incident is resolved. The incident lasted from 17:00 UTC to 19:13 UTC.

Resolved

OVHcloud·[GRA11][Network] - Network API incident notification

OVHcloud reports that the Network API for the public network and the private network (vRack) was unstable in the GRA11 region. The Managed Kubernetes Service in GRA11 was also affected. OVHcloud says that the incident is resolved and that it lasted about 6 hours and 18 minutes.

Resolved

OVHcloud·[Global][Dedicated Servers] - Delivery incident notification

OVHcloud Dedicated Servers delivery was degraded. The processing of suspension and reactivation requests was delayed in Zone Europe, Zone APAC, and Zone Canada. OVHcloud reports that the incident is resolved. It lasted about 7 hours and 25 minutes.

Resolved

OVHcloud·[RBX][Storage and Backups] - NAS HA Cluster11003 incident notification

We would like to inform you that an incident affected our NAS HA offering on the Cluster11003 in the RBX region. This incident has since been resolved. Please find the details of this incident below : Start time : 03/11/2026 10:10 UTC End time : 03/11/2026 10:24 UTC Impacted Service(s) : Some NAS HA services on the Cluster11003 were temporarily unavailable. Customers Impact : Customers were temporarily unable to access their data located on the Cluster11003. Root Cause : This incident was caused by a hardware issue. We thank you for your understanding and patience throughout this incident.

Resolved

OVHcloud·[DE1][Network] - Network API incident notification

The Network API for the public network and the private network (vRack) did not work in the DE1 region. The Managed Kubernetes Service in DE1 was also affected. OVHcloud reports that the incident is resolved. It lasted about 4 hours and 43 minutes.

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