Opti9 incident

Network Issues - LAX/Los Angeles

Major Resolved View vendor source →

Opti9 experienced a major incident on September 2, 2026 affecting Veeam Service Provider Console - veeam-lax-acw and Compute - LAX and 1 more component, lasting 2d 1h. The incident has been resolved; the full update timeline is below.

Started
Sep 02, 2026, 07:02 PM UTC
Resolved
Sep 04, 2026, 09:00 PM UTC
Duration
2d 1h
Detected by Pingoru
Sep 02, 2026, 07:02 PM UTC

Affected components

Veeam Service Provider Console - veeam-lax-acwCompute - LAXZerto - LAXNetwork Core - LAXVeeam Cloud Connect Backup - laxccStorage - LAXVeeam Cloud Connect Replication - laxccrFacilities - Power/Cooling - LAXCloud Director - LAXVeeam Backup for Cloud Director - LAX

Update timeline

  1. investigating Sep 02, 2026, 07:02 PM UTC

    Our teams are currently investigating a network issue impacting multiple services in this region. If you have any questions or concerns, please contact our support team.

  2. identified Sep 02, 2026, 11:10 PM UTC

    We are continuing to work closely with our upstream service providers to resolve the network issue currently impacting service availability across the LAX/Southwest region. To help reduce the impact to customers while the carriers address their fiber cuts, we have activated an alternate carrier circuit and rerouted traffic through alternate network paths. Opti9 systems have successfully transitioned to the alternate route, and we are seeing a significant improvement in network latency and packet loss. We remain in communication with all impacted providers and are working to obtain timely updates and restore normal service as quickly as possible. We understand that service disruptions can affect your business operations, and we sincerely appreciate your patience as our teams continue working toward full resolution. We will share another update as soon as additional information is available or service has been fully restored.

  3. monitoring Sep 03, 2026, 02:10 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Sep 04, 2026, 09:00 PM UTC

    This incident has been resolved.