Netskope Outage History

Netskope is up right now

Netskope had 85 outages in the last 2 years totaling 237h 16m of downtime — averaging 3.5 incidents per month.

There were 85 Netskope outages since October 21, 2024 totaling 237h 16m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://trust.netskope.com

Major May 15, 2026

Service Impact to all Data Centers for MS teams upload traffic.

Detected by Pingoru
May 15, 2026, 12:12 AM UTC
Resolved
May 15, 2026, 02:50 AM UTC
Duration
2h 38m
Timeline · 5 updates
  1. investigating May 15, 2026, 12:12 AM UTC

    We are currently investigating this issue.

  2. resolved May 15, 2026, 12:12 AM UTC

    We are investigating a service impacting incident at all 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 May 15, 2026, 12:54 AM UTC

    Netskope continues to investigate the root cause of this incident.

  4. resolved May 15, 2026, 02:50 AM UTC

    The incident has been resolved

  5. resolved May 15, 2026, 02:50 AM UTC

    Netskope identified the root cause and required changes are deployment to fix the issue. All the affected users should be able to perform Teams file/images Upload successfully.

Read the full incident report →

Critical May 13, 2026

Service Impact to SJC1 Data Center.

Detected by Pingoru
May 13, 2026, 07:14 PM UTC
Resolved
May 13, 2026, 08:00 PM UTC
Duration
46m
Affected: SJC1 — San Jose, United States
Timeline · 5 updates
  1. investigating May 13, 2026, 07:14 PM UTC

    We are currently investigating this issue.

  2. resolved May 13, 2026, 07:14 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. monitoring May 13, 2026, 07:36 PM UTC

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

  4. monitoring May 13, 2026, 07:54 PM UTC

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

  5. resolved May 13, 2026, 08:00 PM UTC

    The incident has been resolved

Read the full incident report →

Major May 8, 2026

Service Impact to MAD1 Data Center.

Detected by Pingoru
May 08, 2026, 08:50 AM UTC
Resolved
May 08, 2026, 11:34 AM UTC
Duration
2h 44m
Affected: MAD1 — Madrid, Spain
Timeline · 6 updates
  1. investigating May 08, 2026, 08:50 AM UTC

    We are currently investigating this issue.

  2. resolved May 08, 2026, 08:50 AM UTC

    We are investigating a service impacting incident at the MAD1 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 May 08, 2026, 09:08 AM UTC

    Netskope identified the root cause and applied a partial mitigation at 08:45 UTC while continuing work toward full resolution. As an interim measure, NPA service in MAD1 has been temporarily disabled, causing new client connections to redirect to the nearest available data center.

  4. monitoring May 08, 2026, 09:12 AM UTC

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

  5. resolved May 08, 2026, 11:33 AM UTC

    Netskope has completed the full mitigation, and NPA services in PoP MAD1 (Madrid, Spain) were restored at 09:54 UTC. Netskope considers this issue fully resolved.

  6. resolved May 08, 2026, 11:34 AM UTC

    The incident has been resolved

Read the full incident report →

Critical May 7, 2026

Service Impact to SIN2 Data Center.

Detected by Pingoru
May 07, 2026, 09:40 AM UTC
Resolved
May 07, 2026, 11:15 AM UTC
Duration
1h 35m
Affected: SIN2 — Singapore, Singapore
Timeline · 4 updates
  1. investigating May 07, 2026, 09:40 AM UTC

    We are currently investigating this issue.

  2. resolved May 07, 2026, 09:40 AM UTC

    We are investigating a service impacting incident at the SIN2 datacenter(s) for the following service(s) 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 May 07, 2026, 11:04 AM UTC

    Netskope has identified the root cause and implemented mitigation measures. IMS services have been fully restored, and remaining services are recovering progressively. We continue to actively monitor the situation.

  4. resolved May 07, 2026, 11:15 AM UTC

    The incident has been resolved

Read the full incident report →

Major May 4, 2026

Service Impact to AM2 Data Center.

Detected by Pingoru
May 04, 2026, 12:47 PM UTC
Resolved
May 04, 2026, 02:31 PM UTC
Duration
1h 44m
Affected: AM2 — Amsterdam, Netherlands
Timeline · 5 updates
  1. investigating May 04, 2026, 12:47 PM UTC

    We are currently investigating this issue.

  2. resolved May 04, 2026, 12:47 PM UTC

    We are investigating a service impacting incident at the AM2 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. resolved May 04, 2026, 01:59 PM UTC

    Netskope has identified the root cause and implemented mitigation measures. We continue to monitor the situation.

  4. monitoring May 04, 2026, 02:02 PM UTC

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

  5. resolved May 04, 2026, 02:31 PM UTC

    The incident has been resolved

Read the full incident report →

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 →

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 →

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 →

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 →

Major January 27, 2026

Service Impact to SJC1, SV5 Data Center.

Detected by Pingoru
Jan 27, 2026, 10:32 AM UTC
Resolved
Jan 27, 2026, 01:00 PM UTC
Duration
2h 28m
Affected: SJC1 — San Jose, United StatesSV5 — San Jose, United States
Timeline · 5 updates
  1. investigating Jan 27, 2026, 10:32 AM UTC

    We are currently investigating this issue.

  2. resolved Jan 27, 2026, 10:32 AM UTC

    We are investigating a service impacting incident at the SJC1, SV5 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 Jan 27, 2026, 11:22 AM UTC

    Netskope has identified the root cause and is actively working to mitigate the issue.

  4. resolved Jan 27, 2026, 12:11 PM UTC

    Netskope has completed mitigation actions, and events are now being consumed by the management plane. Event backlogs are currently draining and are expected to fully clear within the next 30–45 minutes.

  5. resolved Jan 27, 2026, 01:00 PM UTC

    The incident has been resolved

Read the full incident report →