outages.live
Live
OVHcloudIncident ·

[RBX8][Dedicated Servers] - Rack R809R07 incident notification

Partial outageOfficial update
0

Some OVHcloud dedicated servers in rack R809R07 in the RBX region are unavailable. OVHcloud identified the cause as an electrical equipment issue. OVHcloud teams are working to restore service.

State

Identified

Started

Ongoing for

31 min

Worst impact

Partial outage

Timeline

1 update
04:2204:3004:3704:4504:53
Partial outageUpdate postedTimes in UTC

Identified

31 min 100%

Updates

Times in UTC

As posted by OVHcloud

Identified

We are currently experiencing an incident affecting our Dedicated Servers offering in the rack R809R07. The root cause has been identified. Please find the details of this incident below : Start time : 10/11/2026 03:32 UTC Impacted Service(s) : Some servers in the rack R809R07 are temporarily unavailable. Customers Impact : Some customers are temporarily unable to access their servers located on the specified rack. Root Cause : This incident is caused by an electrical equipment issue. Ongoing Actions : Our teams are actively working to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

Affected components

2
RBXDedicated Servers || Global Infrastructure - RBX

OVHcloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

247

Days with an incident

90

Median duration

1 h 39 min

This incident

69% 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 39 min
90 days agoToday

Other OVHcloud incidents

All incidents

OVHcloud·[BHS1][Dedicated Servers] - Rack T01C28 incident notification

OVHcloud reports a partial outage of Dedicated Servers public network in rack T01C28 in the BHS region. Since 03:15 UTC, the public network in this rack is unavailable. OVHcloud identified a network equipment issue and its teams work to restore service.

Partial outage

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

OVHcloud reports that access to Zimbra mailboxes and webmail was unavailable. The affected components are Web Access and Zimbra Web Access. OVHcloud says the incident is resolved, and it lasted about 53 minutes.

Resolved

OVHcloud·[Global][Collaborative Solutions] - Zimbra Incident Notification

OVHcloud reports slow delivery to some Zimbra mailboxes and webmail accounts. The incident affects the Zimbra Delivery email component. OVHcloud identified the root cause and its teams are working to restore service. Incoming emails are queued.

Partial outage

OVHcloud·[GLOBAL][Domains] - .DK Domain Names Incident Notification

OVHcloud reports that multiple operations on .DK domain names do not work. Registration, Renew, Transfer, Restore, and Delete are affected for .DK domain names. OVHcloud identified the root cause and teams are working to restore service.

Partial outage

OVHcloud·[FR][Collaborative Solutions] - Zimbra Incident Notification

OVHcloud Zimbra Web Access, Delivery email, and Operations have a partial outage in France. Access to some mailboxes and webmail is unavailable, and incoming emails are queued. OVHcloud reports the incident resolved. The incident lasted from 07:10 UTC to 16:30 UTC on 09/11/2026.

Resolved · 1 affected

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