Netskope incident

Service Impact to BWAN management plane services in US region.

Critical Resolved View vendor source →

Netskope experienced a critical incident on July 14, 2026 affecting SJC1 — San Jose, United States and SJC2 — San Jose, United States and 1 more component, lasting 10h 50m. The incident has been resolved; the full update timeline is below.

Started
Jul 14, 2026, 12:47 PM UTC
Resolved
Jul 14, 2026, 11:37 PM UTC
Duration
10h 50m
Detected by Pingoru
Jul 14, 2026, 12:47 PM UTC

Affected components

SJC1 — San Jose, United StatesSJC2 — San Jose, United StatesSV5 — San Jose, United States

Update timeline

  1. investigating Jul 14, 2026, 12:47 PM UTC

    We are currently investigating this issue.

  2. resolved Jul 14, 2026, 12:47 PM UTC

    We are investigating a service impacting incident at the SCL2, SJC1, SV5 datacenter(s) for the following service(s) Borderless WAN. 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 Jul 14, 2026, 02:41 PM UTC

    Netskope is seeing BWAN services return to normal and we are monitoring.

  4. resolved Jul 14, 2026, 03:39 PM UTC

    BWAN connectivity services remain stable. Netskope is addressing a issue with metrics impacting dashboards within the BWAN management UI.

  5. monitoring Jul 14, 2026, 03:39 PM UTC

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

  6. resolved Jul 14, 2026, 04:11 PM UTC

    Netskope has resolved the metrics service issue. There is an estimated two hours required for the service to process the backlog of messages that was created while in the degraded state. The next update will be provided once the backlog has been completely cleared.

  7. resolved Jul 14, 2026, 06:00 PM UTC

    The backlog of events continues to be processed as expected. The current estimated time to completion is about 1.5 hours.

  8. resolved Jul 14, 2026, 09:02 PM UTC

    Our team have confirmed that the backlog processing has stalled and our investigation is continuing. We have seen no further issues with inline connectivity up to this point.

  9. monitoring Jul 14, 2026, 10:50 PM UTC

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

  10. resolved Jul 14, 2026, 11:37 PM UTC

    The incident has been resolved