Forcepoint ONE incident

Sao Paulo (Cluster P) Performance Degraded

Minor Resolved View vendor source →

Forcepoint ONE experienced a minor incident on March 5, 2025 affecting Web Security Cloud and São Paulo (P), lasting 4h 1m. The incident has been resolved; the full update timeline is below.

Started
Mar 05, 2025, 08:32 PM UTC
Resolved
Mar 06, 2025, 12:34 AM UTC
Duration
4h 1m
Detected by Pingoru
Mar 05, 2025, 08:32 PM UTC

Affected components

Web Security CloudSão Paulo (P)

Update timeline

  1. investigating Mar 05, 2025, 08:32 PM UTC

    Customer Impact: Web Security Cloud customers may have observed an intermittent loss of connectivity to the web. Description: We are currently experiencing a network reachability issue in Sao Paolo which is causing intermittent loss of connectivity to services hosted in Sao Paolo. We have re-routed traffic to an alternate data center to ensure continuity of services for customers while we investigate the problem. Next update time: 21:30 UTC

  2. identified Mar 05, 2025, 09:40 PM UTC

    Customer Impact: Web Security Cloud customers may observe a loss of connectivity when connecting to our Sao Paulo (Cluster P) datacenter. Customers with a redundant IPSec/GRE connection would have automatically connected to an alternate datacenter and should not be impacted by this incident. Current Status & Next Steps: The team has identified the component with the issue and continues to actively work towards a resolution. Next Update: 22:30 UTC

  3. monitoring Mar 05, 2025, 11:31 PM UTC

    Customer Impact: Web Security Cloud customers may have observed a brief loss of connectivity when connecting to our Sao Paulo (Cluster P) datacenter. Customers with a redundant IPSec/GRE connection would have automatically connected to an alternate datacenter and should not be impacted by this incident. Current Status & Next Steps: We have implemented the necessary remediation to restore the health of impacted services and traffic has been re-introduced to the Sao Paulo Cluster. We are currently monitoring our environment for stability and will provide a final update once we have confirmation on the same.

  4. resolved Mar 06, 2025, 12:34 AM UTC

    This incident has been resolved.