[DE1][Network] - Public network incident notification
OVHcloud reports that public network management operations were unstable in the DE1 region. Customers had errors or delays when they created or changed the network configuration of their instances. OVHcloud resolved the incident, which lasted from 09:22 UTC to 18:32 UTC.
State
Resolved
Started
3 h ago
2026-11-02 15:44 UTC
Lasted
2 h 51 min
until 2026-11-02 18:35 UTC
Worst impact
Degraded
Timeline
3 updatesIdentified
2 h 51 min 100%
Updates
Times in UTCAs posted by OVHcloud
We would like to inform you that the incident affecting our Public Cloud offering has now been resolved. Please find the details of this incident below : Start time : 02/11/2026 09:22 UTC End time : 02/11/2026 18:32 UTC Impacted Service(s) : Some network administrative tasks may have been temporarily slowed down. This did not affect instances. Customers Impact : Customers may have experienced errors or delays when creating or modifying the network configuration of their instances. Root Cause : This incident was caused by a software issue. We thank you for your understanding and patience throughout this incident.
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) : 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
223
Days with an incident
90
Median duration
1 h 37 min
This incident
1.7× 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. OVHcloud reports that it identified the cause. The cause is from a provider. OVHcloud works with the provider to restore service.
OVHcloud·[SBG5][Dedicated Servers] - Rack SBG0505B05B incident notification
OVHcloud reports that some Dedicated Servers in rack SBG0505B05B in the SBG region were temporarily unavailable. OVHcloud identified the cause and resolved the incident. The incident lasted from 09:50 UTC to 12:42 UTC on 02/11/2026.
OVHcloud·[Global][Domains] - .MG Domains Name incident notification
The .MG domain service does not work for Registration, Renew, Transfer, Restore, and Delete operations. OVHcloud has identified the incident. The cause comes from a provider, and OVHcloud teams work to restore the service.
OVHcloud·[Global][Domains] - .CO Domains Name incident notification
The .CO domain registration, renew, transfer, restore, and delete operations do not work for OVHcloud customers. OVHcloud identified the cause as its provider and works with that 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 temporarily unavailable. The incident is resolved and lasted about 5 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.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