Forcepoint ONE experienced a minor incident on January 31, 2026 affecting San Jose (G) and Dallas (O), lasting 2h 54m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jan 31, 2026, 07:09 PM UTC
Customer Impact: Some web security cloud customers may be experiencing connectivity issue via Cluster-O and Cluster-G. Description: We are currently investigating reports of degraded performance in these datacenters. We are investigating the incident and will provide an update as we make progress.
- investigating Jan 31, 2026, 07:42 PM UTC
Customer Impact: The customer impact has been mitigated as Web Security service traffic has failed over to redundant data center. The customers connecting via vpop may not have seen any problem connecting to services. Description: Forcepoint is continuing to investigate reports of degraded performance. We are investigating the incident and will provide an update as we make progress.
- identified Jan 31, 2026, 07:59 PM UTC
Customer Impact: Forcepoint has identified the problem with Cluster-O and the customer impact has been mitigated via failing over traffic to redundant data center. The customers connecting via vpop may not have seen any problem connecting to services. Description: Forcepoint is continuing to work for resolution and recovery in Cluster-O.
- monitoring Jan 31, 2026, 08:30 PM UTC
Customer Impact: Some web security cloud customers may have experienced issue while connecting via Cluster-O Current Status & Next Steps: We have implemented the necessary remediation to restore the health of impacted services and traffic has been automatically re-introduced to Cluster-O We are currently monitoring our environment for stability, and will provide a final update once we have confirmation on the same.
- resolved Jan 31, 2026, 10:03 PM UTC
This incident has been resolved.