Netskope Outage History

Netskope is up right now

Pingoru has recorded 170 incidents for Netskope: 162 in the last 12 months and 47 in the last 90 days.

Source: trust.netskope.com

170incidents recorded
162last 12 months
47last 90 days
11 hourstypical duration
Incidents per month
01020AprMayJunJulAugSepOct12
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct24%
Pingoru began tracking Netskope in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202611191 of 720 (27%)
May 20261238 of 744 (5%)
June 202616134 of 720 (19%)
July 202611173 of 744 (23%)
August 202620172 of 744 (23%)
September 202614275 of 720 (38%)
October 202612142 of 590 (24%)

Incidents, newest first

Major April 30, 2026 Service Impact to BOM1 Data Center. 1h 30m BOM1 — Mumbai, India

Started Apr 30, 2026, 08:45 AM UTC· resolved Apr 30, 2026, 10:15 AM UTC

  1. investigating Apr 30, 2026, 08:45 AM UTC

    We are currently investigating this issue.

  2. resolved Apr 30, 2026, 08:45 AM UTC

    We are investigating a service impacting incident at the BOM1 datacenter(s) for the following service(s) NPA Gateway, NPA Stitcher, Private Access. 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 30, 2026, 09:31 AM UTC

    Netskope has identified the root cause and is performing optimisations on the Load Balancer component to restore optimal performance. These changes will be performed for the next hour starting 9:30 UTC. During this window, the publishers connected to BOM1 point of presence might experience a disconnection.

  4. resolved Apr 30, 2026, 10:14 AM UTC

    All services have auto recovered. To prevent any further disruption, the optimisations will be performed off business hours. This incident is now resolved.

  5. resolved Apr 30, 2026, 10:15 AM UTC

    The incident has been resolved

  6. resolved Apr 30, 2026, 10:15 AM UTC

    The incident has been resolved.

Read the full incident report →

Major April 7, 2026 Service Impact to MEL2 Data Center. 34m MEL2 — Melbourne, Australia

Started Apr 07, 2026, 02:06 AM UTC· resolved Apr 07, 2026, 02:40 AM UTC

  1. investigating Apr 07, 2026, 02:06 AM UTC

    We are currently investigating this issue.

  2. resolved Apr 07, 2026, 02:06 AM UTC

    We are investigating a service impacting incident at the MEL2 datacenter(s) for the following service(s) Advanced Analytics, DEM. 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 07, 2026, 02:40 AM UTC

    The incident has been resolved

  4. resolved Apr 07, 2026, 02:40 AM UTC

    The incident has been resolved.

Read the full incident report →

Major April 2, 2026 Service Impact to all Management Planes(s). 22h 32m

Started Apr 02, 2026, 12:16 PM UTC· resolved Apr 03, 2026, 10:48 AM UTC

  1. investigating Apr 02, 2026, 12:16 PM UTC

    We are currently investigating this issue.

  2. resolved Apr 02, 2026, 12:16 PM UTC

    We are investigating a service impacting incident at the all Management Plane(s) for the following service(s) Netskope Client. 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 02, 2026, 12:28 PM UTC

    Netskope continues to investigate the issue.

  4. resolved Apr 02, 2026, 01:51 PM UTC

    Netskope continues to actively investigate the issue and is working to identify the root cause.

  5. resolved Apr 02, 2026, 03:16 PM UTC

    Netskope has identified the root cause as an endpoint shutdown occurring during the upgrade process, which can result in the client becoming uninstalled or entering a non-functional state. As a mitigation, a clean installation of the Netskope client is recommended to restore normal functionality.

  6. monitoring Apr 02, 2026, 03:27 PM UTC

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

  7. resolved Apr 03, 2026, 12:57 AM UTC

    Netskope continues to monitor for any future reoccurrences and is waiting for confirmation that the recommendation resolves the issue.

  8. resolved Apr 03, 2026, 10:48 AM UTC

    The incident has been resolved

  9. resolved Apr 03, 2026, 10:48 AM UTC

    The incident has been resolved.

