Netskope incident

Service Impact to SJC1 Data Center.

Critical Resolved View vendor source →
Started
Apr 28, 2026, 03:20 PM UTC
Resolved
Apr 30, 2026, 12:55 AM UTC
Duration
1d 9h
Detected by Pingoru
Apr 28, 2026, 03:20 PM UTC

Affected components

SJC1 — San Jose, United States

Update timeline

  1. investigating Apr 28, 2026, 03:20 PM UTC

    We are currently investigating this issue.

  2. resolved Apr 28, 2026, 03:20 PM UTC

    We are investigating a service impacting incident at the SJC1 datacenter(s) for the following service(s) Incident Management System. 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 Apr 28, 2026, 04:00 PM UTC

    Netskope continues to investigate for a potential root cause. Details will continue to be provided within the support portal.

  4. resolved Apr 28, 2026, 05:09 PM UTC

    Netskope continues to investigate at this time. A root cause has not yet been identified.

  5. resolved Apr 28, 2026, 06:00 PM UTC

    Netskope is implementing a potential mitigation strategy. Updates will continue to be provided as they become available.

  6. resolved Apr 28, 2026, 06:23 PM UTC

    Netskope has completed executing the mitigation strategy on one of the impacted service hosts. Positive results have been observed. The strategy is now being implemented across all other hosts. Updates will be provided as they become available. Estimated completion time is currently 1 to 1.5 hours.

  7. resolved Apr 28, 2026, 06:55 PM UTC

    The errors have reappeared on the first host where the first mitigation attempt was performed. Root cause investigation remains underway at this time.

  8. resolved Apr 28, 2026, 07:59 PM UTC

    Netskope continues the root cause investigation at this time. Updates will be provided as they become available.

  9. resolved Apr 28, 2026, 08:54 PM UTC

    Netskope continues to investigate for a root cause.

  10. resolved Apr 28, 2026, 10:05 PM UTC

    Netskope continues to analyze the underlying cause of this incident.

  11. monitoring Apr 28, 2026, 11:09 PM UTC

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

  12. resolved Apr 29, 2026, 12:28 AM UTC

    Netskope continues to investigate the origin of this incident, we have confirmation that there are no more errors reported.

  13. resolved Apr 29, 2026, 02:49 AM UTC

    Netskope continues to monitor system stability and investigate the root cause. All services are currently functioning within normal parameters with no new errors reported. We will provide a final update once the monitoring period is complete.

  14. resolved Apr 29, 2026, 03:06 PM UTC

    Netskope has observed no recurrence during the monitoring period, and system performance remains stable. Monitoring will continue through the completion of NAM business hours, after which a final update will be shared.

  15. resolved Apr 29, 2026, 06:00 PM UTC

    Netskope monitoring reports that system performance continues to be stable and all services are currently functioning within normal parameters, active monitoring remains in place

  16. resolved Apr 30, 2026, 12:55 AM UTC

    The incident has been resolved

  17. resolved Apr 30, 2026, 12:55 AM UTC

    Netskope has formalized a confident hypothesis on root cause. The incident is being moved to a resolved status. Further details can be found within the support portal.

Looking to track Netskope downtime and outages?

Pingoru polls Netskope's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Netskope reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Netskope alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Netskope for free

5 free monitors · No credit card required