Netskope Outage History

Netskope is up right now

There were 22 Netskope outages since February 4, 2026 totaling 262h 44m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://trust.netskope.com

Major April 30, 2026

Service Impact to FR4 Data Center.

Detected by Pingoru
Apr 30, 2026, 06:35 PM UTC
Resolved
Apr 30, 2026, 09:21 PM UTC
Duration
2h 46m
Affected: FR4 — Frankfurt, Germany
Timeline · 5 updates
  1. investigating Apr 30, 2026, 06:35 PM UTC

    We are currently investigating this issue.

  2. resolved Apr 30, 2026, 06:35 PM UTC

    We are investigating a service impacting incident at the FR4 datacenter(s) for the following service(s) Data Protection, 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 Apr 30, 2026, 08:13 PM UTC

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

  4. monitoring Apr 30, 2026, 08:51 PM UTC

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

  5. resolved Apr 30, 2026, 08:57 PM UTC

    The incident has been resolved

Read the full incident report →

Major April 30, 2026

Service Impact to BOM1 Data Center.

Detected by Pingoru
Apr 30, 2026, 08:45 AM UTC
Resolved
Apr 30, 2026, 10:15 AM UTC
Duration
1h 30m
Affected: BOM1 — Mumbai, India
Timeline · 5 updates
  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

Read the full incident report →

Critical April 28, 2026

Service Impact to SJC1 Data Center.

Detected by Pingoru
Apr 28, 2026, 03:20 PM UTC
Resolved
Apr 30, 2026, 12:55 AM UTC
Duration
1d 9h
Affected: SJC1 — San Jose, United States
Timeline · 17 updates
  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.

Read the full incident report →

Major April 23, 2026

Service Impact to FRA2 Data Center.

Detected by Pingoru
Apr 23, 2026, 03:45 PM UTC
Resolved
Apr 23, 2026, 06:24 PM UTC
Duration
2h 39m
Affected: FRA2 — Frankfurt, Germany
Timeline · 6 updates
  1. investigating Apr 23, 2026, 03:45 PM UTC

    We are currently investigating this issue.

  2. resolved Apr 23, 2026, 03:45 PM UTC

    We are investigating a service impacting incident at the FRA2 datacenter(s) for the following service(s) NSClient download. 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 23, 2026, 04:41 PM UTC

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

  4. monitoring Apr 23, 2026, 05:24 PM UTC

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

  5. monitoring Apr 23, 2026, 05:57 PM UTC

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

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

    The incident has been resolved

Read the full incident report →

Critical April 21, 2026

Service Impact to AM2 Data Center.

Detected by Pingoru
Apr 21, 2026, 11:34 PM UTC
Resolved
Apr 22, 2026, 12:33 AM UTC
Duration
59m
Affected: AM2 — Amsterdam, Netherlands
Timeline · 5 updates
  1. investigating Apr 21, 2026, 11:34 PM UTC

    We are currently investigating this issue.

  2. resolved Apr 21, 2026, 11:34 PM UTC

    We are investigating a service impacting incident at the AM2 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 Apr 21, 2026, 11:54 PM UTC

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

  4. monitoring Apr 22, 2026, 12:13 AM UTC

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

  5. resolved Apr 22, 2026, 12:33 AM UTC

    The incident has been resolved

Read the full incident report →

Major April 10, 2026

Service Impact to All DPs Data Center.