Read the full incident report →

Critical March 30, 2026 Service Impact to ICN1 Data Center. 11h 10m ICN1 — Incheon, South Korea

Started Mar 30, 2026, 04:00 AM UTC· resolved Mar 30, 2026, 03:10 PM UTC

  1. investigating Mar 30, 2026, 04:00 AM UTC

    We are currently investigating this issue.

  2. resolved Mar 30, 2026, 04:00 AM UTC

    We are investigating a service impacting incident at the ICN1 datacenter(s) for the following service(s) Secure Web Gateway. 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. monitoring Mar 30, 2026, 04:26 AM UTC

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

  4. resolved Mar 30, 2026, 05:49 AM UTC

    Netskope has identified the root cause of the issue and is currently developing a comprehensive remediation plan to ensure a full resolution.

  5. resolved Mar 30, 2026, 06:46 AM UTC

    Netskope has engaged the relevant transit partners for ICN1 to expedite a resolution. We are closely monitoring the restoration efforts.

  6. resolved Mar 30, 2026, 07:53 AM UTC

    We continue to work toward a resolution in coordination with our transit partners. Our next scheduled update will be shared at 12:00 PM UTC.

  7. resolved Mar 30, 2026, 12:00 PM UTC

    Netskope is continuing to work toward resolving the issue in coordination with its transit partners. The next update will be provided at 18:00 UTC.

  8. resolved Mar 30, 2026, 03:10 PM UTC

    The incident has been resolved

  9. resolved Mar 30, 2026, 03:10 PM UTC

    The incident has been resolved.

  10. resolved Mar 30, 2026, 03:10 PM UTC

    Netskope has confirmed that the issue has been resolved by the carrier partner. Following validation, the PoP ICN1 has been successfully reinstated into the NewEdge traffic management system.

Read the full incident report →

Major March 27, 2026 Service Impact to SWG Service. 3h 4m

Started Mar 27, 2026, 05:03 AM UTC· resolved Mar 27, 2026, 08:07 AM UTC

  1. investigating Mar 27, 2026, 05:03 AM UTC

    We are currently investigating this issue.

  2. resolved Mar 27, 2026, 05:03 AM UTC

    We are investigating a service impacting incident for the following service(s) Secure Web Gateway. 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 Mar 27, 2026, 06:53 AM UTC

    Netskope has identified the root cause of the issue and currently devising a mitigation strategy to mitigate the impact.

  4. resolved Mar 27, 2026, 07:40 AM UTC

    Mitigation steps have been successfully implemented on the MEL2 MP, and we have verified that the issue is resolved at that location. Netskope is now proceeding with these steps across all remaining MPs. A follow-up update will be provided at 8:45 AM UTC.

  5. resolved Mar 27, 2026, 08:07 AM UTC

    The incident has been resolved

  6. resolved Mar 27, 2026, 08:07 AM UTC

    The incident has been resolved.

  7. resolved Mar 27, 2026, 08:07 AM UTC

    Mitigation steps have been successfully completed across all MPs. Final verification confirms that the issue is fully resolved and all systems are performing as expected. This incident is now resolved.

Read the full incident report →

Critical March 24, 2026 Service Impact to FRA2, SJC2, ZUR2, DFW3, SIN2 Data Center. 2h 43m DFW3 — Dallas, United States, FRA2 — Frankfurt, Germany, SIN2 — Singapore, Singapore, SJC2 — San Jose, United States and 1 more

Started Mar 24, 2026, 04:17 AM UTC· resolved Mar 24, 2026, 07:00 AM UTC

  1. investigating Mar 24, 2026, 04:17 AM UTC

    We are currently investigating this issue.

  2. resolved Mar 24, 2026, 04:17 AM UTC

    We are investigating a service impacting incident at the FRA2, SJC2, DFW3, ZUR2, SIN2 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. monitoring Mar 24, 2026, 04:29 AM UTC

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

  4. monitoring Mar 24, 2026, 05:33 AM UTC

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

  5. resolved Mar 24, 2026, 06:47 AM UTC

    During the ongoing monitoring, we identified that the issue was not limited to FRA2 and also impacted San Jose, California, USA (SJC2), Dallas, Texas, USA (DFW3), Zurich, Switzerland (ZUR2) and Singapore (SIN2). Our teams are actively engaged in implementing the fix across the other impacted management planes to ensure full service stability.

  6. resolved Mar 24, 2026, 07:00 AM UTC

    The incident has been resolved

  7. resolved Mar 24, 2026, 07:00 AM UTC

    The incident has been resolved.

