We are currently experiencing an incident affecting our Public Cloud offering, which is causing temporary availability issues in the RBX region.
Please find the details of this incident below :
<b>Start time :</b> 17/11/2026 10:01 UTC
<b>Impacted Service(s) :</b> Some instances in the RBX region are unavailable.
<b>Customers Impact :</b> Some customers are temporarily unable to access their instances located in the specified region.
<b>Ongoing Actions :</b> 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.
Click an issue to upvote it and help us better indicate the service status.
Service outage0
Degraded performance0
Error messages0
Timeouts / no response0
Authentication issues0
Network / connectivity issues0
Feature not working0
API errors0
Billing or usage issues0
Other0
Have a different problem?
Issue breakdown
0 total votes
Distribution of reported issues over the last 24 hours.
Service outage0%
Degraded performance0%
Error messages0%
Timeouts / no response0%
Authentication issues0%
Network / connectivity issues0%
Feature not working0%
API errors0%
Billing or usage issues0%
Other0%
90-Day Health Summary
Total Incidents
80
Aug 19 to Nov 17, 2026
Major / Critical
38
48% of the total
Minor Incidents
42
Avg. 0.5 per day
Median Resolution
1h 25m
P95: 93h 36m
Across all 4,387 services Pulsetic tracks, the incidents their status pages reported over the last 12 months had a median resolution time of 1h 58m, and 33% were rated major or critical by the provider. These numbers are calculated separately from the 90-day figures for OVHcloud above.
Check the status badge at the top of this page for the current status. Pulsetic follows the official status page and cross-references it with user reports to give you the most accurate picture.
How often does OVHcloud go down?
Based on our 90-day data, we've recorded 80 incidents, of which 38 were major or critical. The median resolution time is 1h 25m.
How are outages detected?
Pulsetic follows the official status page and records the incidents the provider posts there. Crowdsourced user reports and Pulsetic's own synthetic checks add an early warning, which can surface an issue before the official status page mentions it.
Is it down for everyone or just me?
The outage map and region breakdown help answer this. If reports are concentrated in one area it may be regional; if hotspots appear globally it's a widespread outage. Submit your own report to help others understand the scope.
What does "never acknowledged" mean?
"Never acknowledged" means Pulsetic recorded a service disruption from user reports and its own checks, but the official status page never posted an incident for it. This is one of the core reasons teams use third-party monitoring alongside official status pages.
Get an email when OVHcloud opens, updates or resolves an incident.
Add it as a dependency monitor. The Free plan includes one. See how it works