Broadcom Messaging Gateway Outage History

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 have implemented a fix. We will now monitor the service for stability and provide updates as soon as new information becomes available.

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.

Broadcom Engineering is investigating an issue causing events to fail to load on the Network Path Timeline and Web Path Timeline pages.

We have identified the cause of the issue and have implemented a fix. At this time, Network and Web Path events are backlogged within the system. They will continue to show up across the next couple of hours as the backlog is processed.

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 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 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 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.

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.

Broadcom Engineering is investigating an issue with the Alarm Console and Alarm Summary pages not respecting the state of the noise filter toggle. During this time, if the noise filter toggle is enabled, noisy alarms will not be cleared from the page as expected.

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 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 an ongoing incident broadly affecting AppNeta services. During this time, users may not be able to log in or browse the system. Additionally, Monitoring Point Telemetry may not be processing or persisting. We are investigating the issue and will post updates here.

Broadcom Engineering has restored service and will continue to monitor the system.