Read the full incident report →

Major March 11, 2026 Users connected to CPT1 Unable to Access Tenant UI Hosted in ZUR2 MP 3h 6m ZUR2 — Zurich, Switzerland

Started Mar 11, 2026, 10:54 AM UTC· resolved Mar 11, 2026, 02:00 PM UTC

  1. investigating Mar 11, 2026, 10:54 AM UTC

    We are currently investigating this issue.

  2. resolved Mar 11, 2026, 10:54 AM UTC

    We are investigating a service impacting incident at the ZUR2 datacenter(s) for the following service(s) Management Console WebUI. 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. monitoring Mar 11, 2026, 11:58 AM UTC

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

  4. resolved Mar 11, 2026, 02:00 PM UTC

    The incident has been resolved

  5. resolved Mar 11, 2026, 02:00 PM UTC

    The incident has been resolved.

Read the full incident report →

Critical March 6, 2026 Service Impact to IAD3 Data Center. 4h 56m

Started Mar 06, 2026, 08:14 PM UTC· resolved Mar 07, 2026, 01:10 AM UTC

  1. investigating Mar 06, 2026, 08:14 PM UTC

    We are currently investigating this issue.

  2. resolved Mar 06, 2026, 08:14 PM UTC

    We are investigating a service impacting incident at the IAD3 datacenter(s) for the following service(s) Management Console WebUI. 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. monitoring Mar 06, 2026, 09:42 PM UTC

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

  4. monitoring Mar 06, 2026, 11:35 PM UTC

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

  5. resolved Mar 07, 2026, 01:10 AM UTC

    The incident has been resolved

  6. resolved Mar 07, 2026, 01:10 AM UTC

    The incident has been resolved.

Read the full incident report →

Critical February 28, 2026 Service Impact to BOM1, BOM2, CCU1, DEL1, DEL2, MAA1 Data Center. 1h 24m BOM1 — Mumbai, India, BOM2 — Mumbai, India, CCU1 — Kolkata, India, DEL1 — Delhi, India and 2 more

Started Feb 28, 2026, 11:36 AM UTC· resolved Feb 28, 2026, 01:00 PM UTC

  1. investigating Feb 28, 2026, 11:36 AM UTC

    We are currently investigating this issue.

  2. resolved Feb 28, 2026, 11:36 AM UTC

    We are investigating a service impacting incident at the BOM1, BOM2, CCU1, DEL1, DEL2, MAA1 datacenter(s) for the following service(s) NPA Gateway, NPA Stitcher. 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 Feb 28, 2026, 01:00 PM UTC

    The incident has been resolved

  4. resolved Feb 28, 2026, 01:00 PM UTC

    The incident has been resolved.

Read the full incident report →

Critical February 21, 2026 Service Impact to YYZ2 Data Center. 4m

Started Feb 21, 2026, 11:22 PM UTC· resolved Feb 21, 2026, 11:26 PM UTC

  1. investigating Feb 21, 2026, 11:22 PM UTC

    We are currently investigating this issue.

  2. resolved Feb 21, 2026, 11:22 PM UTC

    We are investigating a service impacting incident at the YYZ2 datacenter(s) for the following service(s) All Services, Advanced Analytics, CASB API Data Protection, Core Services, Event Logging, Incident Management System, Management Console WebUI. 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 Feb 21, 2026, 11:26 PM UTC

    The incident has been resolved

  4. resolved Feb 21, 2026, 11:26 PM UTC

    The incident has been resolved.

