Netskope incident

Service Impact to SJC1 Data Center.

Major Resolved View vendor source →

Netskope experienced a major incident on May 27, 2026 affecting SJC1 — San Jose, United States, lasting 10h 41m. The incident has been resolved; the full update timeline is below.

Started
May 27, 2026, 05:19 PM UTC
Resolved
May 28, 2026, 04:00 AM UTC
Duration
10h 41m
Detected by Pingoru
May 27, 2026, 05:19 PM UTC

Affected components

SJC1 — San Jose, United States

Update timeline

  1. investigating May 27, 2026, 05:19 PM UTC

    We are currently investigating this issue.

  2. resolved May 27, 2026, 05:19 PM UTC

    We are investigating a service impacting incident at the SJC1 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 27, 2026, 06:28 PM UTC

    Netskope is currently implementing preliminary mitigation measures to address the issue.

  4. monitoring May 27, 2026, 07:30 PM UTC

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

  5. resolved May 27, 2026, 09:20 PM UTC

    Netskope continues to verify the mitigation strategy.

  6. resolved May 27, 2026, 11:22 PM UTC

    Netskope efforts to validate continued system stability remain ongoing

  7. monitoring May 28, 2026, 12:53 AM UTC

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

  8. resolved May 28, 2026, 02:30 AM UTC

    Netskope has identified that the issue stems from an application configuration update deployed earlier this week. As part of our mitigation efforts, a rollback of these changes is currently in progress. We are validating this rollback internally in a controlled manner before proceeding with a broader deployment. Once the rollback is completed, clients will automatically pull the updated configuration. We will continue to monitor the environment closely as this deploys.

  9. resolved May 28, 2026, 04:00 AM UTC

    The incident has been resolved