Netskope Outage History
Netskope is up right nowPingoru has recorded 170 incidents for Netskope: 162 in the last 12 months and 47 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 11 | 191 of 720 (27%) |
| May 2026 | 12 | 38 of 744 (5%) |
| June 2026 | 16 | 134 of 720 (19%) |
| July 2026 | 11 | 173 of 744 (23%) |
| August 2026 | 20 | 172 of 744 (23%) |
| September 2026 | 14 | 275 of 720 (38%) |
| October 2026 | 12 | 141 of 589 (24%) |
Incidents, newest first
Major August 17, 2026 Service Impact to AM2, SJC1 Data Center. 1h 8m AM2 — Amsterdam, Netherlands, SJC1 — San Jose, United States
Started Aug 17, 2026, 07:41 AM UTC· resolved Aug 17, 2026, 08:49 AM UTC
- investigating Aug 17, 2026, 07:41 AM UTC
We are currently investigating this issue.
- resolved Aug 17, 2026, 07:41 AM UTC
We are investigating a service impacting incident at the AM2, SJC1 datacenter(s) for the following service(s) Advanced Analytics, 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.
- resolved Aug 17, 2026, 08:49 AM UTC
The incident has been resolved.
Critical August 17, 2026 Service Impact to PVG2 Data Center. 2h 10m PVG2 — Shanghai, China
Started Aug 17, 2026, 07:37 AM UTC· resolved Aug 17, 2026, 09:47 AM UTC
- investigating Aug 17, 2026, 07:37 AM UTC
We are currently investigating this issue.
- resolved Aug 17, 2026, 07:37 AM UTC
We are investigating a service impacting incident at the PVG2 datacenter(s) for the following service(s) NPA Gateway, 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.
- resolved Aug 17, 2026, 08:41 AM UTC
Netskope has identified the root cause and implemented a mitigation. Impacted Netskope Client users must restart the Netskope Client to successfully establish NPA connections through PVG2. We continue to closely monitor the environment to ensure service stability.
- monitoring Aug 17, 2026, 08:48 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Aug 17, 2026, 09:47 AM UTC
The incident has been resolved.
Major August 11, 2026 Service Impact to NYC4 and PHL1 Data Center. 1h 57m NYC4 — LaGuardia, United States, PHL1 — Philadelphia, United States
Started Aug 11, 2026, 09:00 PM UTC· resolved Aug 11, 2026, 10:57 PM UTC
- investigating Aug 11, 2026, 09:00 PM UTC
We are currently investigating this issue.
- resolved Aug 11, 2026, 09:00 PM UTC
We are investigating a service impacting incident at the PHL1, NYC4 datacenter(s) for the following service(s) AuthService. Additional details on the scope of impact are currently being assessed and will be provided within the support portal once an article is provided.
- monitoring Aug 11, 2026, 10:01 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Aug 11, 2026, 10:30 PM UTC
The issue has been mitigated, we are continuing to monitor the results.
- resolved Aug 11, 2026, 10:57 PM UTC
The incident has been resolved.
Critical August 10, 2026 BWAN-Asia-Management-Portal-Slowness-August-10-2026 1h 33m
Started Aug 10, 2026, 06:46 PM UTC· resolved Aug 10, 2026, 08:19 PM UTC
- investigating Aug 10, 2026, 06:46 PM UTC
We are currently investigating this issue.
- resolved Aug 10, 2026, 06:46 PM UTC
We are investigating a service impacting incident at the n/a datacenter(s) for the following service(s) Borderless WAN 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.
- monitoring Aug 10, 2026, 07:31 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Aug 10, 2026, 07:55 PM UTC
The issue has been mitigated, we are continuing to monitor the results.
- resolved Aug 10, 2026, 08:19 PM UTC
The incident has been resolved.
Critical August 10, 2026 Service Impact to AM2, SJC2, SV5 Data Center. 6h 56m AM2 — Amsterdam, Netherlands, BOM3 — Mumbai, India, DFW3 — Dallas, United States, FR4 — Frankfurt, Germany and 10 more
Started Aug 10, 2026, 02:49 PM UTC· resolved Aug 10, 2026, 09:45 PM UTC
- investigating Aug 10, 2026, 02:49 PM UTC
We are currently investigating this issue.
- resolved Aug 10, 2026, 02:49 PM UTC
We are investigating a service impacting incident at the AM2, SJC2, SV5 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.
- resolved Aug 10, 2026, 04:40 PM UTC
Netskope is actively monitoring tenant performance following the completion of the rollback procedure to verify that the issue has been fully resolved.
- resolved Aug 10, 2026, 06:10 PM UTC
Netskope continues to validate the mitigation techniques utilized.
- resolved Aug 10, 2026, 08:29 PM UTC
Comprehensive validation procedures are currently underway.
- monitoring Aug 10, 2026, 09:26 PM UTC
The issue has been mitigated, we are continuing to monitor the results.
- resolved Aug 10, 2026, 09:45 PM UTC
The incident has been resolved.
Major August 6, 2026 Service Impact to FR4 Data Center. 15m FR4 — Frankfurt, Germany
Started Aug 06, 2026, 01:35 AM UTC· resolved Aug 06, 2026, 01:50 AM UTC
- investigating Aug 06, 2026, 01:35 AM UTC
We are currently investigating this issue.
- resolved Aug 06, 2026, 01:35 AM UTC
We are investigating a service impacting incident at the FR4 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.
- resolved Aug 06, 2026, 01:50 AM UTC
The incident has been resolved.
Critical July 27, 2026 Service Impact to BWAN European Management Plane Service. 3h
Started Jul 27, 2026, 02:50 PM UTC· resolved Jul 27, 2026, 05:50 PM UTC
- investigating Jul 27, 2026, 02:50 PM UTC
We are currently investigating this issue.
- resolved Jul 27, 2026, 02:50 PM UTC
We are investigating a BWAN service impacting incident for European region for the Borderless WAN Management service. Additional details on the scope of impact are currently being assessed and will be provided within the support portal once an article is provided.
- monitoring Jul 27, 2026, 03:55 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Jul 27, 2026, 05:04 PM UTC
The issue has been mitigated, we are continuing to monitor the results.
- resolved Jul 27, 2026, 05:50 PM UTC
The incident has been resolved.
Major July 20, 2026 Service Impact to Gsuite Applications through Reverse Proxy across All DPs Data Center. 5h 53m AKL1 — Auckland, New Zealand, AMS1 — Amsterdam, Netherlands, ATL1 — Atlanta, United States, ATL2 — Atlanta, United States and 118 more
Started Jul 20, 2026, 09:10 AM UTC· resolved Jul 20, 2026, 03:03 PM UTC
- investigating Jul 20, 2026, 09:10 AM UTC
We are currently investigating this issue.
- resolved Jul 20, 2026, 09:10 AM UTC
We are investigating a service impacting incident at the All DPs datacenter(s) for the following service(s) Reverse Proxy. Additional details on the scope of impact are currently being assessed and will be provided within the support portal once an article is provided.
- resolved Jul 20, 2026, 09:37 AM UTC
Netskope has identified the root cause and is actively working to mitigate the impact.
- resolved Jul 20, 2026, 10:56 AM UTC
Netskope has begun deploying the mitigation. Once validation is complete, the update will be rolled out globally to restore normal service.
- resolved Jul 20, 2026, 11:53 AM UTC
Mitigation is progressing as planned and has been completed on approximately 40% of the affected data planes. Further updates will be provided upon full deployment.
- resolved Jul 20, 2026, 02:14 PM UTC
Netskope has successfully deployed the fix across all affected data planes. We continue to monitor the service to ensure stability before considering the incident fully resolved.
- monitoring Jul 20, 2026, 02:15 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 20, 2026, 03:03 PM UTC
The incident has been resolved.
Major July 20, 2026 Service Impact to HKG2 Data Center. 23h 39m HKG2 — Hong Kong, China
Started Jul 20, 2026, 03:23 AM UTC· resolved Jul 21, 2026, 03:02 AM UTC
- investigating Jul 20, 2026, 03:23 AM UTC
We are currently investigating this issue.
- resolved Jul 20, 2026, 03:23 AM UTC
We are investigating a service impacting incident at the HKG2 datacenter(s) for the following service(s) Private Access, 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.
- monitoring Jul 20, 2026, 04:06 AM UTC
The issue has been mitigated, we are continuing to monitor the results.
- resolved Jul 20, 2026, 04:48 AM UTC
Netskope continues to investigate the underlying root cause of the incident and is correlating the findings with historical telemetry to determine the cause and prevent recurrence.
- resolved Jul 20, 2026, 05:25 AM UTC
Netskope continues to investigate the root cause of the incident by analyzing available telemetry and correlating it with historical trends. Further updates are expected within the next 12–24 hours.
- resolved Jul 21, 2026, 03:02 AM UTC
The incident has been resolved.
Critical July 16, 2026 Service Impact to Auth Service and Enterprise browser on all DPs. 4d 12h
Started Jul 16, 2026, 01:50 AM UTC· resolved Jul 20, 2026, 02:15 PM UTC
- investigating Jul 16, 2026, 01:50 AM UTC
We are currently investigating this issue.
- resolved Jul 16, 2026, 01:50 AM UTC
We are investigating a service impacting incident on all datacenter(s) for the following service(s) AuthService, Browser 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.
- resolved Jul 16, 2026, 03:32 AM UTC
Netskope is currently reverting the R139 deployment on select POPs within the AU region to verify if this mitigates the issue. We will provide updates as they become available.
- resolved Jul 16, 2026, 04:25 AM UTC
Netskope identified a new feature introduced in the R139 release as the root cause. It has been successfully disabled across all POPs. The initial tests are positive and further validation is in progress.
- resolved Jul 17, 2026, 11:28 AM UTC
The AuthService on BNE1, MEL1, PER1, and SYD1 POPs will undergo a seamless 5-hour upgrade today at 14:00 UTC with zero expected customer impact. Future upgrades for remaining AU POPs are planned for July 20th, with exact schedules to follow.
- resolved Jul 20, 2026, 05:15 AM UTC
Scheduled upgrades for Authservice (MEL3 & SYD2) and Edge Proxy (PER1 & MEL3) will take place during Australia off-business hours on 20th July 2026. Full schedule details and expected impact are available in the support article.
- resolved Jul 20, 2026, 02:15 PM UTC
The incident has been resolved.
Critical July 14, 2026 Service Impact to BWAN management plane services in US region. 10h 50m SJC1 — San Jose, United States, SJC2 — San Jose, United States, SV5 — San Jose, United States
Started Jul 14, 2026, 12:47 PM UTC· resolved Jul 14, 2026, 11:37 PM UTC
- investigating Jul 14, 2026, 12:47 PM UTC
We are currently investigating this issue.
- resolved Jul 14, 2026, 12:47 PM UTC
We are investigating a service impacting incident at the SCL2, SJC1, SV5 datacenter(s) for the following service(s) Borderless WAN. Additional details on the scope of impact are currently being assessed and will be provided within the support portal once an article is provided.
- resolved Jul 14, 2026, 02:41 PM UTC
Netskope is seeing BWAN services return to normal and we are monitoring.
- resolved Jul 14, 2026, 03:39 PM UTC
BWAN connectivity services remain stable. Netskope is addressing a issue with metrics impacting dashboards within the BWAN management UI.
- monitoring Jul 14, 2026, 03:39 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 14, 2026, 04:11 PM UTC
Netskope has resolved the metrics service issue. There is an estimated two hours required for the service to process the backlog of messages that was created while in the degraded state. The next update will be provided once the backlog has been completely cleared.
- resolved Jul 14, 2026, 06:00 PM UTC
The backlog of events continues to be processed as expected. The current estimated time to completion is about 1.5 hours.
- resolved Jul 14, 2026, 09:02 PM UTC
Our team have confirmed that the backlog processing has stalled and our investigation is continuing. We have seen no further issues with inline connectivity up to this point.
- monitoring Jul 14, 2026, 10:50 PM UTC
The issue has been mitigated, we are continuing to monitor the results.
- resolved Jul 14, 2026, 11:37 PM UTC
The incident has been resolved
- resolved Jul 14, 2026, 11:37 PM UTC
The incident has been resolved.
Major July 13, 2026 Service Impact to PVG1, PVG2 Data Center. 1d 5h PVG1 — Shanghai, China, PVG2 — Shanghai, China
Started Jul 13, 2026, 05:28 AM UTC· resolved Jul 14, 2026, 10:52 AM UTC
- investigating Jul 13, 2026, 05:28 AM UTC
We are currently investigating this issue.
- resolved Jul 13, 2026, 05:28 AM UTC
We are investigating a service impacting incident at the PVG1, PVG2 datacenter(s) for the following service(s) Private Access and 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.
- resolved Jul 13, 2026, 06:13 AM UTC
PVG2 has been removed from the NewEdge traffic management system for the NPA services. It has also been identified that the Secure Web Gateway services are impacted for PVG1 POP and Netskope actively devising a mitigation strategy for the same.
- resolved Jul 13, 2026, 06:48 AM UTC
PVG1 has also been removed from the NewEdge traffic management system to mitigate the impact.
- resolved Jul 13, 2026, 07:38 AM UTC
Netskope has added the Shanghai, China (PVG2) Data Plane back into the NewEdge traffic management system. The transient connectivity issues previously seen have auto-resolved, and network traffic stability has returned.
- monitoring Jul 13, 2026, 07:48 AM UTC
The issue has been mitigated, we are continuing to monitor the results.
- resolved Jul 13, 2026, 07:51 AM UTC
The active customer impact has been mitigated. Netskope continues to work on completely restoring the Shanghai, China (PVG1) POP. The root cause has been identified, and Netskope is working on a remedial action to resolve the issue permanently.
- resolved Jul 14, 2026, 04:38 AM UTC
Netskope successfully deployed a fix and re-introduced PVG1 to the NewEdge traffic management system at 9:11 PM UTC on July 13, 2026. We will continue to monitor the environment closely throughout Shanghai business hours to ensure ongoing stability.
- resolved Jul 14, 2026, 10:52 AM UTC
The incident has been resolved
- resolved Jul 14, 2026, 10:52 AM UTC
The incident has been resolved.
Critical July 8, 2026 Service Impact to AM2 Data Center. 2h 35m AM2 — Amsterdam, Netherlands
Started Jul 08, 2026, 08:56 PM UTC· resolved Jul 08, 2026, 11:31 PM UTC
- investigating Jul 08, 2026, 08:56 PM UTC
We are currently investigating this issue.
- resolved Jul 08, 2026, 08:56 PM UTC
We are investigating a service impacting incident at the AM2 datacenter(s) for the following service(s) CASB API Data Protection, Core Services, 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.
- resolved Jul 08, 2026, 10:07 PM UTC
The performance degradation affecting the AM2 management plane has been partially mitigated, we anticipate that the servers and services will progressively recover until full functionality is completely restored.
- monitoring Jul 08, 2026, 10:38 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Jul 08, 2026, 11:07 PM UTC
The issue has been mitigated, we are continuing to monitor the results.
- resolved Jul 08, 2026, 11:31 PM UTC
The incident has been resolved
Critical June 30, 2026 Service Impact to BOS1, DEN1 Data Center. 1h 48m BOS1 — Boston, United States, DEN1 — Denver, United States
Started Jun 30, 2026, 11:53 PM UTC· resolved Jul 01, 2026, 01:41 AM UTC
- investigating Jun 30, 2026, 11:53 PM UTC
We are currently investigating this issue.
- resolved Jun 30, 2026, 11:53 PM UTC
We are investigating a service impacting incident at the BOS1, DEN1 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.
- resolved Jul 01, 2026, 12:49 AM UTC
Netskope continues to work on a mitigation strategy, and further updates will be shared as more information becomes available.
- monitoring Jul 01, 2026, 12:56 AM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Jul 01, 2026, 01:20 AM UTC
The issue has been mitigated, we are continuing to monitor the results.
- resolved Jul 01, 2026, 01:41 AM UTC
The incident has been resolved
- resolved Jul 01, 2026, 01:41 AM UTC
The incident has been resolved.
Major June 29, 2026 Service Impact to SYD2 Data Center. 18h 54m SYD2 — Sydney, Australia
Started Jun 29, 2026, 04:36 AM UTC· resolved Jun 29, 2026, 11:30 PM UTC
- investigating Jun 29, 2026, 04:36 AM UTC
We are currently investigating this issue.
- resolved Jun 29, 2026, 04:36 AM UTC
We are investigating a service impacting incident at the SYD2 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.
- resolved Jun 29, 2026, 05:05 AM UTC
Netskope has removed the SYD2 POP from the NewEdge Traffic Management system aiming to minimize the customer impact and mitigate the issue.
- monitoring Jun 29, 2026, 05:34 AM UTC
The issue has been mitigated, we are continuing to monitor the results.
- resolved Jun 29, 2026, 09:18 PM UTC
Netskope continues to work on identifying a root cause. The SYD2 POP will remain out of New Edge Traffic Management system until a final root cause has been identified and the data center can be safely reintroduced.
- resolved Jun 29, 2026, 11:30 PM UTC
The incident has been resolved
Critical June 26, 2026 Service Impact to BOM1, BOM2, CCU1, DEL1, DEL2, HYD1, MAA1, MAA2 Data Center. 3d 18h BOM1 — Mumbai, India, BOM2 — Mumbai, India, CCU1 — Kolkata, India, DEL1 — Delhi, India and 4 more
Started Jun 26, 2026, 10:40 AM UTC· resolved Jun 30, 2026, 05:00 AM UTC
- investigating Jun 26, 2026, 10:40 AM UTC
We are currently investigating this issue.
- resolved Jun 26, 2026, 10:40 AM UTC
We are investigating a service impacting incident at the BOM1, BOM2, CCU1, DEL1, DEL2, HYD1, MAA1, MAA2 datacenter(s) for the following service(s) GRE, IPSEC, 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.
- resolved Jun 26, 2026, 12:12 PM UTC
Netskope identified a network issue impacting a major carrier partner utilized across our India Points of Presence (PoPs). Performance has since stabilized, and services are recovering. We are currently engaged with the vendor to conduct a thorough root cause investigation while our team continues to monitor the platform closely.
- monitoring Jun 26, 2026, 12:37 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 26, 2026, 08:10 PM UTC
The issue was caused by secondary connectivity circuits exhibiting elevated RTT and intermittent packet loss. As there have been no further reports of issues following this window, this incident has been moved to mitigated status. Additionally, an incident earlier today impacted data flows from the India region to other regions, including the US West Coast. This was caused by a major ISP fiber cut, which required Netskope to perform traffic engineering to disable the affected circuit. We will move this incident to a resolved state once the provider has fully addressed the network issue.
- monitoring Jun 26, 2026, 08:10 PM UTC
The issue has been mitigated, we are continuing to monitor the results.
- resolved Jun 28, 2026, 02:06 PM UTC
Netskope have received information from our Internet Service Provider (ISP) indicating that the link previously affected by a fiber cut has now been successfully resolved. In light of this resolution, we are currently enabling this ISP link gradually across all affected Indian Points of Presence (PoPs) to restore optimal routing. We will mark this incident as resolved once the deployment concludes.
- resolved Jun 29, 2026, 05:00 PM UTC
The incident has been resolved
- resolved Jun 30, 2026, 01:30 AM UTC
Netskope has re-enabled Airtel connectivity across all affected POPs and is actively monitoring the environment to ensure connectivity remains stable. If no further issues are observed during the day, the incident will be resolved.
Major June 26, 2026 Service Impact to SIN2, SJC1 Data Center. 3d 22h SIN2 — Singapore, Singapore, SJC1 — San Jose, United States
Started Jun 26, 2026, 06:18 AM UTC· resolved Jun 30, 2026, 05:00 AM UTC
- investigating Jun 26, 2026, 06:18 AM UTC
We are currently investigating this issue.
- resolved Jun 26, 2026, 06:18 AM UTC
We are investigating a service impacting incident at the SIN2, SJC1 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.
- resolved Jun 26, 2026, 07:02 AM UTC
During the investigation, Netskope determined that the issue was not limited to the SIN2 and SJC1 Management Planes. The root cause was identified as latency and packet loss on Airtel network paths, resulting in degraded connectivity between users in India and the affected Management Planes.
- resolved Jun 26, 2026, 07:58 PM UTC
Earlier today, Netskope has performed traffic engineering updates to shift traffic away from the impacted provider network to other available connectivity circuits. We are continuing to work with the provider to determine when a full resolution will be reached. This incident has been moved to mitigated status, as we have not received any additional reports of connectivity issues since implementing these updates. We will resolve the incident once the provider confirms the issues within their network are addressed and the link is returned to service.
- monitoring Jun 26, 2026, 07:58 PM UTC
The issue has been mitigated, we are continuing to monitor the results.
- resolved Jun 29, 2026, 01:20 AM UTC
Netskope have received information from our Internet Service Provider (ISP) indicating that the link previously affected by a fiber cut has now been successfully resolved. In light of this resolution, we are currently enabling this ISP link gradually across all affected Indian Points of Presence (PoPs) to restore optimal routing. We will mark this incident as resolved once the deployment concludes.
- resolved Jun 30, 2026, 01:30 AM UTC
Netskope has re-enabled Airtel connectivity across all affected POPs and is actively monitoring the environment to ensure connectivity remains stable. If no further issues are observed during the day, the incident will be resolved.
- resolved Jun 30, 2026, 05:00 AM UTC
The incident has been resolved
Major June 25, 2026 Service Impact to BOM1, BOM2, CCU1, DEL1, HYD1, MAA1, MAA2 Data Center. 5h 12m BOM1 — Mumbai, India, BOM2 — Mumbai, India, CCU1 — Kolkata, India, DEL1 — Delhi, India and 3 more
Started Jun 25, 2026, 08:28 PM UTC· resolved Jun 26, 2026, 01:40 AM UTC
- investigating Jun 25, 2026, 08:28 PM UTC
We are currently investigating this issue.
- resolved Jun 25, 2026, 08:28 PM UTC
We are investigating a service impacting incident at the BOM1, BOM2, CCU1, DEL1, HYD1, MAA1, MAA2 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.
- monitoring Jun 25, 2026, 09:52 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 26, 2026, 01:40 AM UTC
The incident has been resolved
- resolved Jun 26, 2026, 01:40 AM UTC
The incident has been resolved.
Major June 22, 2026 Service Impact to SYD1 Data Center. 20h 21m SYD1 — Sydney, Australia
Started Jun 22, 2026, 09:48 PM UTC· resolved Jun 23, 2026, 06:09 PM UTC
- investigating Jun 22, 2026, 09:48 PM UTC
We are currently investigating this issue.
- resolved Jun 22, 2026, 09:48 PM UTC
We are investigating a service impacting incident at the SYD1 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.
- resolved Jun 23, 2026, 04:24 AM UTC
Netskope removed SYD1 from NewEdge traffic management system at 10:26 PM UTC on June 22nd to mitigate the impact. Netskope has identified the root cause as resource congestion affecting CPU performance on internal nodes, and we are actively working on a strategy to stabilize the infrastructure.
- monitoring Jun 23, 2026, 04:24 AM UTC
The issue has been mitigated, we are continuing to monitor the results.
- resolved Jun 23, 2026, 06:30 AM UTC
We are continuing to work on the mitigation strategy and will share the next update within the next 12 hours.
- resolved Jun 23, 2026, 01:46 PM UTC
Mitigation efforts are ongoing. Engineering continues to work toward service restoration, and the next update will be provided within 5 hours.
- resolved Jun 23, 2026, 04:59 PM UTC
SYD1 is currently being brought back online. Netskope will monitor performance for the next hour before officially closing the incident.
- resolved Jun 23, 2026, 06:09 PM UTC
The incident has been resolved
Critical June 18, 2026 Service Impact to YMQ2 Data Center. 1h 31m
Started Jun 18, 2026, 01:58 PM UTC· resolved Jun 18, 2026, 03:29 PM UTC
- investigating Jun 18, 2026, 01:58 PM UTC
We are currently investigating this issue.
- resolved Jun 18, 2026, 01:58 PM UTC
We are investigating a service impacting incident at the YMQ2 datacenter(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.
- monitoring Jun 18, 2026, 03:09 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 18, 2026, 03:29 PM UTC
The incident has been resolved
- resolved Jun 18, 2026, 03:29 PM UTC
The incident has been resolved.
- monitoring Jun 18, 2026, 03:49 PM UTC
The issue has been mitigated, we are continuing to monitor the results.
Critical June 15, 2026 Service Impact to PVG1 Data Center. 1h 14m PVG1 — Shanghai, China
Started Jun 15, 2026, 08:10 AM UTC· resolved Jun 15, 2026, 09:24 AM UTC
- investigating Jun 15, 2026, 08:10 AM UTC
We are currently investigating this issue.
- resolved Jun 15, 2026, 08:10 AM UTC
We are investigating a service impacting incident at the PVG1 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.
- resolved Jun 15, 2026, 09:10 AM UTC
The incident has been resolved
- resolved Jun 15, 2026, 09:24 AM UTC
The incident has been resolved.
- monitoring Jun 15, 2026, 09:24 AM UTC
The issue has been mitigated, we are continuing to monitor the results.
Critical June 12, 2026 Service Impact to PEK1, PVG1, PVG2, SZX1 Data Center. 1h 11m PEK1 — Beijing, China, PVG1 — Shanghai, China, PVG2 — Shanghai, China, SZX1 — Shenzhen, China
Started Jun 12, 2026, 01:51 AM UTC· resolved Jun 12, 2026, 03:02 AM UTC
- investigating Jun 12, 2026, 01:51 AM UTC
We are currently investigating this issue.
- resolved Jun 12, 2026, 01:51 AM UTC
We are investigating a service impacting incident at the PEK1, PVG1, PVG2, SZX1 datacenter(s) for the following service(s) Gateway, 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.
- monitoring Jun 12, 2026, 03:00 AM UTC
The issue has been mitigated, we are continuing to monitor the results.
- resolved Jun 12, 2026, 03:02 AM UTC
The incident has been resolved
- resolved Jun 12, 2026, 03:02 AM UTC
The incident has been resolved.
Major May 19, 2026 Service Impact to ZUR2 Data Center. 8h 31m AM2 — Amsterdam, Netherlands, MEL2 — Melbourne, Australia, SJC1 — San Jose, United States, SV5 — San Jose, United States and 1 more
Started May 19, 2026, 10:55 AM UTC· resolved May 19, 2026, 07:26 PM UTC
- investigating May 19, 2026, 10:55 AM UTC
We are currently investigating this issue.
- resolved May 19, 2026, 10:55 AM UTC
We are investigating a service impacting incident at the ZUR2 datacenter(s) for the following service(s) Core Services. Additional details on the scope of impact are currently being assessed and will be provided within the support portal once an article is provided.
- resolved May 19, 2026, 12:01 PM UTC
Netskope is actively investigating to isolate the root cause of this issue.
- resolved May 19, 2026, 01:05 PM UTC
Netskope continues to investigate to identify a root cause.
- resolved May 19, 2026, 02:24 PM UTC
Netskope continues to investigate to identify a root cause.
- resolved May 19, 2026, 03:37 PM UTC
Netskope continues to actively investigate the root cause.
- resolved May 19, 2026, 04:34 PM UTC
Netskope continues to investigate to identify a root cause.
- monitoring May 19, 2026, 05:21 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring May 19, 2026, 06:08 PM UTC
The issue has been mitigated, we are continuing to monitor the results.
- resolved May 19, 2026, 06:13 PM UTC
The incident has been resolved
- resolved May 19, 2026, 07:26 PM UTC
The incident has been resolved.
Major May 15, 2026 Service Impact to all Data Centers for MS teams upload traffic. 2h 38m AKL1 — Auckland, New Zealand, AMS1 — Amsterdam, Netherlands, ATL1 — Atlanta, United States, ATL2 — Atlanta, United States and 118 more
Started May 15, 2026, 12:12 AM UTC· resolved May 15, 2026, 02:50 AM UTC
- investigating May 15, 2026, 12:12 AM UTC
We are currently investigating this issue.
- 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.
- resolved May 15, 2026, 12:54 AM UTC
Netskope continues to investigate the root cause of this incident.
- resolved May 15, 2026, 02:50 AM UTC
The incident has been resolved
- resolved May 15, 2026, 02:50 AM UTC
The incident has been resolved.
- 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.
Major May 8, 2026 Service Impact to MAD1 Data Center. 2h 44m MAD1 — Madrid, Spain
Started May 08, 2026, 08:50 AM UTC· resolved May 08, 2026, 11:34 AM UTC
- investigating May 08, 2026, 08:50 AM UTC
We are currently investigating this issue.
- 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.
- 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.
- monitoring May 08, 2026, 09:12 AM UTC
The issue has been mitigated, we are continuing to monitor the results.
- 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.
- resolved May 08, 2026, 11:34 AM UTC
The incident has been resolved