Read the full incident report →

Critical February 20, 2026 Missing malware events and alerts within SkopeIT 16h 41m

Started Feb 20, 2026, 02:04 PM UTC· resolved Feb 21, 2026, 06:45 AM UTC

  1. investigating Feb 20, 2026, 02:04 PM UTC

    We are currently investigating this issue.

  2. resolved Feb 20, 2026, 02:04 PM UTC

    Netskope has received reports from customers that are missing recent malware scan events in SkopeIT.

  3. resolved Feb 20, 2026, 03:20 PM UTC

    Netskope continues to investigate this issue.

  4. resolved Feb 20, 2026, 04:26 PM UTC

    Netskope continues to investigate the issue.

  5. resolved Feb 20, 2026, 09:01 PM UTC

    Netskope is in the process of implementing a fix. More details can be found in the support portal.

  6. resolved Feb 20, 2026, 09:38 PM UTC

    Netskope has begun deploying a fix. More details can be found in the support portal.

  7. resolved Feb 21, 2026, 06:42 AM UTC

    This incident has been resolved. More details can be found in the support portal.

  8. resolved Feb 21, 2026, 06:45 AM UTC

    The incident has been resolved

  9. resolved Feb 21, 2026, 06:45 AM UTC

    The incident has been resolved.

  10. resolved Feb 27, 2026, 11:01 PM UTC

    Netskope has successfully rolled back the changes that caused the recent impact. Customers no longer need to use the temporary workaround.

Read the full incident report →

Major January 23, 2026 Service Impact to BOM2 Data Center. 1d 2h BOM2 — Mumbai, India

Started Jan 23, 2026, 05:37 AM UTC· resolved Jan 24, 2026, 08:00 AM UTC

  1. investigating Jan 23, 2026, 05:37 AM UTC

    We are currently investigating this issue.

  2. resolved Jan 23, 2026, 05:37 AM UTC

    We are investigating a service impacting incident at the BOM2 datacenter(s) for the following service(s) Cloud Access Security Broker, Netskope Client, Secure Web Gateway. 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 Jan 24, 2026, 08:00 AM UTC

    The incident has been resolved

  4. resolved Jan 24, 2026, 08:00 AM UTC

    The incident has been resolved.

Read the full incident report →

Critical January 21, 2026 Service Impact to LON2, MAN1 Data Center. 3h 38m LON2 — London, United Kingdom, MAN1 — Manchester, United Kingdom

Started Jan 21, 2026, 09:52 AM UTC· resolved Jan 21, 2026, 01:30 PM UTC

  1. investigating Jan 21, 2026, 09:52 AM UTC

    We are currently investigating this issue.

  2. resolved Jan 21, 2026, 09:52 AM UTC

    We are investigating a service impacting incident at the LON2, MAN1 datacenter(s) for the following service(s) NPA Gateway, Secure Web Gateway. 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 Jan 21, 2026, 11:01 AM UTC

    Netskope continues to investigate the issue.

  4. resolved Jan 21, 2026, 11:45 AM UTC

    Netskope identified an issue involving one of its service providers in the EU region. The issue was automatically mitigated at 11:10 UTC with no manual intervention required from Netskope. We are actively working with the service provider to complete a detailed root cause analysis and will share further updates as they become available.

  5. monitoring Jan 21, 2026, 11:46 AM UTC

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

  6. resolved Jan 21, 2026, 01:30 PM UTC

    The incident has been resolved

  7. resolved Jan 21, 2026, 01:30 PM UTC

    The incident has been resolved.

Read the full incident report →

Major January 19, 2026 Service Impact to AKL1 Data Center. 4h 41m AKL1 — Auckland, New Zealand

