Broadcom Edge Secure Web Gateway had 66 outages in the last 2 years totaling 749h 35m of downtime — averaging 2.7 incidents per month.
There were 66 Broadcom Edge Secure Web Gateway outages since April 14, 2026 totaling 749h 35m of downtime. Each is summarised below — incident details, duration, and resolution information.
We have identified the cause of the issue and working on a fix. We will provide 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.
VIP customers may see SMS delivery delays to Verizon Wireless subscribers in the US. Twilio has identified the cause and is working on a fix, with the next update due in about 1 hour. Source: [https://status.twilio.com/incidents/yn67bt4txhw7](https://status.twilio.com/incidents/yn67bt4txhw7)
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 experiencing issues with Login to the US Region Quarantine Portal. Our engineering teams are engaged and 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 monitored the service for stability and this incident shall now be closed.
Please be advised that Broadcom Product Licensing is currently unavailable impacting all products. Internal Teams are actively investigating and are working towards a resolution.
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 monitored the service for stability and this incident shall now be closed.
We are currently experiencing delays in processing events in the US region. We are actively working towards fixing the issue.
We have identified the cause of the issue and working on a fix. We will provide 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.
We have monitored the service for stability and this incident shall now be closed.
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 monitored the service for stability and this incident shall now be closed.
We are aware of an issue with US Prod Stack 004, where users may experience slowness when attempting to connect to Clarity services. More information will be provided as it 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 monitored the service for stability and this incident shall now be closed.
We are currently aware that some Cloud SWG customers are experiencing errors when attempting to download logs using Sync API. The issue began on October 3, 2026, around 00:00 UTC. We are currently investigating the cause of this issue and will provide updates as new information becomes available. All other aspects of the service is functioning as normal.
We have identified the cause of the issue and working on a fix. We will provide 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.
We have monitored the service for stability and this incident shall now be closed.
Arcot monitoring has detected a drop in incoming AREQ from Visa Directory Server. This is also impacting the Challenge transactions processing due to increased directory server timeouts in the RREQ flow. Arcot is aware of an ongoing service disruption at Visa end. Our internal teams are engaged with Visa at this point and Visa team is actively investigating this issue and also working on service recovery on priority. Impact: Transactions may be experiencing increased latency resulting in increased directory server timeouts and Incomplete, or Unavailable Authentications. The cardholders may experience failures in attempting to make purchases. We shall get back to you with the next update 05:20 HRS GMT.
Arcot confirms that the drop in incoming AREQ and the Challenge transactions processing issue with Visa Directory Server is resolved. The Visa team implemented the mitigation actions successfully to restore the services. With this update, the incident stands resolved. If you have any questions regarding this Service Advisory, please contact Broadcom Support by clicking here .
The mitigation has been deployed to the impacted region, and we are currently monitoring the service to ensure ongoing stability. Further updates will be provided as additional information becomes available.
We have monitored the service for stability and this incident shall now be closed.
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 monitored the service for stability and this incident shall now be closed.
Arcot monitoring detected a drop in incoming AREQ traffic. Following an internal investigation, we traced the root cause to connectivity issues on the Cardinal 3DS server side. Our monitoring indicates that traffic routing has normalized and services appear to be operating as expected. If you have any questions regarding this Service Advisory, please contact Broadcom Support by clicking here .
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 monitored the service for stability and this incident shall now be closed.
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 monitored the service for stability and this incident shall now be closed.
We have monitored the service for stability and this incident shall now be closed.
We have identified the cause of the issue and working on a fix. We will provide 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.
We have monitored the service for stability and this incident shall now be closed.
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 monitored the service for stability and this incident shall now be closed.
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 monitored the service for stability and this incident shall now be closed.
We have monitored the service for stability and this incident shall now be closed.
We have monitored the service for stability and this incident shall now be closed.
We have monitored the service for stability and this incident shall now be closed.
We have monitored the service for stability and this incident shall now be closed.
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.