Netskope incident

Service Impact to SJC1, SV5 Data Center.

Critical Resolved View vendor source →

Netskope experienced a critical incident on September 30, 2026 affecting MEL2 — Melbourne, Australia and SJC1 — San Jose, United States and 1 more component, lasting 14h 48m. The incident has been resolved; the full update timeline is below.

Started
Sep 30, 2026, 01:02 AM UTC
Resolved
Sep 30, 2026, 03:50 PM UTC
Duration
14h 48m
Detected by Pingoru
Sep 30, 2026, 01:02 AM UTC

Affected components

MEL2 — Melbourne, AustraliaSJC1 — San Jose, United StatesSV5 — San Jose, United States

Update timeline

  1. investigating Sep 30, 2026, 01:02 AM UTC

    We are currently investigating this issue.

  2. resolved Sep 30, 2026, 01:02 AM UTC

    We are investigating a service impacting incident at the SJC1, SV5 datacenter(s) for the following service(s) NPA Gateway, Private Access. 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 Sep 30, 2026, 02:00 AM UTC

    Netskope is actively investigating the underlying cause and working on a mitigation. Further updates will be provided as more information becomes available.

  4. resolved Sep 30, 2026, 02:34 AM UTC

    During the ongoing investigation, we have identified that E-Proxy may also be impacted by this issue. Our teams are continuing to investigate and will provide further updates as more information becomes available.

  5. resolved Sep 30, 2026, 03:11 AM UTC

    Netskope is working to reproduce the issue internally to identify the root cause and determine the appropriate mitigation.

  6. resolved Sep 30, 2026, 04:00 AM UTC

    Netskope has successfully reproduced the issue and is working with affected customers to validate the configuration and determine the appropriate next steps. We will share further updates as they become available.

  7. resolved Sep 30, 2026, 05:13 AM UTC

    Netskope has identified a potential cause consistent with our ongoing investigation and has validated the corresponding mitigation with one of the affected customers, who confirmed that updating the configuration resolved the NPA re-authentication issue. Netskope is continuing to work with other affected customers to validate and apply the mitigation, while continuing to investigate the underlying cause and determine a permanent resolution. Further updates will be provided as the investigation progresses.

  8. monitoring Sep 30, 2026, 07:01 AM UTC

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

  9. resolved Sep 30, 2026, 03:50 PM UTC

    The incident has been resolved.