Started Jan 19, 2026, 11:19 PM UTC· resolved Jan 20, 2026, 04:00 AM UTC

  1. investigating Jan 19, 2026, 11:19 PM UTC

    We are currently investigating this issue.

  2. resolved Jan 19, 2026, 11:19 PM UTC

    We are investigating a service impacting incident at the AKL1 datacenter(s) for the following service(s) Secure Web Gateway. 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 Jan 19, 2026, 11:45 PM UTC

    AKL1 removed from NewEdge to allow customers to connect to alternative nearby data centers while the investigation continues

  4. monitoring Jan 20, 2026, 01:07 AM UTC

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

  5. monitoring Jan 20, 2026, 01:40 AM UTC

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

  6. resolved Jan 20, 2026, 04:00 AM UTC

    The incident has been resolved

  7. resolved Jan 20, 2026, 04:00 AM UTC

    The incident has been resolved.

Read the full incident report →

Major December 17, 2025 Netskope Chromebook Extension Issue 2h 25m

Started Dec 17, 2025, 07:19 PM UTC· resolved Dec 17, 2025, 09:44 PM UTC

  1. investigating Dec 17, 2025, 07:19 PM UTC

    We are currently investigating this issue.

  2. resolved Dec 17, 2025, 07:19 PM UTC

    Customers that upgraded the Netskope Chromebook Extension to v132.1.0.0 may encounter intermittent website accessibility issues.

  3. resolved Dec 17, 2025, 07:27 PM UTC

    Netskope has provided mitigation instructions via the linked support portal article. This incident will remain open for a period of time before being set to resolved.

  4. resolved Dec 17, 2025, 09:44 PM UTC

    The incident has been resolved

Read the full incident report →

Major November 28, 2025 Service Impact to LON1, LON2, MAN1 Data Center. 1h 50m LON1 — London, United Kingdom, LON2 — London, United Kingdom, MAN1 — Manchester, United Kingdom

Started Nov 28, 2025, 08:50 AM UTC· resolved Nov 28, 2025, 10:40 AM UTC

  1. investigating Nov 28, 2025, 08:50 AM UTC

    We are currently investigating this issue.

  2. resolved Nov 28, 2025, 08:50 AM UTC

    We are investigating a service impacting incident at the LON1, LON2, MAN1 datacenter(s) for the following service(s) IPSEC, Netskope Client, Private Access. Full details can be found on the support portal.

  3. resolved Nov 28, 2025, 10:40 AM UTC

    The incident has been resolved

Read the full incident report →

Critical November 12, 2025 Service Impact - Netskope Client - All MP data centers 6d 14h

Started Nov 12, 2025, 01:00 PM UTC· resolved Nov 19, 2025, 03:01 AM UTC

  1. investigating Nov 12, 2025, 01:00 PM UTC

    We are currently investigating this issue.

  2. resolved Nov 12, 2025, 01:00 PM UTC

    We are investigating a service impacting incident for all MP datacenters related to the Netskope Client. Full details can be found on the support portal.

  3. resolved Nov 14, 2025, 08:06 AM UTC

    Netskope is targeting emergency hotfix release r132.0.7 to address the issue between Monday and Tuesday of next week. Netskope will provide confirmation of the hotfix availability once it has been successfully deployed to all commercial and compliance management plane environments.

  4. resolved Nov 18, 2025, 02:46 PM UTC

    Netskope has started deploying the r132.0.7 hot fix client release to all management planes beginning November 17th. Details regarding the deployment schedule, status, and recommended customer action has been updated in the support portal article. Once deployment has been completed to all management planes, the incident will be marked resolved.

  5. resolved Nov 19, 2025, 03:01 AM UTC

    The incident has been resolved

  6. resolved Nov 19, 2025, 03:01 AM UTC

    Netskope has completed the deployment of the r132.0.7 hot fix client release. The incident is now resolved.

Read the full incident report →

Critical November 8, 2025 Service Impact for NPA to several Data Centers 10h 23m AKL1 — Auckland, New Zealand, AMS1 — Amsterdam, Netherlands, BCN1 — Barcelona, Spain, BKK1 — Bangkok, Thailand and 63 more

