Live

[GLOBAL][Hosted Private Cloud] - Managed vMware vSphere Maintenance Notification

MaintenanceOfficial update

Scheduled maintenance is currently in progress. We will provide updates as necessary.

The latest update from OVHcloud.

State

In progress

Started

Ongoing for

31 min

Worst impact

Maintenance

Timeline

1 update
15:2315:3015:3815:4615:54
MaintenanceUpdate postedTimes in UTC

In progress

31 min 100%

Updates

Times in UTC

As posted by OVHcloud

In progress

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Affected components

9
Management planeManaged VMware vSphere || RBX - Management planeManaged VMware vSphere || LIM - Management planeManaged VMware vSphere || SBG - Management planeManaged VMware vSphere || ERI - Management planeManaged VMware vSphere || BHS - Management planeManaged VMware vSphere || WAW - Management planeManaged VMware vSphere || GRA - Management plane

OVHcloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

177

Days with an incident

90

Median duration

1 h 49 min

This incident

Not comparable

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

7 days
median 1 h 49 min
90 days agoToday

Other OVHcloud incidents

All incidents

OVHcloud·[RBX5][Dedicated Servers] - Rack 45D18 incident notification

The vRack network does not work for Dedicated Servers in rack 45D18 in the RBX region. OVHcloud reports that the incident is resolved. It lasted from 08:07 UTC to 11:14 UTC.

Resolved

OVHcloud·[EU/US/APAC][Infrastructure] - Backbone incident notification

OVHcloud reports packet loss on some backbone links between Europe and APAC, and between North America and APAC. The incident is resolved. OVHcloud gives the start time as 08:15 UTC and the end time as 09:15 UTC on 20/11/2026.

Resolved

OVHcloud·[GLOBAL][AI & Machine Learning] - AI Endpoint Incident Notification

The AI Endpoint component of OVHcloud AI & Machine Learning is not available. OVHcloud reports that the incident is resolved. The incident lasted from 06:25 UTC to 07:12 UTC.

Resolved

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 had an increased error rate, and customers may have had errors when they stored or retrieved archived data. OVHcloud reports that the incident is resolved. The incident lasted from 19/11/2026 16:30 UTC to 19/11/2026 22:00 UTC.

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