[DE1][Network] - Public network incident notification
OVHcloud reports that Public Cloud network management operations are unstable in the DE1 region. Customers can get errors or delays when they create or change the network configuration of their instances. OVHcloud identified the cause as a software issue, and the fix is in progress with an estimated time of 19:00 UTC.
State
Identified
Started
1 h ago
2026-11-02 15:44 UTC
Ongoing for
1 h 25 min
Worst impact
Degraded
Timeline
3 updatesIdentified
1 h 25 min 100%
Updates
Times in UTCAs posted by OVHcloud
We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : Our technical team is actively working on the incident. We currently have an ETA of 02/11/2026 19:00 UTC. We will update this page if we receive any further information before then. 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.
We are currently experiencing an incident affecting our Public Cloud offering in the DE1 region. The root cause has been identified. Please find the details of this incident below : Start time : 02/11/2026 09:22 UTC Impacted Service(s) : Some network administrative tasks may be temporarily slowed down. This does not affect instances. Customers Impact : Customers may experience errors or delays when creating or modifying the network configuration of their instances. 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.
We are currently experiencing an incident affecting our Public Cloud offering in the DE1 region. The root cause has been identified. Please find the details of this incident below : Start time : 02/11/2026 09:22 UTC Impacted Service(s) : Public Cloud network management operations are temporarily unstable in the DE1 region. Customers Impact : Customers may experience errors or delays when creating or modifying the network configuration of their instances. 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
2OVHcloud in the last 90 days
Full historyIncidents in 90 days
219
Days with an incident
90
Median duration
1 h 37 min
This incident
About the median
Other OVHcloud incidents
All incidentsOVHcloud·[Global][Domains] - .TOP Domains Name incident notification
The .TOP domain operations do not work. Registration, Renew, Transfer, Restore, and Delete are affected in all regions. OVHcloud reports the state as identified. The cause comes from a provider.
OVHcloud·[SBG5][Dedicated Servers] - Rack SBG0505B05B incident notification
Some servers in rack SBG0505B05B were unavailable. This affected the Dedicated Servers offering in the SBG region. OVHcloud reports that the incident is resolved and that it lasted 2 hours and 52 minutes.
OVHcloud·[Global][Domains] - .MG Domains Name incident notification
OVHcloud reports that Registration, Renew, Transfer, Restore, and Delete do not work for .MG domains. OVHcloud identified the cause and states that the cause comes from its provider. OVHcloud teams are working to restore service.
OVHcloud·[Global][Domains] - .CO Domains Name incident notification
OVHcloud reports that multiple .CO domain operations do not work. Registration, Renew, Transfer, Restore, and Delete for .CO domains are affected. OVHcloud identified the cause and works with its provider to restore service.
OVHcloud·[ERI1][Dedicated Servers] - Rack E105A01 incident notification
OVHcloud reports that Dedicated Servers in rack E105A01 in the ERI region were unavailable. The incident is resolved. It lasted 5 minutes, from 07:38 to 07:43 UTC.
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