Netskope incident

Service Impact to SJC2 Data Center.

Major Resolved View vendor source →

Netskope experienced a major incident on October 24, 2025 affecting SJC2 — San Jose, United States, lasting 6h 52m. The incident has been resolved; the full update timeline is below.

Started
Oct 24, 2025, 05:35 PM UTC
Resolved
Oct 25, 2025, 12:27 AM UTC
Duration
6h 52m
Detected by Pingoru
Oct 24, 2025, 05:35 PM UTC

Affected components

SJC2 — San Jose, United States

Update timeline

  1. investigating Oct 24, 2025, 05:35 PM UTC

    We are currently investigating this issue.

  2. resolved Oct 24, 2025, 05:35 PM UTC

    We are investigating a service impacting incident at the SJC2 datacenter(s) for the following service(s) Management Console WebUI. Full details can be found on the support portal.

  3. resolved Oct 24, 2025, 05:53 PM UTC

    Netskope has identified the potential root cause and is implementing a mitigation strategy

  4. resolved Oct 24, 2025, 06:08 PM UTC

    Netskope has implemented the first mitigation strategy which resulted in some success, however, slowness is still being observed inconsistently. The investigation continues at this time.

  5. resolved Oct 24, 2025, 06:44 PM UTC

    Netskope continues to investigate at this time.

  6. resolved Oct 24, 2025, 07:20 PM UTC

    Netskope is actively investigating the root cause of the inconsistent WebUI performance that is still being observed.

  7. resolved Oct 24, 2025, 08:27 PM UTC

    Netskope is executing a debugging on specific components that are affected by the delays in order to isolate the root cause. The delays appear in an intermittent fashion.

  8. resolved Oct 24, 2025, 09:40 PM UTC

    Netskope has encountered a root cause and its running internal tests to verify and implement a final mitigation strategy.

  9. resolved Oct 24, 2025, 11:35 PM UTC

    Netskope has implemented a mitigation strategy and is currently conducting validation tests.

  10. monitoring Oct 24, 2025, 11:58 PM UTC

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

  11. resolved Oct 25, 2025, 12:27 AM UTC

    The incident has been resolved