Broadcom CloudSOC CASB incident

CloudHealth degraded asset ingestion

Major Resolved View vendor source →

Broadcom CloudSOC CASB experienced a major incident on April 21, 2026, lasting 3d 1h. The incident has been resolved; the full update timeline is below.

Started
Apr 21, 2026, 02:46 PM UTC
Resolved
Apr 24, 2026, 03:56 PM UTC
Duration
3d 1h
Detected by Pingoru
Apr 21, 2026, 02:46 PM UTC

Update timeline

  1. investigating Apr 21, 2026, 09:59 PM UTC

    We continue to work on a fix. We will provide updates as new information becomes available.

  2. investigating Apr 22, 2026, 04:36 PM UTC

    We are currently working through a data rebuild to ensure asset data is accurate and up to date. While the rebuild is processing as expected, it is taking a bit longer than anticipated to reach 100% completion. Current Status: - Asset Data Availability: You can still access and view asset data; however, please note that the information is currently approximately 36 hours behind (stale) from the initial service interruption for all GCP assets and a limited number of Azure assets. - Next Steps: Once the rebuild of the source data completes, our team will validate and then reset the cached data to clear the stale assets from the system. We appreciate your patience while we ensure your data integrity is maintained. We will provide further updates as new information becomes available.

  3. investigating Apr 23, 2026, 08:34 PM UTC

    Assets collection has resumed into the CloudHealth Platform. Customers can now access the platform to view updated asset data. While many updates are already live, the remaining asset sets will continue to populate over a short period. No further action is required on your part