outages.live
Live
OVHcloudIncident ·

[DE1][Network] - Load Balancer incident notification

Partial outageOfficial update
0

The Load Balancer service in the DE1 region does not work correctly. The Network API in DE1 is unstable, so users cannot create or resize Load Balancers. OVHcloud reports that it is investigating the incident.

State

Investigating

Started

Ongoing for

1 h 30 min

Worst impact

Partial outage

Timeline

1 update
10:1610:3811:0111:2311:46
Partial outageUpdate postedTimes in UTC

Investigating

1 h 30 min 100%

Updates

Times in UTC

As posted by OVHcloud

Investigating

We are currently experiencing an incident affecting our Public Cloud Network offering, which is causing temporary availability issues in the DE1 region. Please find the details of this incident below : Start time : 04/11/2026 05:30 UTC Impacted Service(s) : The Network API in the DE1 region is temporarily unstable. Creation or modification of any Load Balancer can have issues. Customers Impact : Customers may experience API errors when performing network administrative actions, and are temporarily unable to create or resize their Load Balancers. Running services remain unaffected. Ongoing Actions : Our teams are investigating to determine the origin of the incident to fix it. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

Affected components

2
DE1Network || Load Balancer - DE1

OVHcloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

230

Days with an incident

90

Median duration

1 h 37 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 37 min
90 days agoToday

Other OVHcloud incidents

All incidents

OVHcloud·[GRA][Web Hosting] - Some Filerz incident notification

OVHcloud reports that some websites on some Filerz were temporarily unavailable in the GRA region. The affected components include clusters 100 to 128. OVHcloud reports that the incident is resolved. It started at 20:20 UTC and ended at 21:05 UTC, so it lasted 45 minutes.

Resolved

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

OVHcloud reports that administrative changes to public and private network settings did not work on Dedicated Servers. The affected regions include BHS, CCH, ERI, GRA, IEB, LIM, MR9, RBX, SBG, SGP, SYD, WAW, YNM, YYZ, US-EAST-VA, US-WEST-OR and US-WEST-LZ-SEA. OVHcloud resolved the incident, which lasted about 13 hours and 18 minutes.

Resolved

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

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