OVHcloud has resolved an infrastructure incident that caused degraded performance for some Virtual Private Server (VPS) instances in its GRA1 and GRA2 regions.
The disruption began on September 3, 2026, at 15:16 UTC and lasted for more than three hours. OVHcloud confirmed that the incident was fully resolved at 18:41 UTC.
According to the company, the disruption was caused by an unexpected infrastructure failure.
Some VPS Instances Experienced Degraded Performance
The incident specifically affected OVHcloud’s Virtual Private Servers in the GRA1 and GRA2 regions.
During the disruption, some customers experienced degraded performance on their VPS instances. OVHcloud identified the source of the issue shortly after the incident began and said its technical teams were working to restore normal service.
The company did not report that all VPS instances in the affected regions were unavailable. Instead, the incident affected a subset of instances and resulted in temporarily degraded performance.
OVHcloud marked the incident as resolved at 18:41 UTC on September 3.
Based on the reported start and end times, the underlying disruption lasted approximately three hours and 25 minutes.
Storage Services Were Also Affected
The VPS incident was not the only service disruption reported in the Gravelines infrastructure at the same time.
OVHcloud also reported an incident affecting its Cloud Disk Array storage service in the GRA region. That disruption began at the same time — 15:16 UTC — and was also resolved at 18:41 UTC.
In its Public Cloud infrastructure, Block Storage services in GRA1 and GRA11 were affected during the same period. Some Block Storage services became temporarily unavailable, while customers could also experience degraded storage performance.
OVHcloud attributed the storage disruption to an unexpected infrastructure failure as well.
The matching timelines and root-cause descriptions indicate that multiple services were affected by the same underlying infrastructure event.
What OVHcloud Said About the Cause
OVHcloud described the cause as an “unexpected infrastructure failure” but did not provide additional technical details about the failed component in its incident notice.
There was no indication in the status update that the disruption was caused by a cyberattack or security incident.
After identifying the issue, OVHcloud said its teams had been mobilized to restore service as quickly as possible. The company subsequently confirmed that the incident affecting its VPS offering had been resolved.
Why Regional VPS Incidents Matter
Regional infrastructure failures can have consequences beyond individual virtual servers.
VPS environments depend on several layers of underlying infrastructure, including physical compute hosts, networking, storage and virtualization systems. A failure in shared infrastructure can therefore affect multiple virtual machines or related services at the same time.
The September 3 incident is particularly notable because VPS and storage services reported problems beginning at exactly the same time.
For customers running production workloads on VPS infrastructure, incidents of this kind also highlight the importance of avoiding a single point of failure.
Applications that require higher availability can be designed to distribute workloads across separate infrastructure locations, maintain independent backups and prepare recovery procedures that do not depend on a single hosting region.
Services Returned to Normal
OVHcloud reported the GRA1 and GRA2 VPS incident as resolved on September 3 at 18:41 UTC.
The related Cloud Disk Array and Public Cloud Block Storage incidents were also reported as resolved with the same end time.
No further customer action was specified in OVHcloud’s resolution notice.
The incident adds to the operational events infrastructure teams monitor closely because even relatively short regional disruptions can affect hosted applications, customer-facing services and workloads running on virtual servers.
