Opti9 incident

WAN Connectivity Issues - GSC/New York

Major Resolved View vendor source →

Opti9 experienced a major incident on May 30, 2026 affecting Cloud Director - GSC and Veeam Service Provider Console - gsc2-acw and 1 more component, lasting 6d 5h. The incident has been resolved; the full update timeline is below.

Started
May 30, 2026, 01:07 PM UTC
Resolved
Jun 05, 2026, 06:09 PM UTC
Duration
6d 5h
Detected by Pingoru
May 30, 2026, 01:07 PM UTC

Affected components

Cloud Director - GSCVeeam Service Provider Console - gsc2-acwCompute - GSCVeeam Service Provider Console - gsc3-acwNetwork Core - GSCVeeam Cloud Connect Backup - pub1-gsc2-cgbStorage - GSCVeeam Cloud Connect Replication - pub1-gsc2-cgrFacilities - Power/Cooling - GSCVeeam Backup for Microsoft 365 - gsc3-m-portal

Update timeline

  1. identified May 30, 2026, 01:07 PM UTC

    Our teams are currently investigating a network issue impacting WAN connectivity in this region. We have identified the issue and are working toward resolution. If you have any questions or concerns, please contact our support team.

  2. monitoring May 30, 2026, 01:50 PM UTC

    Mitigation has been applied, and we are continuing to monitor the situation to ensure stability.

  3. monitoring May 30, 2026, 03:35 PM UTC

    We are aware of routing issues in this region that are impacting the availability of Google services. Our team is investigating.

  4. monitoring May 30, 2026, 05:42 PM UTC

    The issue impacting Google-related services has now been resolved for the majority of clients. Our team is continuing to investigate all remaining open incident tickets to ensure complete resolution and address any outstanding cases.

  5. identified May 30, 2026, 09:34 PM UTC

    Our team has identified that upstream carrier we rerouted to for mitigating this issue is not providing a complete set of routes. As a result, there are connectivity issues with a selected IPv4 subnets. We are working with the provider to address the issue.

  6. identified May 31, 2026, 12:41 AM UTC

    We are actively engaged with our upstream carriers working toward resolution, and will provide another update at 10PM ET or sooner.

  7. identified May 31, 2026, 02:07 AM UTC

    Investigation and remediation efforts remain ongoing in coordination with our upstream carriers. The next status update will be provided by 12:00 AM ET or earlier if warranted.

  8. identified May 31, 2026, 04:03 AM UTC

    Our team is adjusting routing between upstream carriers to restore unavailable routes.

  9. monitoring May 31, 2026, 01:04 PM UTC

    Rerouting efforts were successful overnight and were completed at 2AM ET. At this time, all services have been restored. If you are still experiencing connectivity issues, please engage with our support team.

  10. monitoring Jun 03, 2026, 01:23 PM UTC

    The Root Cause Analysis (RCA) for this incident has been published and distributed to all impacted clients. Should you require a copy of the RCA, or have any additional questions regarding the incident, please contact our Support team for assistance.

  11. resolved Jun 05, 2026, 06:09 PM UTC

    This incident has been resolved.