Netskope incident
Performance degradation in PAR2 Data Center.
Netskope experienced a critical incident on June 13, 2025 affecting PAR2 — Paris, France, lasting 18d 18h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 13, 2025, 08:15 AM UTC
We are currently investigating this issue.
- resolved Jun 13, 2025, 08:15 AM UTC
We are investigating a performance degradation observed at the PAR2 datacenter for Secure Web Gateway traffic. Full details can be found on the support portal.
- resolved Jun 13, 2025, 10:20 AM UTC
Netskope has identified the root cause currently removing PAR2 from New Edge. Users will connect to alternate POPs.
- monitoring Jun 13, 2025, 10:37 AM UTC
The issue has been mitigated, we are continuing to monitor the results.
- monitoring Jun 13, 2025, 11:37 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 16, 2025, 08:18 AM UTC
Netskope re-enabled the PAR2 connection to NewEdge at 5:30 AM UTC on June 15, 2025, after completing traffic engineering measures and confirmation from the carrier vendor to address a surge in link utilization for one of the network service providers in PAR2. However, following renewed user complaints indicating the issue had resurfaced, Netskope has removed PAR2 from NewEdge as a mitigation step.
- monitoring Jun 16, 2025, 08:25 AM UTC
The issue has been mitigated, we are continuing to monitor the results.
- resolved Jun 16, 2025, 09:33 PM UTC
Netskope identified a configuration issue that prevented traffic in PAR2 from successfully distributing to other data centers automatically. The issue has been fixed. Netskope will re-enable PAR2 within NewEdge on June 17th at 01:00 UTC with limited traffic.
- resolved Jun 17, 2025, 01:30 AM UTC
Netskope has reintroduced the PAR2 POP into the NewEdge Traffic Management system and is actively monitoring to ensure stable performance.
- resolved Jun 17, 2025, 02:15 AM UTC
Netskope continues to closely monitor the PAR2 POP for any signs of instability and will take immediate action if any issues arise.
- resolved Jun 17, 2025, 03:15 AM UTC
Netskope identified a configuration issue that prevented the AFO (Auto-Failout) mechanism from operating properly and transferring traffic from PAR2 to alternative Data Centers. The configuration issue has been addressed, and PAR2 POP has been re-enabled in NewEdge at 5pm PT with limited traffic.
- resolved Jun 17, 2025, 03:45 AM UTC
Netskope identified a configuration issue that had prevented the AFO (Auto-Failout) mechanism from functioning as intended, which delayed the transfer of traffic from the PAR2 POP to alternative Data Centers. This configuration issue has since been addressed, and the PAR2 POP was re-enabled in NewEdge with limited traffic at 01:30 UTC. We apologise for the earlier error in communication and appreciate your understanding.
- resolved Jul 02, 2025, 03:00 AM UTC
The incident has been resolved