Broadcom Symantec ZTNA Outage History

Broadcom Symantec ZTNA is up right now

Broadcom Symantec ZTNA had 13 outages in the last 2 years totaling 565h 54m of downtime — averaging 0.5 incidents per month.

There were 13 Broadcom Symantec ZTNA outages since April 14, 2026 totaling 565h 54m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.broadcom.com/services/symantec-ztna

Major June 3, 2026

Issues with Alarms Affecting all Application Nodes

Detected by Pingoru
Jun 03, 2026, 05:00 PM UTC
Resolved
Jun 05, 2026, 06:20 AM UTC
Duration
1d 13h
Timeline · 2 updates
  1. investigating Jun 03, 2026, 05:00 PM UTC

    Broadcom Engineering is investigating issues with alarms, including but not limited to: - Errors in the UI when loading certain data in the Alarm Summary, Alarm Console, or Alarm Detail pages - Network Path, Web Path, and Monitoring Point information not populating properly in alarms We are investigating the issue and will post updates here.

  2. investigating Jun 03, 2026, 07:51 PM UTC

    We have implemented a fix and we are monitoring the situation

Read the full incident report →

Major May 29, 2026

Carbon Black - Endpoint Standard - Customers may be experiencing failures with the Cloud Analysis Service

Detected by Pingoru
May 29, 2026, 02:24 PM UTC
Resolved
Jun 01, 2026, 05:48 PM UTC
Duration
3d 3h
Timeline · 2 updates
  1. investigating May 29, 2026, 02:45 PM UTC

    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.

  2. resolved Jun 01, 2026, 05:48 PM UTC

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

Read the full incident report →

Major May 5, 2026

Cloud SWG: DNS Errors for .de Domains

Detected by Pingoru
May 05, 2026, 10:18 PM UTC
Resolved
May 09, 2026, 03:24 PM UTC
Duration
3d 17h
Timeline · 1 update
  1. investigating May 05, 2026, 11:32 PM UTC

    We are seeing DNS failure rate back to normal. Based on our tests, the DNS queries are working fine for the .de hostnames. We will now monitor the service for stability and provide updates as soon as new information becomes available.

Read the full incident report →

Major April 21, 2026

CloudHealth degraded asset ingestion

Detected by Pingoru
Apr 21, 2026, 02:46 PM UTC
Resolved
Apr 23, 2026, 01:39 PM UTC
Duration
1d 22h
Timeline · 2 updates
  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.

Read the full incident report →

Major April 19, 2026

CASB Gatelet unavailable

Detected by Pingoru
Apr 19, 2026, 07:49 PM UTC
Resolved
Apr 20, 2026, 11:55 PM UTC
Duration
1d 4h
Timeline · 1 update
  1. resolved Apr 20, 2026, 11:55 PM UTC

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

Read the full incident report →

Major April 17, 2026

Carbon Black: Event Processing Issue

Detected by Pingoru
Apr 17, 2026, 11:08 AM UTC
Resolved
Apr 17, 2026, 08:35 PM UTC
Duration
9h 27m
Timeline · 1 update
  1. resolved Apr 17, 2026, 08:35 PM UTC

    We have identified the cause of the issue and have implemented a fix. After monitoring the environment for stability, this issue is now resolved.

Read the full incident report →