outages.live
Live
OVHcloudMaintenance ·

[ERI1][Infrastructure] - Multiple racks maintenance notification

ResolvedOfficial update

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

The latest update from OVHcloud.

State

Resolved

Started

Lasted

4 h 15 min

Worst impact

Maintenance

Timeline

3 updates
07:3008:3309:3710:4111:45
MaintenanceUpdate postedTimes in UTC

Scheduled

3 min 1%

In progress

4 h 12 min 99%

Updates

Times in UTC

As posted by OVHcloud

Resolved
In progress

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

Scheduled

As part of our continuous improvement plan, we will be carrying out maintenance on our electrical infrastructure. Start time : 12/11/2026 07:30 UTC End time : 12/11/2026 15:00 UTC List of concerned racks : - Rack ERI0111A01A - Rack ERI0111A01B - Rack ERI0111A02A - Rack ERI0111A02B - Rack ERI0111A03A - Rack ERI0111A03B - Rack ERI0111A04A - Rack ERI0111A04B Service impact : In the worst case, customers could experience a temporary reboot or shutdown of their servers. Service improvement : As part of our continuous improvement policy, we will be performing maintenance on our electrical infrastructure. Thank you for your understanding.

Affected components

1
ERI1

OVHcloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

258

Days with an incident

90

Median duration

1 h 41 min

This incident

Not comparable

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

41 days
median 1 h 41 min
90 days agoToday

Other OVHcloud incidents

All incidents

OVHcloud·[RBX8][Dedicated Servers] - Racks RBX0841A05A and RBX0841A05B incident notification

OVHcloud reports that some Dedicated Servers in racks RBX0841A05A and RBX0841A05B in the RBX region are unavailable. OVHcloud identified a cooling system issue. All servers in rack RBX0841A05B and many servers in rack RBX0841A05A now work.

Partial outage

OVHcloud·[GRA3][Dedicated Servers] - Rack GRA0326A03B incident notification

OVHcloud reports that the public network did not work in rack GRA0326A03B in the GRA region. This affected Dedicated Servers. The incident is resolved. It lasted from 10:37 UTC to 14:35 UTC.

Resolved

OVHcloud·[RBX/GRA/SBG][Collaborative Solutions] - EmailPro, Hosted Exchange, Private Exchange, MX Plan incident notification

OVHcloud reports that some management operations, such as password changes and account deletions, did not work on EmailPro, Hosted Exchange, Private Exchange and MX Plan in the RBX, GRA and SBG datacenters. OVHcloud says the incident is resolved. It lasted 1 hour and 41 minutes.

Resolved

OVHcloud·[Global][Databases & Data Analytics] - API incident notification

OVHcloud reports that the API of PostgreSQL, MySQL, Valkey, ClickHouse, Dashboards, Kafka, Kafka Connect, Kafka MirrorMaker and OpenSearch had slowness and errors in BHS, DE, GRA, EU-WEST-PAR, EU-SOUTH-MIL, AP-SOUTH-MUM, RBX, SBG, SGP, UK and WAW. OVHcloud resolved the incident. The incident lasted 53 minutes, from 09:15 UTC to 10:08 UTC on 12 November 2026.

Resolved

OVHcloud·[RBX3][Dedicated Servers] - Rack 43N06 incident notification

OVHcloud reports that some Dedicated Servers in rack 43N06 in the RBX region were unavailable. OVHcloud identified an electrical equipment issue. OVHcloud resolved the incident, which lasted about 74 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