Started Nov 08, 2025, 12:50 AM UTC· resolved Nov 08, 2025, 11:13 AM UTC

  1. investigating Nov 08, 2025, 12:50 AM UTC

    We are currently investigating this issue.

  2. resolved Nov 08, 2025, 12:50 AM UTC

    We are investigating service impacting incident at several data centers for the Private Access accessibility issue. Full details can be found on the support portal.

  3. resolved Nov 08, 2025, 02:30 AM UTC

    Netskope has identified that the issue is related to a recent NPA deployment. A rollback of the code has been completed across APAC-based DP's and we have confirmation that the issue has been resolved for those specific data centers. A roll back is now being completed within the EU-based DP's listed.

  4. resolved Nov 08, 2025, 02:40 AM UTC

    Netskope has completed the roll back activity for EU-based DP's. Testing and validation is now commencing at this time.

  5. resolved Nov 08, 2025, 03:22 AM UTC

    Validations have been completed and we have confirmed the issue has been mitigated post roll back activity. Root cause investigation remains underway.

  6. resolved Nov 08, 2025, 11:13 AM UTC

    The incident has been resolved

Read the full incident report →

Major October 31, 2025 Service Impact to LOS1 Data Center. 1d 23h LOS1 — Lagos, Nigeria

Started Oct 31, 2025, 01:28 PM UTC· resolved Nov 02, 2025, 12:44 PM UTC

  1. investigating Oct 31, 2025, 01:28 PM UTC

    We are currently investigating this issue.

  2. resolved Oct 31, 2025, 01:28 PM UTC

    We are investigating a service impacting incident at the LOS1 datacenter(s) for the following service(s) NPA Gateway, Secure Web Gateway. Full details can be found on the support portal.

  3. resolved Oct 31, 2025, 01:33 PM UTC

    Netskope has removed the LOS1 data center from NewEdge to force new client connections to alternative, nearby data centers while the investigation continues into potential root cause.

  4. monitoring Oct 31, 2025, 01:57 PM UTC

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

  5. resolved Oct 31, 2025, 05:29 PM UTC

    Netskope has identified the potential root cause as linked to a fiber cut disruption within the region. A case is opened with the IX vendor and they are actively working on restoration efforts. LOS1 will remain out of NewEdge until the IX issue has been completely resolved in order to ensure customers have the fastest connectivity and lowest latency options when steering through LOS1.

  6. resolved Nov 01, 2025, 03:14 PM UTC

    Netskope has received an update from the vendor that work continues on restoration efforts to the IX issue caused by the regional fiber cut damage. Once Netskope receives confirmation that restoration of the link has been restored, testing and validation will be performed when the IX link is reactivated. Once validations are successful, Netskope will re-enable LOS1 within the NewEdge network.

  7. resolved Nov 02, 2025, 12:43 PM UTC

    The vendor has completed the necessary repairs on the fiber link issue and connectivity with the IX has been fully restored with the LOS1 data center. Upon completing validation tests, LOS1 was reintroduced back into the NewEdge network successfully. The incident is now resolved.

  8. resolved Nov 02, 2025, 12:44 PM UTC

    The incident has been resolved

Read the full incident report →

Critical October 29, 2025 Service Impact to DFW3, FRA2, LON3, MEL2, SJC2, ZUR2 Data Center. 2h 56m DFW3 — Dallas, United States, FRA2 — Frankfurt, Germany, LON3 — London, United Kingdom, MEL2 — Melbourne, Australia and 3 more

