OVHcloud reported "[RBX8][Compute - Instance] - Instance incident notification" on its status page at 2026-10-27 08:44 UTC.

OVHcloud lists these components: RBX-A, Compute - Instance || RBX - RBX-A.

When did the incident start and end?

It started at 2026-10-27 08:44 UTC and ended at 2026-10-27 15:05 UTC. It lasted 6 h 20 min.

How do I get alerts for OVHcloud?

Subscribe to the OVHcloud live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of OVHcloud. outages.live reads it every few minutes and keeps every update.

OVHcloudIncident · 2026-10-27 08:44 UTC

[RBX8][Compute - Instance] - Instance incident notification

ResolvedOfficial update

We are pleased to inform you that the incident affecting our Compute - Instance offering in the RBX8 region has been resolved. Start time : 27/10/2026 07:49 UTC End time : 27/10/2026 14:18 UTC Root Cause : This incident was caused by this maintenance : https://network.status-ovhcloud.com/incidents/f629kcrn2cvg We apologize for any inconvenience caused and appreciate your understanding.

The latest update from OVHcloud.

State

Resolved

Started

6 d ago

2026-10-27 08:44 UTC

Lasted

6 h 20 min

until 2026-10-27 15:05 UTC

Worst impact

Partial outage

Timeline

3 updates

08:4410:2011:5513:3015:05

Partial outageUpdate postedTimes in UTC

Identified

6 h 20 min 100%

Updates

Times in UTC

As posted by OVHcloud

Resolved2026-10-27 15:05 UTC

Identified2026-10-27 11:23 UTC

We have new information regarding this incident that affected your service(s). Please find below an update on the situation: Update : The fix has been implemented. Some instances are operational again, and the remaining instances will be operational soon. We apologize for any inconvenience caused and appreciate your understanding.

Identified2026-10-27 08:44 UTC

We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific RBX8 Region. Here are some supplementary details : Start time : 27/10/2026 07:49 UTC Impacted Service(s) : Some instances in the RBX8 region are unreachable. Customers Impact : Some customers are temporarily unable to access instances located on the specified region. Root Cause : This incident is caused by this maintenance : https://network.status-ovhcloud.com/incidents/f629kcrn2cvg Ongoing Actions : The incident has been identified and our teams are mobilised 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

RBX-ACompute - Instance || RBX - RBX-A

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.cc/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.cc/feed.xml?providers=ovhcloud

Slack

/feed subscribe https://outages.cc/feed.xml?providers=ovhcloud

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane