OVHcloud experienced a major incident affecting IAM (Identity and Access Management) login functionality for Public Cloud instances across multiple global regions for 4.3 hours on March 22, 2026. Customers were temporarily unable to login to their compute instances due to an unexpected underlying infrastructure malfunction. The incident was resolved after teams implemented a fix and completed service recovery operations.
We are pleased to inform you that the incident affecting our Compute - Instance offer has been resolved.
Start time : 22/03/2026 10:55 UTC
End time : 22/03/2026 20:51 UTC
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.
We apologize for any inconvenience caused and appreciate your understanding.
We have new information regarding the incident that affected your service(s).
Please find below an update on the situation:
Update : Our teams are still working on recovering the impacted services.
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.
We have new information regarding the incident that affected your service(s).
Please find below an update on the situation:
Update : A fix has been implemented by our teams.
Ongoing Actions : Our teams are currently recovering impacted services.
We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.
We are currently investigating an incident affecting our Compute - Instance offering, which is causing temporary availability issue in the GLOBAL region.
Here are some supplementary details :
Start time : 22/03/2026 10:55 UTC
Impacted Service(s) : Some instances in the GLOBAL region are unreachable using IAM (Identity and Access Management).
Customers Impact : Some customers are temporarily unable to login to their Public Cloud instances using IAM (Identity and Access Management).
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.
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.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6020 services available
Integrations with