Live

[GRA2][Dedicated Servers] - Rack G224B17 Incident Notification

0

Dedicated Servers in Rack G224B17 in the GRA region are unavailable. OVHcloud reports that the incident is resolved and lasted 16 minutes. The cause was a network equipment issue.

State

Resolved

Started

Lasted

16 min

Worst impact

Partial outage

Timeline

2 updates
11:4011:4411:4711:5111:55
Partial outageUpdate postedTimes in UTC

Investigating

16 min 100%

Updates

Times in UTC

As posted by OVHcloud

Resolved

We are pleased to inform you that the incident affecting our Dedicated Servers offering has been resolved. Start time : 19/11/2026 11:28 UTC End time : 19/11/2026 11:54 UTC Root Cause : This incident was caused by a Network equipment issue. We apologize for any inconvenience caused and appreciate your understanding.

Investigating

We are currently investigating an incident affecting our Dedicated Servers offering, which is causing temporary availability issue in Rack G224B17. Here are some supplementary details : Start time : 19/11/2026 11:28 UTC Impacted Service(s) : Servers in Rack G224B17 are temporarily unavailable. Customers Impact : Customers are temporarily unable to access their servers located in the specified rack. Ongoing Actions : Our teams are investigating to determine the origin of the incident and 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
GRADedicated Servers || Global Infrastructure - GRA

OVHcloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

184

Days with an incident

90

Median duration

1 h 46 min

This incident

85% 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 46 min
90 days agoToday

Other OVHcloud incidents

All incidents

OVHcloud·[Global][Identity, Security & Operations] - Logs Data Platform incident notification

We would like to inform you that the incident affecting our Identity, Security & Operations offering has now been resolved. Please find the details of this incident below : Start time : 19/11/2026 17:31 UTC End time : 19/11/2026 20:50 UTC Impacted Service(s) : The OpenSearch API of the Logs Data Platform service was temporarily unavailable. Customers Impact : Customers were temporarily unable to query or access their logs through the OpenSearch API. Log ingestion remained unaffected. Root Cause : This incident was caused by a network equipment issue. We thank you for your understanding and patience throughout this incident.

Resolved

OVHcloud·[US-WEST-OR][Storage] - Cloud Archive incident notification

The Cloud Archive service in the US-WEST-OR region has an increased error rate. Storing or retrieving archived data may fail. OVHcloud reports the root cause as identified.

Partial outage

OVHcloud·[BHS-CHI][Infrastructure] - Backbone incident notification

OVHcloud reports increased latency on the Backbone link between BHS and CHI. OVHcloud states that the incident is resolved. The incident lasted from 19:41 UTC to 20:38 UTC.

Resolved

OVHcloud·[Global][Collaborative Solutions] - Zimbra incident notification

OVHcloud Zimbra mailbox access, webmail, email delivery, and operations had a partial outage. OVHcloud reports that the incident is resolved. It lasted 3 hours and 4 minutes, from 14:30 to 17:34 UTC.

Resolved

OVHcloud·[Global][Web Hosting] - HTTP/2 incident notification

OVHcloud Web Hosting has degraded service on all Web Hosting clusters. HTTP/2 support is temporarily disabled, and sites are served over HTTP/1.1 only. OVHcloud is investigating.

Degraded

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