VMWare Cloud Services Outage History

As of 07:23 UTC, the backlog has cleared. We will now monitor the service for stability and provide updates as soon as new information becomes available.

A small subset of customers may have been experiencing issues with delayed Event Processing. The issue has been identified and remediation actions implemented. Services are currently being monitored to ensure any backlog of alerts and events are processed.

AWS Customers logging into Cloudhealth will notice an inflated cost for the month of July 2026. This is caused by an upstream issue with the AWS Billing and Cost Management Console. The CloudHealth engineering team is closely monitoring the situation as AWS works toward a resolution.

AWS has reported that backfills are progressing but are taking longer than anticipated. Their new ETA for all customers to have corrected billing data is 12:00 AM PDT (07:00 UTC) July 19. CloudHealth will reprocess all impacted customers at that time and expects all customers to have corrected cost data in reports by 12:00 AM PDT (07:00 UTC) July 20 or sooner. We will provide further updates as necessary and/or when data has been updated.

AWS has confirmed that bills have been corrected for the majority of their customers by 6:00 AM PDT (13:00 UTC) July 18. CloudHealth began reprocessing bills and reports for impacted customers at that time and have confirmed that costs have been corrected once the report generation cycle completes. We expect costs to be fully refreshed and corrected for all customers by 6:00 PM PDT (01:00 UTC) July 19 or sooner.

Portal login issue is now resolved. We are closely monitoring the service to ensure continued stability and will provide further updates as new information becomes available.

At this point, Mastercard has confirmed that their internal investigation remains actively in progress as their technical teams work toward a resolution. Arcot continues to stay closely engaged with Mastercard, monitoring the situation and tracking their recovery efforts. Impact: Frictionless transactions (which do not require a challenge step) are entirely unaffected. However, cardholders may experience intermittent failures if a challenge step is triggered.

Our SMS provider has successfully deployed a fix. We have entered a stability monitoring period to ensure services remain fully operational, and we will provide further updates as new information becomes available.

All services have successfully returned to their pre-incident state. We have entered a stability monitoring period to ensure performance remains optimal, and we will provide another update as soon as new information becomes available.

We have engaged our platform provider, and they are actively investigating the issue. We will provide further updates here as new information becomes available.

The platform provider continues to investigate the ongoing issue. Our team is actively working with them toward a resolution. We will provide further updates here 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 currently investigating an issue affecting the Vulnerability Assessment Service in the US region. During this window, customers may experience errors or degradation when attempting to use the vulnerability assessment features within the user interface (UI). Please be assured that backend data collection is still functioning normally, though processing and updates may be delayed. Our engineering team has successfully identified the root cause and is actively working on a resolution. We appreciate your patience and will provide further updates 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.

We 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 that CloudSOC customers using the Enterprise Console are currently experiencing issues accessing the DLP portion of the service. We have identified the cause of the issue and are actively working on a fix. We will provide further updates as new information becomes available. Please note that no other Enterprise Cloud Console Platform is affected and the protection services provided by endpoints continues to protect devices it is installed on.

We 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 an issue with alarm decoration across all NIS nodes. We are investigating the issue and will post updates here. Thanks, Broadcom Engineering.

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.

Our Voice provider has 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 continue to work on a fix. We will provide updates 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.