API Service Degradation
Timeline · 1 update
- resolved Jul 24, 2026, 09:36 PM UTC
We have monitored the service for stability and this incident will now be closed.
Broadcom Symantec ZTNA had 35 outages in the last 2 years totaling 1550h 9m of downtime — averaging 1.4 incidents per month.
There were 35 Broadcom Symantec ZTNA outages since April 14, 2026 totaling 1550h 9m of downtime. Each is summarised below — incident details, duration, and resolution information.
We have monitored the service for stability and this incident will now be closed.
We have monitored the service for stability and this incident shall now be closed.
Arcot confirms that the drop in incoming AREQ from card schemes is resolved. If you have any questions regarding this Service Advisory, please contact Broadcom Support by clicking here .
We have monitored the service for stability and this incident shall now be closed.
Arcot confirms that the drop in incoming AREQ from card schemes is resolved. If you have any questions regarding this Service Advisory, please contact Broadcom Support by clicking here .
Arcot observed processing delays for incoming Authentication Request (AReq) from card schemes. Impact: Transactions may have experienced increased latency within Arcot ACS, resulting in directory server timeouts as well as incomplete or unavailable authentications. Consequently, cardholders may have experienced purchase failures. Internal teams engaged quickly and successfully implemented recovery actions to resolve the incident. If you have any questions regarding this Service Advisory, please contact Broadcom Support by clicking here .
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.
We have monitored the service for stability and this incident shall now be closed.
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.
We have monitored the service for stability and this incident shall now be closed.
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.
Arcot confirms that the earlier noticed intermittent rate of MasterCard challenge transaction failures has been resolved and being confirmed by the Mastercard's internal technical teams. Arcot teams confirm that the incident stands resolved. If you have any questions regarding this Service Advisory, please contact Broadcom Support by clicking here .
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.
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.
Performance issues at the Mumbai (GINMU) data center have resolved, and operations have returned to normal. We are closely monitoring the service to ensure continued stability and will provide further updates as new information becomes available.
We have monitored the service for stability and this incident shall now be closed.
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 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 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 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.
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 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.
We have implemented a fix and we are monitoring the situation