I have logged into the servers locally via KVM/Console.
The system OS is active, and the SSH service is fully running.
However, all external public internet routing and SSH access are completely dead/blocked from the outside on all ports (including default 22 and custom ports).
The Edge Network Firewall in the OVH panel is set to Disabled, and internal firewalls have been opened, but connectivity remains dead.
Since multiple servers are blocked at the exact same time, this is clearly a critical network routing or host node infrastructure failure on the OVH end.
I have already opened critical support tickets but have received no technical response yet. Can a community moderator or staff member please escalate this immediately to the network engineering team?
A mandatory security patch has started to be applied across all VPS services as of today.
A service interruption lasting less than 30 minutes could occur during the intervention, so it is very likely that you will be impacted by the deployment of this patch. Feel free to contact OVHcloud support to review your services if needed, via ticket, live chat or phone
Thank you for the update regarding the mandatory security patch.
However, the service interruption on my 4 VPS servers has already exceeded several hours, resulting in a total network blackout and SSH lockout. It seems this goes beyond the 30-minute patch window and is tied to the broader GRA region network incident.
I am unable to reach support via phone at the moment, but I have already submitted urgent support tickets (Ticket IDs: CS16224625 and CS16224566) and sent follow-up emails explaining the situation.
Since my production services are heavily impacted, could you please look into my account or escalate these tickets internally to the engineering team?
Iâm sorry, I no longer have visibility, feel free to stay vigilant about the response that will be given to you on the two tickets to get more information.
I wanted to update this thread and let you know that the issue has been successfully resolved and access to all servers is now fully restored. It turned out to be a configuration conflict that triggered during the reboot, which we managed to fix from our end.
We truly appreciate OVHcloud's reliable infrastructure. However, as these are production servers, it would be highly appreciated if any upcoming maintenance or node updates that might trigger such restarts could be communicated to us in advance. This will help us take proactive measures and ensure seamless business continuity.
Thank you to the community and the support team for your attention!
I completely understand, security must always come first. Thank you for the quick clarification and for keeping the infrastructure secure. You may close this ticket now.
For your information, I have several VPS that were configured in rescue mode (the services have been migrated elsewhere, the VPS is still funded for a few weeks), and with this reboot the VPS come back up ânormallyâ, even though the panel lists them as being in rescue.
Thank you for adding this important information. I contacted them as well, and it seems the shutdown was mandatory due to urgent security reasons, but that still doesn't justify not sending an automated alert to users. Thank you for sharing the solution, and I'm glad things are back to normal for you.
