[US-EAST-LZ-MIA][Network] - Localzone incident notification

Event timeline

How this incident unfolded, from the official status page.

1. Investigating

   23 days ago

   OVHcloud - Public Cloud

   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.

2. Monitoring

   23 days ago

   OVHcloud - Public Cloud

   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. Resolved

   23 days ago

   OVHcloud - Public Cloud

   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.