Netskope incident

Service Impact to multiple Data Centers in Europe region affecting NPA connectivity

Critical Resolved View vendor source →

Netskope experienced a critical incident on June 6, 2025 affecting AMS1 — Amsterdam, Netherlands and BRU1 — Brussels, Belgium and 1 more component, lasting 1d 7h. The incident has been resolved; the full update timeline is below.

Started
Jun 06, 2025, 10:07 AM UTC
Resolved
Jun 07, 2025, 05:45 PM UTC
Duration
1d 7h
Detected by Pingoru
Jun 06, 2025, 10:07 AM UTC

Affected components

AMS1 — Amsterdam, NetherlandsBRU1 — Brussels, BelgiumMIL1 — Milan, ItalyPAR3 — Paris, France

Update timeline

  1. investigating Jun 06, 2025, 10:07 AM UTC

    We are currently investigating this issue.

  2. resolved Jun 06, 2025, 10:07 AM UTC

    We are investigating a service impacting incident datacenter(s) in Europe region for NPA services.

  3. resolved Jun 06, 2025, 11:31 AM UTC

    Netskope has identified a potential issue between the NPA gateway and the Stitcher proxy within multiple POPs. Our team is actively investigating the root cause and working to implement mitigation measures as quickly as possible.

  4. resolved Jun 06, 2025, 12:32 PM UTC

    Netskope has verified that connectivity between POPs (Points of Presence) remains stable. The investigation is now focused on the initial entry point for NPA traffic, particularly the Stitcher Proxy component. All relevant teams are actively collaborating to identify the root cause and implement a timely resolution.

  5. resolved Jun 06, 2025, 01:35 PM UTC

    Netskope teams continue working on a mitigation strategy.

  6. resolved Jun 06, 2025, 02:30 PM UTC

    Netskope teams continue working on a mitigation strategy.

  7. resolved Jun 06, 2025, 03:37 PM UTC

    Netskope is attempting to perform an additional mitigation strategy at this time.

  8. monitoring Jun 06, 2025, 04:32 PM UTC

    A fix has been implemented and we are monitoring the results.

  9. resolved Jun 06, 2025, 06:01 PM UTC

    Root cause investigation continues at this time. There is no active impact.

  10. resolved Jun 06, 2025, 06:55 PM UTC

    Root cause investigation continues.

  11. resolved Jun 06, 2025, 07:29 PM UTC

    Netskope has identified the potential root cause and is working on a resolution strategy

  12. monitoring Jun 06, 2025, 07:47 PM UTC

    The issue has been mitigated, we are continuing to monitor the results.

  13. resolved Jun 06, 2025, 08:07 PM UTC

    Netskope will be performing a change within the BRU1 and PAR1 datacenters to address the root cause identified. The stitcher gateway services are expected to remain out of NewEdge for roughly 24 hours.

  14. resolved Jun 06, 2025, 10:18 PM UTC

    Netskope has scheduled emergency maintenance for BRU1 and PAR1 beginning at 22:30 UTC. The maintenance is scheduled for a 24 hour window

  15. resolved Jun 07, 2025, 01:34 AM UTC

    The change has been completed and Netskope is in the process of reintroducing BRU1 and PAR1 back into the NewEdge network.

  16. resolved Jun 07, 2025, 05:45 PM UTC

    The incident has been resolved