Started Oct 29, 2025, 04:42 PM UTC· resolved Oct 29, 2025, 07:38 PM UTC

  1. investigating Oct 29, 2025, 04:42 PM UTC

    We are currently investigating this issue.

  2. resolved Oct 29, 2025, 04:42 PM UTC

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

  3. resolved Oct 29, 2025, 05:04 PM UTC

    Netskope has identified a potential root cause of the issue and is working on determining a potential mitigation strategy.

  4. resolved Oct 29, 2025, 05:22 PM UTC

    Netskope has determined that an active major cloud provider DNS outage is potentially contributing to service degradation of the WebUI component within the management planes. Netskope continues to work on the identification of a potential mitigation strategy.

  5. resolved Oct 29, 2025, 05:44 PM UTC

    Netskope continues to work on development and and implementation of a mitigation strategy.

  6. resolved Oct 29, 2025, 05:57 PM UTC

    Netskope has completed the mitigation strategy implementation and DNS errors have started to subside. Validations on WebUI accessibility and performance is now occurring.

  7. investigating Oct 29, 2025, 06:31 PM UTC

    We are continuing to investgate this issue.

  8. resolved Oct 29, 2025, 06:32 PM UTC

    Netskope has confirmed that the issues in the majority of the MP’s have subsided, however, there are observations of continued sporadic WebUI errors occurring for tenants provisioned in SJC2 specifically. Netskope is investigating SJC2 errors at this point in time.

  9. monitoring Oct 29, 2025, 06:58 PM UTC

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

  10. resolved Oct 29, 2025, 06:59 PM UTC

    Netskope has completed implementing additional fixes for the SJC2 and FRA2 management planes. Validations were successful. Tests have been carried out and results indicate that no additional WebUI errors are being reported at this time. Netskope will continue to monitor closely to confirm the issue has been fully mitigated.

  11. resolved Oct 29, 2025, 07:38 PM UTC

    The incident has been resolved

Read the full incident report →

Major October 29, 2025 Service Impact to WAW1 Data Center. 13h 18m WAW1 — Warsaw, Poland

Started Oct 29, 2025, 11:04 AM UTC· resolved Oct 30, 2025, 12:22 AM UTC

  1. investigating Oct 29, 2025, 11:04 AM UTC

    We are currently investigating this issue.

  2. resolved Oct 29, 2025, 11:04 AM UTC

    We are investigating a service impacting incident at the WAW1 datacenter(s) for the following service(s) Netskope Client, Secure Web Gateway. Full details can be found on the support portal.

  3. resolved Oct 29, 2025, 11:25 AM UTC

    This issue has been mitigated by removing WAW1 from NewEdge traffic management system.

  4. monitoring Oct 29, 2025, 11:25 AM UTC

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

  5. resolved Oct 29, 2025, 02:28 PM UTC

    Netskope continues to investigate for a possible root cause of the issue and WAW1 will remain out of NewEdge until the issue has been identified and resolved.

  6. resolved Oct 30, 2025, 12:21 AM UTC

    Netskope addressed the root cause of the issue and the WAW1 POP has been reintroduced back into the NewEdge network.

  7. resolved Oct 30, 2025, 12:22 AM UTC

    The incident has been resolved

Read the full incident report →

Critical October 24, 2025 Service Impact to MAN1 Data Center. 1h 17m DUB1 — Dublin, Ireland, MAN1 — Manchester, United Kingdom

Started Oct 24, 2025, 11:02 AM UTC· resolved Oct 24, 2025, 12:19 PM UTC

  1. investigating Oct 24, 2025, 11:02 AM UTC

    We are currently investigating this issue.

  2. resolved Oct 24, 2025, 11:02 AM UTC

    We are investigating a service impacting incident at the MAN1 datacenter(s) for the following service(s) EProxy, GRE, IPSEC, Netskope Client, Proxy Chaining, Secure Web Gateway. Full details can be found on the support portal.

  3. resolved Oct 24, 2025, 11:58 AM UTC

    Netskope has identified the root cause and applying a fix to mitigate the impact.

  4. resolved Oct 24, 2025, 12:19 PM UTC

    The incident has been resolved

Read the full incident report →

Major October 20, 2025 Service Impact to PVG1, SZX1 Data Center. 21m PVG1 — Shanghai, China, SZX1 — Shenzhen, China

Started Oct 20, 2025, 02:44 AM UTC· resolved Oct 20, 2025, 03:05 AM UTC

  1. investigating Oct 20, 2025, 02:44 AM UTC

    We are currently investigating this issue.

  2. resolved Oct 20, 2025, 02:44 AM UTC

    We are investigating a service impacting incident at the PVG1, SZX1 datacenter(s) for the following service(s) Gateway, GSLB, Netskope Client, NPA Gateway, NPA Stitcher, Private Access, Secure Web Gateway. Full details can be found on the support portal.

  3. resolved Oct 20, 2025, 03:05 AM UTC

    The incident has been resolved

