Netskope incident

Service Impact to SV5 Data Center.

Critical Resolved View vendor source →

Netskope experienced a critical incident on October 11, 2025 affecting SV5 — San Jose, United States, lasting 5h 58m. The incident has been resolved; the full update timeline is below.

Started
Oct 11, 2025, 04:00 PM UTC
Resolved
Oct 11, 2025, 09:58 PM UTC
Duration
5h 58m
Detected by Pingoru
Oct 11, 2025, 04:00 PM UTC

Affected components

SV5 — San Jose, United States

Update timeline

  1. investigating Oct 11, 2025, 04:00 PM UTC

    We are currently investigating this issue.

  2. resolved Oct 11, 2025, 04:00 PM UTC

    We are investigating a service impacting incident at the SV5 datacenter(s) for the following service(s) Event Logging, Incident Management System, Management Console WebUI. Full details can be found on the support portal.

  3. resolved Oct 11, 2025, 05:10 PM UTC

    Our investigation of the incident is still ongoing. More details will be provided as soon as available.

  4. resolved Oct 11, 2025, 06:49 PM UTC

    Netskope has identified a faulty switch-to-switch control link within the SV5 management plane. The impacted switch has been disabled, and connectivity is now stabilizing. Several services are beginning to recover. Our network and service teams continue to validate system health and address any remaining issues to ensure full service restoration.

  5. resolved Oct 11, 2025, 07:52 PM UTC

    The Netskope team is confirming that all services have recovered except the following: - SMTP: Remains unavailable from SV5 while further data is collected to confirm full recovery. - DLP/Events: Still experiencing a drain. The team continues to validate overall system health and is actively addressing remaining issues to ensure complete service restoration..

  6. resolved Oct 11, 2025, 08:50 PM UTC

    The Netskope team confirms that all impacted services, including SMTP, have been fully restored, and SkopeIT event backlogs have been cleared. The incident has been mitigated, and monitoring is ongoing to ensure continued stability.

  7. monitoring Oct 11, 2025, 08:58 PM UTC

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

  8. resolved Oct 11, 2025, 09:58 PM UTC

    The incident has been resolved