Detected by Pingoru
Apr 10, 2026, 09:13 AM UTC
Resolved
Apr 10, 2026, 07:20 PM UTC
Duration
10h 7m
Timeline · 11 updates
  1. investigating Apr 10, 2026, 09:13 AM UTC

    We are currently investigating this issue.

  2. resolved Apr 10, 2026, 09:13 AM UTC

    We are investigating a service impacting incident at the All DPs datacenter(s) for the following service(s) IPSEC. 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 10, 2026, 09:40 AM UTC

    Netskope has started the rollback process and expects it to be completed in the next 2 hours. Next update will be shared at 11:30 AM UTC.

  4. resolved Apr 10, 2026, 11:55 AM UTC

    Netskope has completed the rollback across 50% of the PoPs. The remaining rollback activities are expected to conclude within the next three hours. We will provide the next status update at 3:00 PM UTC.

  5. resolved Apr 10, 2026, 03:00 PM UTC

    Netskope has successfully completed the rollback across all Points of Presence (PoPs). A temporary surge in IPsec tunnel re-establishment requests triggered DoS protection mechanisms on certain PoPs, resulting in some tunnels going down. Netskope is actively working to stabilize the environment and restore full service continuity.

  6. resolved Apr 10, 2026, 04:16 PM UTC

    Following the rollback of IPsec nodes across all PoPs, a temporary tunnel imbalance has been observed. Netskope is actively executing remediation actions to restore balanced tunnel distribution. Customers may notice brief tunnel flapping during this window. A limited number of PoPs have also experienced continued failures after rollback and will be temporarily taken out of service for continued mitigation. Currently working is being performed in SAO4 and NYC1. Additional POPs will be provided if required.

  7. resolved Apr 10, 2026, 04:48 PM UTC

    Work continues to redeploy the IPSec service in some impacted data centers. Tunnel rebalancing efforts also continues at this time. During the rebalance activity, customers may experience transient tunnel flaps.

  8. resolved Apr 10, 2026, 05:09 PM UTC

    Rebalance activity for all Day 3 POPs has been completed. Day 2 is currently underway. Details on which POPs are targeted under each can be viewed in the support portal deployment notifications. Detail on how to access the deployment schedule is included in the support portal article. All work is expected to completed within the next 30 minutes.

  9. resolved Apr 10, 2026, 05:17 PM UTC

    Rebalance activity for all Day 2 POPs has been completed. Day 1 is currently underway. SAO4 data center work has also been completed. Further details are in the support portal.

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

    Rebalance activity for all Day 1 POPs has been completed. Netskope is now conducting a thorough audit to ensure the IPSec service is fully operational in all data centers.

  11. resolved Apr 10, 2026, 07:20 PM UTC

    The incident has been resolved

Read the full incident report →

Critical April 7, 2026

Service Impact to SIN2 Data Center.

Detected by Pingoru
Apr 07, 2026, 09:02 AM UTC
Resolved
Apr 07, 2026, 11:51 AM UTC
Duration
2h 49m
Affected: SIN2 — Singapore, Singapore
Timeline · 5 updates
  1. investigating Apr 07, 2026, 09:02 AM UTC

    We are currently investigating this issue.

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

    We are investigating a service impacting incident at the SIN2 datacenter(s) for the following service(s) Event Logging. 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, 10:02 AM UTC

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

  4. resolved Apr 07, 2026, 10:48 AM UTC

    Netskope has applied the fix to mitigate the impact. It is anticipated to take close to 3 hours for the lag to completely drain. The next update will be shared at 1:45 PM UTC.

  5. resolved Apr 07, 2026, 11:51 AM UTC

    The incident has been resolved

Read the full incident report →

Major April 7, 2026

Service Impact to MEL2 Data Center.

Detected by Pingoru
Apr 07, 2026, 02:06 AM UTC
Resolved
Apr 07, 2026, 02:40 AM UTC
Duration
34m
Affected: MEL2 — Melbourne, Australia
Timeline · 3 updates
  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

Read the full incident report →

Major April 4, 2026

Service Impact to All MPs Data Center.

