Broadcom Web Isolation Outage History

Broadcom Web Isolation is up right now

Pingoru has recorded 1 incident for Broadcom Web Isolation: 1 in the last 12 months and 1 in the last 90 days.

Source: status.broadcom.com

1incidents recorded
1last 12 months
1last 90 days
29 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking Broadcom Web Isolation in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 2026129 of 744 (4%)
November 202600 of 123 (0%)

Incidents, newest first

Major October 20, 2026 Web Isolation Degraded Performance in Europe Region 1d 4h Web Isolation, Data Centers - Europe, Middle East & Africa, London, England, UK (europe-west2)

Started Oct 20, 2026, 07:22 AM UTC· resolved Oct 21, 2026, 12:05 PM UTC

  1. investigating Oct 20, 2026, 07:22 AM UTC

    We are aware of an issue where customers having tenant instances on the EU west2 region will be experiencing performance issues when browsing. We have engaged our platform provider, and they are actively investigating the issue. We will provide further updates here as new information becomes available. We will continue to provide updates as more information becomes available.

  2. investigating Oct 20, 2026, 07:46 AM UTC

    The platform provider continues to investigate the ongoing issue. Our team is actively working with them toward a resolution. We will provide further updates here as new information becomes available.

  3. investigating Oct 20, 2026, 10:27 AM UTC

    The platform provider’s investigation is still actively underway. Our teams continue to collaborate closely with them to resolve the issue as quickly as possible. Further updates will be posted here as they become available.

  4. identified Oct 20, 2026, 10:54 AM UTC

    The Platform provider has identified the cause of the issue and are working on a fix. We will provide updates as new information becomes available.

  5. investigating Oct 20, 2026, 01:23 PM UTC

    The Platform provider 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.

  6. resolved Oct 21, 2026, 12:05 PM UTC

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

Read the full incident report →