OVHcloud outage: [EU-WEST-PAR][Network] - Public network incident notification

Affected components

• EU-WEST-PAR-A
• EU-WEST-PAR-B
• EU-WEST-PAR-C

1. resolvedSep 25, 2026, 09:14 UTC

   We are pleased to inform you that the incident affecting our Network offer on the specific EU-WEST-PAR region has been resolved. <b>Start time :</b> 23/09/2026 14:00 UTC <b>End time :</b> 23/09/2026 17:19 UTC <b>Root Cause :</b> A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.

2. monitoringSep 23, 2026, 17:29 UTC

   Service has been fully restored since 23/09/2026 17:19 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : <b>Start time :</b> 23/09/2026 14:00 UTC <b>Impacted Service(s) :</b> Public Cloud services hosted in the EU-WEST-PAR region, including customer networks, experienced increased latency and packet loss. <b>Customers Impact :</b> Customers experienced latency and packet drops when accessing their Public Cloud services and networks hosted in the EU-WEST-PAR region. We apologize for any inconvenience caused and appreciate your understanding.

3. identifiedSep 23, 2026, 14:28 UTC

   We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Network offer on the specific EU-WEST-PAR region. Here are some supplementary details : <b>Start time :</b> 23/09/2026 14:00 UTC <b>Impacted Service(s) :</b> Public Cloud services hosted in the EU-WEST-PAR region, including customer networks, experience increased latency and packet loss. <b>Customers Impact :</b> Customers experience latency and packet drops when accessing their Public Cloud services and networks hosted in the EU-WEST-PAR region. <b>Root Cause :</b> A service disruption occurred due to an unexpected underlying infrastructure malfunction. <b>Ongoing Actions :</b> 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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in OVHcloud's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• HashiCorp Vault: HCP Terraform Returning 404sCritical · Sep 23, 2026, 17:43 UTC
• Shippo: Axlehire Shipment and Tracking OutageCritical · Sep 24, 2026, 08:51 UTC
• Supabase: Permission errors in the Supabase DashboardCritical · Sep 24, 2026, 10:37 UTC
• Shippo: Elevated error rate on Canada Post ShipmentCritical · Sep 24, 2026, 19:23 UTC
• Confluent Cloud: Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2Major · Sep 23, 2026, 11:47 UTC
• Telnyx: Intermittent 5XX responses on various API endpointsMajor · Sep 23, 2026, 13:49 UTC
• Elasticsearch: Degraded Performance: Cloud Provisioning DelaysMajor · Sep 23, 2026, 14:04 UTC
• Telnyx: Data Connectivity Issues - IMSI1Major · Sep 23, 2026, 14:16 UTC
• Fly.io: Elevated private networking errorsMajor · Sep 23, 2026, 15:13 UTC
• Telnyx: MMS Delivery Delays to AT&T DestinationsMajor · Sep 23, 2026, 16:42 UTC

How often does OVHcloud have incidents?

OVHcloud reported 39 incidents in the last 90 days, 30 of them major or critical. A typical incident lasted 3h 19m. See OVHcloud's uptime and incident history