Detected by Pingoru
Apr 04, 2026, 08:28 PM UTC
Resolved
Apr 09, 2026, 05:20 PM UTC
Duration
4d 20h
Timeline · 6 updates
  1. investigating Apr 04, 2026, 08:28 PM UTC

    We are currently investigating this issue.

  2. resolved Apr 04, 2026, 08:28 PM UTC

    We are investigating a service impacting incident at the All MPs datacenter(s) for the following service(s) Cloud Access Security Broker. 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, 12:34 PM UTC

    The vendor continues with their investigation as a root cause has not yet been identified. A temporary mitigation solution has been implemented by Netskope to eliminate the risk of interruption. The incident will be marked resolved once the vendor has provided a final solution.

  4. monitoring Apr 07, 2026, 12:34 PM UTC

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

  5. resolved Apr 09, 2026, 05:18 PM UTC

    The vendor released a fix based on a code regression that was identified after a recent deployment within their environment. The fix was successful in addressing all API subscription errors. The incident is now being marked resolved.

  6. resolved Apr 09, 2026, 05:20 PM UTC

    The incident has been resolved

Read the full incident report →

Major April 2, 2026

Service Impact to all Management Planes(s).

Detected by Pingoru
Apr 02, 2026, 12:16 PM UTC
Resolved
Apr 03, 2026, 10:48 AM UTC
Duration
22h 32m
Timeline · 8 updates
  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

Read the full incident report →

Critical March 30, 2026

Service Impact to SV5 Data Center.

Detected by Pingoru
Mar 30, 2026, 06:06 PM UTC
Resolved
Mar 30, 2026, 11:45 PM UTC
Duration
5h 39m
Affected: SV5 — San Jose, United States
Timeline · 8 updates
  1. investigating Mar 30, 2026, 06:06 PM UTC

    We are currently investigating this issue.

  2. resolved Mar 30, 2026, 06:06 PM UTC

    We are investigating a service impacting incident at the SV5 datacenter(s) for the following service(s) CASB API Data Protection, Event Logging, 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 Mar 30, 2026, 07:05 PM UTC

    Netskope is actively working on implementing the mitigation strategy

  4. resolved Mar 30, 2026, 08:05 PM UTC

    Netskope continues to actively implement a mitigation strategy.

  5. monitoring Mar 30, 2026, 09:28 PM UTC

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

  6. resolved Mar 30, 2026, 10:41 PM UTC

    All affected nodes have been restored to an online status.

  7. monitoring Mar 30, 2026, 11:02 PM UTC

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

  8. resolved Mar 30, 2026, 11:45 PM UTC

    The incident has been resolved

Read the full incident report →

Critical March 30, 2026

Service Impact to ICN1 Data Center.

Detected by Pingoru
Mar 30, 2026, 04:00 AM UTC
Resolved
Mar 30, 2026, 03:10 PM UTC
Duration
11h 10m
Affected: ICN1 — Incheon, South Korea
Timeline · 9 updates
  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

    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.

Detected by Pingoru
Mar 27, 2026, 05:03 AM UTC
Resolved
Mar 27, 2026, 08:07 AM UTC
Duration
3h 4m
Timeline · 6 updates
  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

    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.

Detected by Pingoru
Mar 24, 2026, 04:17 AM UTC
Resolved
Mar 24, 2026, 07:00 AM UTC
Duration
2h 43m
Affected: DFW3 — Dallas, United StatesFRA2 — Frankfurt, GermanySIN2 — Singapore, SingaporeSJC2 — San Jose, United StatesZUR2 — Zurich, Switzerland
Timeline · 6 updates
  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

Read the full incident report →

Major March 23, 2026

Service Impact to LON2 Data Center.

Detected by Pingoru
Mar 23, 2026, 10:36 AM UTC
Resolved
Mar 23, 2026, 03:52 PM UTC
Duration
5h 16m
Affected: LON2 — London, United Kingdom
Timeline · 6 updates
  1. investigating Mar 23, 2026, 10:36 AM UTC

    We are currently investigating this issue.

  2. resolved Mar 23, 2026, 10:36 AM UTC

    We are investigating a service impacting incident at the LON2 datacenter(s) for the following service(s) GRE, IPSEC, 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 Mar 23, 2026, 10:59 AM UTC

    LON2 has been removed from NewEdge traffic management system to mitigate the impact.

  4. monitoring Mar 23, 2026, 02:40 PM UTC

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

  5. resolved Mar 23, 2026, 02:41 PM UTC

    LON2 data center has been re-added to the NewEdge traffic management system. Netskope will continue to monitor before marking this incident as fully mitigated.

  6. resolved Mar 23, 2026, 03:52 PM 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

