outages.live
Live
OVHcloudIncident ·

[GRA6][Virtual Private Servers] - VPS incident notification

Partial outageOfficial update
0

OVHcloud reports that Backup and image management features do not work correctly for Virtual Private Servers in the GRA6 region. The incident affects the GRA and EU-WEST-GRA components. OVHcloud is investigating the cause.

State

Investigating

Started

Ongoing for

36 min

Worst impact

Partial outage

Timeline

1 update
17:2817:3717:4617:5518:04
Partial outageUpdate postedTimes in UTC

Investigating

36 min 100%

Updates

Times in UTC

As posted by OVHcloud

Investigating

We are currently experiencing an incident affecting our Virtual Private Servers offering, which is causing temporary instability issues in the GRA6 region. Please find the details of this incident below : Start time : 05/11/2026 15:26 UTC Impacted Service(s) : Backup and image management features are temporarily unstable in the GRA6 region. Customers Impact : Customers may experience errors or delays when creating, restoring or managing their VPS backups and images. 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

4
GRAEU-WEST-GRAVirtual Private Servers || Operating System - GRAVirtual Private Servers || Additional services - EU-WEST-GRA

OVHcloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

235

Days with an incident

90

Median duration

1 h 38 min

This incident

63% 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 38 min
90 days agoToday

Other OVHcloud incidents

All incidents

OVHcloud·[GRA6][Storage] - Instance Backup incident notification

OVHcloud reports that Instance Backup and image management were unstable in the GRA6 region. Customers may have had failures when they created backups or managed images. OVHcloud states that the incident is resolved and lasted 1 hour and 39 minutes.

Resolved

OVHcloud·[EU-WEST-PAR-B][Storage] - Block Storage incident notification

OVHcloud reports degraded performance on some Block Storage volumes in the EU-WEST-PAR-B region. This causes increased latency and reduced performance on affected volumes. OVHcloud is investigating the incident and its teams work to improve storage performance.

Degraded

OVHcloud·[EU-WEST-PAR-A][Storage] - Block Storage incident notification

OVHcloud reports that Block Storage volumes in the EU-WEST-PAR-A region have performance degradation. Some volumes have increased latency and reduced performance. OVHcloud is investigating and its teams work to improve the storage infrastructure performance.

Degraded

OVHcloud·[RBX8][Dedicated Servers] - Rack RBX0840B05B incident notification

All servers in rack RBX0840B05B of the OVHcloud Dedicated Servers offering in the RBX region are temporarily unavailable. OVHcloud identified the cause as an electrical equipment issue. Some servers in the rack are becoming operational again.

Partial outage

OVHcloud·[US/SYD][Infrastructure] - Backbone incident notification

We would like to inform you that an incident affected our Infrastructure offering. This incident has since been resolved. Please find the details of this incident below : Start time : 04/11/2026 13:37 UTC End time : 04/11/2026 14:00 UTC Impacted Service(s) : Increased latency was observed on the link between US and SYD. Customers Impact : Customers may have experienced increased latency when accessing their services passing from US and SYD. Root Cause : This incident was caused by our provider. We thank you for your understanding and patience throughout this incident.

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