outages.live
Live
OVHcloudIncident ·

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

Partial outageOfficial update
0

OVHcloud reports that all servers in rack RBX0840B05B are temporarily unavailable. This affects Dedicated Servers in the RBX region. OVHcloud identified the cause as an electrical equipment issue. OVHcloud teams are working to restore service.

State

Identified

Started

Ongoing for

54 min

Worst impact

Partial outage

Timeline

2 updates
13:1313:2613:4013:5314:07
Partial outageUpdate postedTimes in UTC

Investigating

14 min 26%

Identified

40 min 74%

Updates

Times in UTC

As posted by OVHcloud

Identified

We are currently experiencing an incident affecting our Dedicated Servers offering in the rack RBX0840B05B. The root cause has been identified. Please find the details of this incident below : Start time : 05/11/2026 13:05 UTC Impacted Service(s) : All servers in the rack RBX0840B05B are temporarily unavailable. Customers Impact : 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.

Investigating

We are currently experiencing an incident affecting our Dedicated Servers offering, which is causing temporary availability issues in the rack RBX0840B05B. Please find the details of this incident below : Start time : 05/11/2026 13:05 UTC Impacted Service(s) : All servers in the rack RBX0840B05B are temporarily unavailable. Customers Impact : Customers are temporarily unable to access their servers located on the specified rack. 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

2
RBXDedicated Servers || Global Infrastructure - RBX

OVHcloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

231

Days with an incident

90

Median duration

1 h 38 min

This incident

44% 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·[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

OVHcloud·[DE1][Network] - Load Balancer incident notification

OVHcloud reports that the Network API in the DE1 region was unstable. Customers could not create or resize Load Balancers, and network administrative actions returned API errors. OVHcloud says the incident is resolved. It lasted about 11 hours.

Resolved

OVHcloud·[GRA][Web Hosting] - Some Filerz incident notification

OVHcloud reports that some websites on some Filerz were temporarily unavailable in the GRA region. The affected components include clusters 100 to 128. OVHcloud reports that the incident is resolved. It started at 20:20 UTC and ended at 21:05 UTC, so it lasted 45 minutes.

Resolved

OVHcloud·[GLOBAL][Dedicated Servers] - Administrative network task incident notification

OVHcloud reports that administrative changes to public and private network settings did not work on Dedicated Servers. The affected regions include BHS, CCH, ERI, GRA, IEB, LIM, MR9, RBX, SBG, SGP, SYD, WAW, YNM, YYZ, US-EAST-VA, US-WEST-OR and US-WEST-LZ-SEA. OVHcloud resolved the incident, which lasted about 13 hours and 18 minutes.

Resolved

OVHcloud·[DE1][Network] - Load balancer incident notification

The load balancer delivery service in the DE1 region did not work. OVHcloud reports that the incident is resolved. The incident lasted from 17:00 UTC to 19:13 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