OVHcloud reported "[ERI1][Dedicated Servers] - Rack E105A01 incident notification" on its status page at 2026-11-02 07:43 UTC. OVHcloud reports that Dedicated Servers in rack E105A01 in the ERI region were temporarily unavailable. The incident is resolved and lasted about 5 minutes.

OVHcloud lists these components: ERI, Dedicated Servers || Global Infrastructure - ERI.

When did the incident start and end?

It started at 2026-11-02 07:43 UTC and ended at 2026-11-02 07:57 UTC. It lasted 14 min.

How do I get alerts for OVHcloud?

Subscribe to the OVHcloud live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of OVHcloud. outages.live reads it every few minutes and keeps every update. A language model writes the summary from those updates.

OVHcloudIncident · 2026-11-02 07:43 UTC

[ERI1][Dedicated Servers] - Rack E105A01 incident notification

ResolvedOfficial update

OVHcloud reports that Dedicated Servers in rack E105A01 in the ERI region were temporarily unavailable. The incident is resolved and lasted about 5 minutes.

State

Resolved

Started

2 h ago

2026-11-02 07:43 UTC

Lasted

14 min

until 2026-11-02 07:57 UTC

Worst impact

Partial outage

Timeline

2 updates

07:4307:4607:5007:5307:57

Partial outageUpdate postedTimes in UTC

Identified

14 min 100%

Updates

Times in UTC

As posted by OVHcloud

Resolved2026-11-02 07:57 UTC

We would like to inform you that the incident affecting our Dedicated Servers offering has now been resolved. Please find the details of this incident below : Start time : 02/11/2026 07:38 UTC End time : 02/11/2026 07:43 UTC Impacted Service(s) : All servers in the rack E105A01 were temporarily unavailable. Customers Impact : Customers were temporarily unable to access their servers located on the specified rack. Root Cause : This incident was caused by this maintenance : https://network.status-ovhcloud.com/incidents/gmhxf7yn6t3h We thank you for your understanding and patience throughout this incident.

Identified2026-11-02 07:45 UTC

We are currently experiencing an incident affecting our Dedicated Servers offering in the rack E105A01. The root cause has been identified. Please find the details of this incident below : Start time : 02/11/2026 07:38 UTC Impacted Service(s) : All servers in the rack E105A01 are temporarily unavailable. Customers Impact : Customers are temporarily unable to access their servers located on the specified rack. Root Cause : This incident is caused by this maintenance : https://network.status-ovhcloud.com/incidents/gmhxf7yn6t3h 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

ERIDedicated Servers || Global Infrastructure - ERI

OVHcloud in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

220

Days with an incident

Median duration

1 h 35 min

This incident

85% shorter than the median

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

41 days

median 1 h 35 min

90 days agoToday

Other OVHcloud incidents

All incidents

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.

Partial outageupdated 25 min ago

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.

Partial outageupdated 31 min ago

OVHcloud·[RBX3][Dedicated Servers] - Rack 42C19 incident notification

OVHcloud reports that some Dedicated Servers in rack 42C19 in the RBX region were temporarily unavailable. The incident is resolved. It lasted from 05:48 UTC to 07:18 UTC on 02/11/2026. The cause was an electrical equipment issue.

Resolvedresolved 2 h ago

OVHcloud·[SBG8][Virtual Private Servers] - VPS Incident Notification

Some Virtual Private Servers in the SBG8 region were temporarily unreachable. The incident affected some VPS in the SBG region. OVHcloud identified a network equipment issue as the cause. OVHcloud resolved the incident. The incident started at 17:55 UTC and ended at 19:54 UTC.

Resolvedresolved 13 h ago

OVHcloud·[SBG6/8][Virtual Private Servers] - VPS Incident Notification

Some Virtual Private Servers in the SBG5, SBG6 and SBG8 regions were unreachable. OVHcloud reports that the incident is resolved. It lasted from 17:55 UTC to 19:30 UTC.

Resolvedresolved 14 h ago

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.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.

RSS

https://outages.cc/feed.xml?providers=ovhcloud

Slack

/feed subscribe https://outages.cc/feed.xml?providers=ovhcloud

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane