Live

[GRA1][Dedicated Servers] - Rack G125A23 incident notification

Partial outageOfficial update
0

We are currently experiencing an incident affecting our Dedicated Servers offering in the rack G125A23. The root cause has been identified. Please find the details of this incident below : Start time : 18/11/2026 13:40 UTC Impacted Service(s) : Some servers in the rack G125A23 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 a cooling system 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.

The latest update from OVHcloud.

State

Identified

Started

Ongoing for

21 min

Worst impact

Partial outage

Timeline

1 update
14:3014:3514:4114:4614:51
Partial outageUpdate postedTimes in UTC

Identified

21 min 100%

Updates

Times in UTC

As posted by OVHcloud

Identified

We are currently experiencing an incident affecting our Dedicated Servers offering in the rack G125A23. The root cause has been identified. Please find the details of this incident below : Start time : 18/11/2026 13:40 UTC Impacted Service(s) : Some servers in the rack G125A23 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 a cooling system 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

2
GRADedicated Servers || Global Infrastructure - GRA

OVHcloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

196

Days with an incident

90

Median duration

1 h 40 min

This incident

79% shorter than the median

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

24 days
median 1 h 40 min
90 days agoToday

Other OVHcloud incidents

All incidents

OVHcloud·[SBG5][Dedicated Servers] - Rack SBG0506B04C Incident Notification

The vRack Private Network does not work for Dedicated Servers in rack SBG0506B04C in the SBG region. OVHcloud identified the incident and states that a network equipment issue causes it. OVHcloud teams work to restore service.

Partial outage

OVHcloud·[RBX][Public VMware Cloud Foundation] - Public VCFaaS Incident Notification

Public VMware Cloud Foundation as-a-Service has degraded network, management plane, compute and storage in the RBX region. Some customers can have high latency and packet loss on the vRack network. OVHcloud reports that the incident is under investigation.

Degraded

OVHcloud·[RBX3][Dedicated Servers] - Rack 46G20 Incident Notification

Some Dedicated Servers in Rack 46G20 in the RBX region are temporarily unavailable. OVHcloud reported an electrical equipment issue and resolved the incident. The outage lasted 37 minutes, from 10:00 to 10:37 UTC.

Resolved

OVHcloud·[US][Backbone] - Backbone Incident Notification

The OVHcloud Backbone infrastructure in the US region has packet loss and increased latency. OVHcloud reports the status as investigating. OVHcloud gives no cause, workaround, or resolution time.

Degraded

OVHcloud·[GRA2][Dedicated Servers] - Rack G265B01 Incident Notification

Dedicated Servers in Rack G265B01 in the GRA region do not work. OVHcloud reports that the incident is resolved. The incident lasted from 07:48 UTC to 12:22 UTC on 18/11/2026.

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