VMware VeloCloud SASE: Issue with Velocloud SD-WAN Gateways

Resolved
Resolved

We have monitored the service for stability and this incident shall now be closed.

Monitoring

We have identified the cause of the issue and have implemented a fix. We will now monitor the service for stability and provide updates as soon as new information becomes available.

Identified

VMware VeloCloud SASE team has determined the cause of the issue and will be upgrading all impacted gateways accordingly. 6.0.0.x VCGs in the following POPs are in scope:

wiii1, llbg1, epwa1, ymml1, sbgr1, vhhh1, vabb1, rjbb1, ehgg1, faor1, lszh1, rksi1, cyyz1, limc1, lfpg1, yssy1, egll1, vidp1.

Identified

We have identified the cause of the issue and working on a fix. We will provide updates as new information becomes available.

Investigating

We continue to investigate this issue. We will provide updates as new information becomes available.

Investigating

The VMware VeloCloud SASE team has become aware of a potential service event and is gathering more information. Customers may notice that their edges are going Up and Down while connecting to Orchestrator (vco301-syd1) resulting in the management plane connectivity issue.

We will provide more updates as new information becomes available.

Began at:

Affected components
  • VMware VeloCloud SASE
    • VMware VeloCloud SD-WAN Gateways
      • North America
        • Toronto
      • Europe
        • Amsterdam
        • London
        • Milan
        • Paris
        • Warsaw
        • Zurich
      • Asia
        • Hong Kong
        • Jakarta
        • Mumbai
        • Osaka
        • Seoul
        • Delhi
        • Tel Aviv
      • Oceania
        • Melbourne
        • Sydney
      • LATAM
        • Sao Paulo
      • Africa
        • Johannesburg