Live

[GRA][Containers & Orchestration] - Managed Private Registry incident notification

0

We would like to inform you that an incident affected our Managed Private Registry offering. This incident has since been resolved. Please find the details of this incident below : Start time : 17/11/2026 09:27 UTC End time : 17/11/2026 09:40 UTC Impacted Service(s) : Some Registries in the GRA region were temporarily unavailable. Customers Impact : Customers were temporarily unable to access their Registries located in the specified region. Root Cause : This incident was caused by a software issue. We thank you for your understanding and patience throughout this incident.

The latest update from OVHcloud.

State

Resolved

Started

Lasted

1 min

Worst impact

Notice

Timeline

1 update
15:1415:1515:1515:1515:15
NoticeUpdate postedTimes in UTC

Resolved

1 min 100%

Updates

Times in UTC

As posted by OVHcloud

Resolved

We would like to inform you that an incident affected our Managed Private Registry offering. This incident has since been resolved. Please find the details of this incident below : Start time : 17/11/2026 09:27 UTC End time : 17/11/2026 09:40 UTC Impacted Service(s) : Some Registries in the GRA region were temporarily unavailable. Customers Impact : Customers were temporarily unable to access their Registries located in the specified region. Root Cause : This incident was caused by a software issue. We thank you for your understanding and patience throughout this incident.

Affected components

2
GRAContainers & Orchestration || Managed Private Registry - GRA

OVHcloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

218

Days with an incident

90

Median duration

1 h 37 min

This incident

100% shorter than the median

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

26 days
median 1 h 37 min
90 days agoToday

Other OVHcloud incidents

All incidents

OVHcloud·[EU][Dedicated Servers] - IP Failover/VMAC incident notification

OVHcloud reports delays for Additional IP move and virtual MAC creation operations on Dedicated Servers in the EU region. The affected locations include CCH, ERI, GRA, IEB, LIM, MR9, RBX, SBG, and WAW. OVHcloud identified the cause as a software issue and continues to monitor the situation.

Degraded

OVHcloud·[US-CENTRAL-LZ-SLC][LocalZones] - Salt Lake City incident notification

OVHcloud reports that public network and resource management did not work in the US-CENTRAL-LZ-SLC-A Local Zone. OVHcloud states that the incident is resolved. The incident lasted about one hour.

Resolved

OVHcloud·[RBX][Public Cloud] - Compute Instance incident notification

OVHcloud reports that some Compute Instances in the RBX region are unavailable. The affected components are RBX-A and Compute - Instance RBX - RBX-A. OVHcloud is investigating the incident.

Partial outage

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

OVHcloud Dedicated Servers in rack R831A07 in the RBX region did not work. Some servers were unavailable from 17/11/2026 08:18 UTC to 17/11/2026 10:23 UTC. OVHcloud reports that the incident is resolved and the cause was an electrical equipment issue.

Resolved

OVHcloud·[ERI1C][Backup as a Service] - Rack ERI0111E01A - Veeam Backup Managed incident notification

OVHcloud reports that some Veeam Backup Managed storage servers were temporarily unavailable in the ERI1 region. Some customers could not run or restore their VM backups. OVHcloud reports that the incident is resolved and that it lasted about 89 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