OVHcloud outage: [US-EAST-LZ-MIA][Network] - Localzone incident notification

Affected components

• US-EAST-LZ-MIA

1. resolvedOct 1, 2026, 08:03 UTC

   We are pleased to inform you that the incident affecting our LocalZones offering has been resolved. <b>Start time :</b> 01/10/2026 05:06 UTC <b>End time :</b> 01/10/2026 07:26 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. monitoringOct 1, 2026, 07:29 UTC

   Service has been fully restored since 01/10/2026 07:26 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : <b>Start time :</b> 01/10/2026 05:06 UTC <b>Impacted Service(s) :</b> The public network was temporarily slowed down or became unstable. <b>Customers Impact :</b> Customers temporarily experienced latency or disruptions on the public network in this region. <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.

3. investigatingOct 1, 2026, 06:09 UTC

   We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Network offer on the specific US-EAST-LZ-MIA region. Here are some supplementary details : <b>Start time :</b> 01/10/2026 05:41 UTC <b>Impacted Service(s) :</b> The public network may temporarily be slowed down or become unstable. <b>Customers Impact :</b> Customers may temporarily experience latency or disruptions on the public network in this 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.

• Shippo: Deutsche Post Tracking DisruptionCritical · Oct 1, 2026, 04:41 UTC
• Bitbucket: Job processing and scheduling is degraded affecting multiple Atlassian productsMajor · Oct 1, 2026, 02:55 UTC
• Confluence: Job processing and scheduling is degraded affecting multiple Atlassian productsMajor · Oct 1, 2026, 02:55 UTC
• Akamai: Origin Server Connectivity Issues with Elevated Errors in APAC RegionMinor · Sep 22, 2026, 14:28 UTC
• Cloudflare: Cloudflare One Clients are incorrectly challenged on some sitesMinor · Sep 22, 2026, 19:23 UTC
• Zoom: Service Degradation Affecting Customer Using Polycom Devices Going OfflineMinor · Sep 25, 2026, 17:45 UTC
• Twilio: MMS Delivery Delays from a Subset of Twilio Long Codes to GCI United StatesMinor · Sep 26, 2026, 03:16 UTC
• Snyk: Snyk CLI Scans DegradedMinor · Sep 28, 2026, 14:26 UTC
• Clerk: Development instances only - Apple rejecting emailsMinor · Sep 28, 2026, 15:23 UTC
• Supabase: Intermittent latency in Eastern USMinor · Sep 29, 2026, 16:26 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