Resolved
Resolved

The VMware SASE team has not encountered additional issues in monitoring and has implemented a fix to resolve this incident. Accordingly, this is the final notification for this incident which will now be closed.

Further updates will be provided 19th of June or earlier if available.

Start Time: Jun 1, 2023 10:21 PM UTC End Time: Jun 17, 2023 14:07 PM UTC

Current Impact: None (issue resolved)

Update

The VMware SASE team became aware of service event, incident started impacting more customers & partners on 1st of June and escalated internally. Root cause has been isolated to the memory consumption of the config parsing engine. Memory configuration change has been identified and tested. This configuration change is currently in progress of being implemented across all relevant components.

Further updates will be provided 19th of June or earlier if available.

Start Time: Jun 1, 2023 10:21 PM UTC End Time: To be determined

Current Impact: Users can access CWS, however some web requests may intermittently fail with 503 error.

Update

The VMware SASE team became aware of service event, incident started impacting more customers & partners on 1st of June and escalated internally. Root cause has been isolated to the config parsing engine. The VMware SASE team is in progress of validating and testing fix created.

Further updates will be provided in the next 24 hours or earlier if available.

Start Time: Jun 1, 2023 10:21 PM UTC End Time: To be determined

Current Impact: Users can access CWS, however some web requests may intermittently fail with 503 error.

Update

The VMware SASE team became aware of service event, incident started impacting more customers & partners on 1st of June and escalated internally. Root cause has been isolated to the config parsing engine. The VMware SASE team continues to actively work towards a fix.

Further updates will be provided in the next 24 hours or earlier if available.

Start Time: Jun 1, 2023 10:21 PM UTC End Time: To be determined

Current Impact: Users can access CWS, however some web requests may intermittently fail with 503 error.

Identified

The VMware SASE team became aware of service event, incident started impacting more customers & partners on 1st of June and escalated internally. Root cause isolation is in progress, the VMWare SASE team continues to actively work towards a path for resolution.

Further updates will be provided in the next 24 hours or earlier if available.

Start Time: Jun 1, 2023 10:21 PM UTC End Time: To be determined

Current Impact: Users can access CWS, however some web requests may intermittently fail with 503 error.

Began at:

Affected components
  • VMware SASE
    • Cloud Web Security
      • North America
        • Ashburn
        • Atlanta
        • Chicago
        • Dallas
        • Denver
        • Los Angeles
        • Miami
        • New York
        • San Jose
        • Seattle
        • Toronto
        • Vancouver
      • Europe
        • Amsterdam
        • Dublin
        • Frankfurt
        • London
        • Milan
        • Paris
      • Asia
        • Hong Kong
        • Osaka
        • Singapore
        • Tokyo
      • Oceania
        • Melbourne
        • Sydney
      • LATAM
        • Sao Paulo