Forcepoint ONE incident

RBI Service Un-available - North Virginia Region

Critical Resolved View vendor source →

Forcepoint ONE experienced a critical incident on April 3, 2026 affecting N. Virginia (us-east-1) and Oregon (us-west-2) and 1 more component, lasting 9h 47m. The incident has been resolved; the full update timeline is below.

Started
Apr 03, 2026, 11:51 AM UTC
Resolved
Apr 03, 2026, 09:38 PM UTC
Duration
9h 47m
Detected by Pingoru
Apr 03, 2026, 11:51 AM UTC

Affected components

N. Virginia (us-east-1)Oregon (us-west-2)Remote Browser Isolation

Update timeline

  1. investigating Apr 03, 2026, 11:51 AM UTC

    Customer Impact: Some of our RBI customers may have experienced a brief loss of connectivity while browsing from North Virginia (us-east-1) region until services were failed over to an alternate cluster. Description: We are currently experiencing un-availability of RBI services in the North Virginia region. We have rerouted customer traffic to an alternate region to mitigate impact. Teams are troubleshooting the incident, and we will provide further update as we make progress. Next update time: 13:30 UTC

  2. identified Apr 03, 2026, 01:48 PM UTC

    Customer Impact: We have identified a similar degradation impacting Phoenix (us-west-2) region as well. Customers in Northern Virginia (us-east-1) region and Phoenix (us-west-2) will unable to browse via RBI. Description: We have identified a workaround and working on deploying a fix. We will provide further updates as we make progress. Next update time: 14:30 UTC

  3. identified Apr 03, 2026, 01:58 PM UTC

    We are continuing to work on a fix for this issue.

  4. identified Apr 03, 2026, 02:00 PM UTC

    We are continuing to work on a fix for this issue.

  5. monitoring Apr 03, 2026, 04:25 PM UTC

    Customer Impact: We have identified a similar degradation impacting Phoenix (us-west-2) region as well. Customers in Northern Virginia (us-east-1) region and Phoenix (us-west-2) will unable to browse via RBI. Current Status & Next Steps: We have implemented the necessary remediation to restore the health of impacted services in both the regions and traffic has been re-introduced to the Ashburn (us-east-1). We are currently monitoring our environment for stability, and will provide a final update once we have confirmation on the same. Next update time: 17:00 UTC

  6. resolved Apr 03, 2026, 09:38 PM UTC

    This incident has been resolved.