Netskope incident

Service Impact to ZUR2 Data Center.

Major Resolved View vendor source →

Netskope experienced a major incident on May 19, 2026 affecting AM2 — Amsterdam, Netherlands and MEL2 — Melbourne, Australia and 1 more component, lasting 8h 31m. The incident has been resolved; the full update timeline is below.

Started
May 19, 2026, 10:55 AM UTC
Resolved
May 19, 2026, 07:26 PM UTC
Duration
8h 31m
Detected by Pingoru
May 19, 2026, 10:55 AM UTC

Affected components

AM2 — Amsterdam, NetherlandsMEL2 — Melbourne, AustraliaSJC1 — San Jose, United StatesSV5 — San Jose, United StatesZUR2 — Zurich, Switzerland

Update timeline

  1. investigating May 19, 2026, 10:55 AM UTC

    We are currently investigating this issue.

  2. resolved May 19, 2026, 10:55 AM UTC

    We are investigating a service impacting incident at the ZUR2 datacenter(s) for the following service(s) Core Services. Additional details on the scope of impact are currently being assessed and will be provided within the support portal once an article is provided.

  3. resolved May 19, 2026, 12:01 PM UTC

    Netskope is actively investigating to isolate the root cause of this issue.

  4. resolved May 19, 2026, 01:05 PM UTC

    Netskope continues to investigate to identify a root cause.

  5. resolved May 19, 2026, 02:24 PM UTC

    Netskope continues to investigate to identify a root cause.

  6. resolved May 19, 2026, 03:37 PM UTC

    Netskope continues to actively investigate the root cause.

  7. resolved May 19, 2026, 04:34 PM UTC

    Netskope continues to investigate to identify a root cause.

  8. monitoring May 19, 2026, 05:21 PM UTC

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

  9. monitoring May 19, 2026, 06:08 PM UTC

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

  10. resolved May 19, 2026, 06:13 PM UTC

    The incident has been resolved