Detected by Pingoru
Mar 11, 2026, 10:54 AM UTC
Resolved
Mar 11, 2026, 02:00 PM UTC
Duration
3h 6m
Affected: ZUR2 — Zurich, Switzerland
Timeline · 4 updates
  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

Read the full incident report →

Critical March 6, 2026

Service Impact to IAD3 Data Center.

Detected by Pingoru
Mar 06, 2026, 08:14 PM UTC
Resolved
Mar 07, 2026, 01:10 AM UTC
Duration
4h 56m
Timeline · 5 updates
  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

Read the full incident report →

Critical March 6, 2026

Service Impact to DFW3 Data Center.

Detected by Pingoru
Mar 06, 2026, 05:55 PM UTC
Resolved
Mar 07, 2026, 12:57 AM UTC
Duration
7h 2m
Affected: DFW3 — Dallas, United States
Timeline · 7 updates
  1. investigating Mar 06, 2026, 05:55 PM UTC

    We are currently investigating this issue.

  2. resolved Mar 06, 2026, 05:55 PM UTC

    We are investigating a service impacting incident at the DFW3 datacenter(s) for the following service(s) Advanced Analytics, Borderless WAN, CASB API Data Protection, Cloud Security Posture Management, Core Services, DEM, DSPM, Event Logging, Incident Management System, Management Console WebUI, SaaS Security Posture Management. 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 06, 2026, 07:57 PM UTC

    Netskope is working on the recovery of the infrastructure before proceeding with service restoration

  4. resolved Mar 06, 2026, 09:03 PM UTC

    Netskope is actively engaged in the recovery of the internal databases

  5. resolved Mar 06, 2026, 09:36 PM UTC

    The WebUI service has been restored.

  6. resolved Mar 06, 2026, 11:39 PM UTC

    Services recovered successfully. SkopeIT is currently processing a backlog of events

  7. resolved Mar 07, 2026, 12:57 AM UTC

    The incident has been resolved

Read the full incident report →

Critical March 2, 2026

Service Impact to TLV1 Data Center.

Detected by Pingoru
Mar 02, 2026, 02:23 PM UTC
Resolved
Mar 02, 2026, 09:39 PM UTC
Duration
7h 16m
Affected: TLV1 — Tel Aviv, Israel
Timeline · 4 updates
  1. investigating Mar 02, 2026, 02:23 PM UTC

    We are currently investigating this issue.

  2. resolved Mar 02, 2026, 02:23 PM UTC

    We are investigating a service impacting incident at the TLV1 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 Mar 02, 2026, 09:36 PM UTC

    Netskope has implemented further mitigation actions. Further details on what was done can be found in the Support Portal

  4. resolved Mar 02, 2026, 09:39 PM 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.

Detected by Pingoru
Feb 28, 2026, 11:36 AM UTC
Resolved
Feb 28, 2026, 01:00 PM UTC
Duration
1h 24m
Affected: BOM1 — Mumbai, IndiaBOM2 — Mumbai, IndiaCCU1 — Kolkata, IndiaDEL1 — Delhi, IndiaDEL2 — Delhi, IndiaMAA1 — Chennai, India
Timeline · 3 updates
  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

Read the full incident report →

Critical February 21, 2026

Service Impact to YYZ2 Data Center.

Detected by Pingoru
Feb 21, 2026, 11:22 PM UTC
Resolved
Feb 21, 2026, 11:26 PM UTC
Duration
4m
Timeline · 3 updates
  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

Read the full incident report →

Critical February 20, 2026

Missing malware events and alerts within SkopeIT

Detected by Pingoru
Feb 20, 2026, 02:04 PM UTC
Resolved
Feb 21, 2026, 06:45 AM UTC
Duration
16h 41m
Timeline · 9 updates
  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 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 →

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