Read the full incident report →

Major October 17, 2025 Service Impact to ORD1 Data Center. 2h 13m ORD1 — Chicago, United States

Started Oct 17, 2025, 07:50 PM UTC· resolved Oct 17, 2025, 10:03 PM UTC

  1. investigating Oct 17, 2025, 07:50 PM UTC

    We are currently investigating this issue.

  2. resolved Oct 17, 2025, 07:50 PM UTC

    We are investigating a service impacting incident at the ORD1 datacenter(s) for the following service(s) NPA Gateway. Full details can be found on the support portal.

  3. resolved Oct 17, 2025, 08:53 PM UTC

    Netskope identified a network routing path that was contributing to service disruption. The affected route was removed, and traffic has stabilized. We are currently monitoring performance and customer impact, and no further issues have been reported since mitigation. The ORD1 POP has been returned to NewEdge network, following verification of stability.

  4. monitoring Oct 17, 2025, 08:55 PM UTC

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

  5. resolved Oct 17, 2025, 10:03 PM UTC

    The incident has been resolved

Read the full incident report →

Major October 17, 2025 Service Impact to IAD2, LAX1, LAX2, STO1, SYD1, SYD2 Data Center. 2d 14h IAD2 — Washington, United States, LAX1 — Los Angeles, United States, LAX2 — Los Angeles, United States, STO1 — Stockholm, Sweden and 2 more

Started Oct 17, 2025, 03:24 AM UTC· resolved Oct 19, 2025, 06:00 PM UTC

  1. investigating Oct 17, 2025, 03:24 AM UTC

    We are currently investigating this issue.

  2. resolved Oct 17, 2025, 03:24 AM UTC

    We are investigating a service impacting incident at the IAD2, LAX1, LAX2, STO1, SYD1, SYD2 datacenter(s) for the following service(s) NPA Gateway, NPA Stitcher, Private Access. Full details can be found on the support portal.

  3. resolved Oct 17, 2025, 04:29 AM UTC

    Netskope has identified the root cause and is currently developing the mitigation strategy to resolve the issue.

  4. resolved Oct 17, 2025, 05:10 AM UTC

    Netskope is actively devising a mitigation strategy and closely monitoring the situation. Our analysis confirms that the impact on other POPs is significantly less severe than the previously affected POPs.

  5. resolved Oct 17, 2025, 05:43 AM UTC

    Netskope has identified that a subset of NPA service nodes are exhibiting high CPU utilization across multiple POPs, which is causing the reported behavior. To mitigate the impact, Netskope is manually restarting these affected nodes. Users whose NPA connections are being handled by these specific nodes may experience brief disconnections during the restart process.

  6. resolved Oct 17, 2025, 06:41 AM UTC

    Netskope has successfully completed the restart process and is now actively monitoring the status of the affected NPA service nodes.

  7. monitoring Oct 17, 2025, 06:41 AM UTC

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

  8. resolved Oct 17, 2025, 07:48 AM UTC

    Netskope has identified the root cause but is actively investigating various trigger points to prevent a recurrence of the issue. Until a permanent solution is deployed, we will continue to monitor the affected service nodes and promptly perform restarts when the issue is observed. Users whose NPA connections are being handled by these specific nodes may still experience brief disconnections during the restart process. We anticipate providing an update on the final fix within the next 24 hours.

  9. resolved Oct 17, 2025, 02:53 PM UTC

    Netskope is currently developing an Emergency Hotfix (EHF) to address the root cause of this issue and continues to closely monitor the infrastructure. Based on ongoing observations across the affected POPs, the impact is now considered mitigated. We will share further details regarding the EHF deployment in the next update.

  10. monitoring Oct 17, 2025, 02:54 PM UTC

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

  11. resolved Oct 19, 2025, 06:00 PM UTC

    The incident has been resolved

Read the full incident report →