VMWare Cloud Services Outage History

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.

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.

We are aware of some customers experiencing issues receiving ClientNet Track and Trace search results via email. As a workaround, these results can still be accessed and downloaded directly through the portal. Our engineering team is currently investigating the issue. Please note that there is no impact to delivery and security scanning of your email traffic, and all other aspects of our services remain functional.

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

Our SMS provider has confirmed that nearly 100% of all traffic to China is currently impacted. While they are actively working to resolve this, they are unable to provide an ETA as they depend on carriers to restore access. Broadcom has been added to an expedited list of high-priority accounts to ensure prompt action to unblock our traffic once access has been restored.

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.

We are aware of an issue where customers accessing the AWS Cost History drilldown reports within the classic CloudHealth experience may encounter slow loading times or drilldowns unavailable. The CloudHealth NX experience is operating normally and is fully unaffected. We strongly encourage customers to use the equivalent capability at apps.cloudhealthtech.com/nx/cost/history while we resolve this issue. Our engineering teams are engaged and are actively investigating the issue. We will provide updates as more information becomes available.

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.

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.

The maintenance is complete and the service is restored. We will now monitor the service for stability and provide updates as soon as new information becomes available.

Issue is resolved and service is stable. We will now monitor the service for stability and provide updates as soon as new information becomes available.

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.

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.

Between 07:55 and 08:45 UTC on August 18, 2026, DEI and PBR services in the London (GGBLO) POP experienced intermittent performance issues. The root cause appears to stem from a platform provider issue. We have escalated the incident to the provider along with initial telemetry logs. Traffic has normalized, and we are actively monitoring the environment.

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.

Between 07:51 and 09:11 UTC on August 20 2026, DEI services in the London (GGBLO) POP experienced intermittent performance issues. Engineers continue to investigate the cause of the issue and will provide updates as soon as new information is available.

Microsoft has incorrectly geolocated our Warsaw, Poland (GPOWA) POP IP addresses as being in Algeria. As a result, customers connecting through the GPOWA POP who enforce Microsoft Conditional Access policies blocking Algerian IP addresses may be unable to access Microsoft services. Impacted customers are requested to adjust conditional access policies to allow users to access the service. We will provide updates as new information becomes available.

Microsoft has confirmed they are actively working to fix the IP geolocation misidentification for our Warsaw, Poland (GPOWA) POP and expect to deploy a resolution by the end of August or sooner. As a reminder, customers using GPOWA POP with Microsoft Conditional Access policies that block Algerian IPs should temporarily update their policies to allow access. We will share further updates as new information becomes available.

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.

Broadcom Engineering is investigating an issue with the Alarm Console and Alarm Summary pages not respecting the state of the noise filter toggle. During this time, if the noise filter toggle is enabled, noisy alarms will not be cleared from the page as expected.

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.

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

Broadcom engineering is investigating an ongoing incident broadly affecting AppNeta services. During this time, users may not be able to log in or browse the system. Additionally, Monitoring Point Telemetry may not be processing or persisting. We are investigating the issue and will post updates here.

Broadcom Engineering has restored service and will continue to monitor the system.