- Detected by Pingoru
- Jul 01, 2026, 01:47 AM UTC
- Resolved
- Jul 01, 2026, 02:20 AM UTC
- Duration
- 33m
Affected: DFW3 — Dallas, United States
Timeline · 3 updates
-
investigating Jul 01, 2026, 01:47 AM UTC
We are currently investigating this issue.
-
resolved Jul 01, 2026, 01:47 AM UTC
We are investigating a service impacting incident at the DFW3 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, 02:20 AM UTC
The incident has been resolved
Read the full incident report →
- Detected by Pingoru
- Jul 01, 2026, 12:30 AM UTC
- Resolved
- Jul 01, 2026, 01:50 AM UTC
- Duration
- 1h 20m
Affected: SJC1 — San Jose, United States
Timeline · 6 updates
-
investigating Jul 01, 2026, 12:30 AM UTC
We are currently investigating this issue.
-
resolved Jul 01, 2026, 12:30 AM UTC
We are investigating a service impacting incident at the 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 Jul 01, 2026, 01:11 AM UTC
Netskope has identified the root cause and is actively executing mitigation activities to restore the affected services. Recovery is in progress through controlled infrastructure remediation, and Engineering continues to closely monitor the environment.
-
monitoring Jul 01, 2026, 01:12 AM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Jul 01, 2026, 01:42 AM UTC
The issue has been mitigated, we are continuing to monitor the results.
-
resolved Jul 01, 2026, 01:50 AM UTC
The incident has been resolved
Read the full incident report →
- Detected by Pingoru
- Jun 30, 2026, 11:53 PM UTC
- Resolved
- Jul 01, 2026, 01:41 AM UTC
- Duration
- 1h 48m
Affected: BOS1 — Boston, United StatesDEN1 — Denver, United States
Timeline · 6 updates
-
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
Read the full incident report →
- Detected by Pingoru
- Jun 29, 2026, 04:36 AM UTC
- Resolved
- Jun 29, 2026, 11:30 PM UTC
- Duration
- 18h 54m
Affected: SYD2 — Sydney, Australia
Timeline · 6 updates
-
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
Read the full incident report →
- Detected by Pingoru
- Jun 26, 2026, 10:40 AM UTC
- Resolved
- Jun 30, 2026, 05:00 AM UTC
- Duration
- 3d 18h
Affected: BOM1 — Mumbai, IndiaBOM2 — Mumbai, IndiaCCU1 — Kolkata, IndiaDEL1 — Delhi, IndiaDEL2 — Delhi, IndiaHYD1 — Hyderabad, IndiaMAA1 — Chennai, IndiaMAA2 — Chennai, India
Timeline · 9 updates
Read the full incident report →
- Detected by Pingoru
- Jun 26, 2026, 06:18 AM UTC
- Resolved
- Jun 30, 2026, 05:00 AM UTC
- Duration
- 3d 22h
Affected: SIN2 — Singapore, SingaporeSJC1 — San Jose, United States
Timeline · 8 updates
-
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
Read the full incident report →
- Detected by Pingoru
- Jun 25, 2026, 08:28 PM UTC
- Resolved
- Jun 26, 2026, 01:40 AM UTC
- Duration
- 5h 12m
Affected: BOM1 — Mumbai, IndiaBOM2 — Mumbai, IndiaCCU1 — Kolkata, IndiaDEL1 — Delhi, IndiaHYD1 — Hyderabad, IndiaMAA1 — Chennai, IndiaMAA2 — Chennai, India
Timeline · 4 updates
-
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
Read the full incident report →
- Detected by Pingoru
- Jun 24, 2026, 07:35 AM UTC
- Resolved
- Jun 24, 2026, 08:20 AM UTC
- Duration
- 45m
Affected: FR4 — Frankfurt, Germany
Timeline · 3 updates
-
investigating Jun 24, 2026, 07:35 AM UTC
We are currently investigating this issue.
-
resolved Jun 24, 2026, 07:35 AM UTC
We are investigating a service impacting incident at the FR4 datacenter(s) for the following service(s) Private Access, 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 24, 2026, 08:20 AM UTC
The incident has been resolved
Read the full incident report →
- Detected by Pingoru
- Jun 22, 2026, 09:48 PM UTC
- Resolved
- Jun 23, 2026, 06:09 PM UTC
- Duration
- 20h 21m
Affected: SYD1 — Sydney, Australia
Timeline · 8 updates
-
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
Read the full incident report →
- Detected by Pingoru
- Jun 18, 2026, 01:58 PM UTC
- Resolved
- Jun 18, 2026, 03:29 PM UTC
- Duration
- 1h 31m
Timeline · 5 updates
-
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
-
monitoring Jun 18, 2026, 03:49 PM UTC
The issue has been mitigated, we are continuing to monitor the results.
Read the full incident report →
- Detected by Pingoru
- Jun 15, 2026, 08:10 AM UTC
- Resolved
- Jun 15, 2026, 09:24 AM UTC
- Duration
- 1h 14m
Affected: PVG1 — Shanghai, China
Timeline · 4 updates
-
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
-
monitoring Jun 15, 2026, 09:24 AM UTC
The issue has been mitigated, we are continuing to monitor the results.
Read the full incident report →
- Detected by Pingoru
- Jun 12, 2026, 04:21 PM UTC
- Resolved
- Jun 12, 2026, 05:28 PM UTC
- Duration
- 1h 7m
Affected: AM2 — Amsterdam, Netherlands
Timeline · 5 updates
-
investigating Jun 12, 2026, 04:21 PM UTC
We are currently investigating this issue.
-
resolved Jun 12, 2026, 04:21 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, 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.
-
monitoring Jun 12, 2026, 04:43 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Jun 12, 2026, 05:09 PM UTC
The issue has been mitigated, we are continuing to monitor the results.
-
resolved Jun 12, 2026, 05:28 PM UTC
The incident has been resolved
Read the full incident report →
- Detected by Pingoru
- Jun 12, 2026, 01:51 AM UTC
- Resolved
- Jun 12, 2026, 03:02 AM UTC
- Duration
- 1h 11m
Affected: PEK1 — Beijing, ChinaPVG1 — Shanghai, ChinaPVG2 — Shanghai, ChinaSZX1 — Shenzhen, China
Timeline · 4 updates
-
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
Read the full incident report →
- Detected by Pingoru
- May 29, 2026, 09:07 PM UTC
- Resolved
- May 29, 2026, 11:24 PM UTC
- Duration
- 2h 17m
Timeline · 5 updates
-
investigating May 29, 2026, 09:07 PM UTC
We are currently investigating this issue.
-
resolved May 29, 2026, 09:07 PM UTC
We are investigating a service impacting incident at the All MPs datacenter(s) for the following service(s) DEM, 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.
-
monitoring May 29, 2026, 09:36 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring May 29, 2026, 10:17 PM UTC
The issue has been mitigated, we are continuing to monitor the results.
-
resolved May 29, 2026, 11:24 PM UTC
The incident has been resolved
Read the full incident report →
- Detected by Pingoru
- May 23, 2026, 07:30 AM UTC
- Resolved
- May 23, 2026, 08:45 AM UTC
- Duration
- 1h 15m
Affected: SIN2 — Singapore, Singapore
Timeline · 4 updates
-
investigating May 23, 2026, 07:30 AM UTC
We are currently investigating this issue.
-
resolved May 23, 2026, 07:30 AM UTC
We are investigating a service impacting incident at the SIN2 datacenter(s) for the following service(s) 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.
-
resolved May 23, 2026, 08:32 AM UTC
Netskope has identified the root cause of the issue and is currently applying a fix to mitigate the impact.
-
resolved May 23, 2026, 08:45 AM UTC
The incident has been resolved
Read the full incident report →
- Detected by Pingoru
- May 19, 2026, 10:55 AM UTC
- Resolved
- May 19, 2026, 07:26 PM UTC
- Duration
- 8h 31m
Affected: AM2 — Amsterdam, NetherlandsMEL2 — Melbourne, AustraliaSJC1 — San Jose, United StatesSV5 — San Jose, United StatesZUR2 — Zurich, Switzerland
Timeline · 10 updates
Read the full incident report →
- Detected by Pingoru
- May 15, 2026, 12:12 AM UTC
- Resolved
- May 15, 2026, 02:50 AM UTC
- Duration
- 2h 38m
Timeline · 5 updates
-
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
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 →
- 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
-
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
Read the full incident report →
- 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
-
investigating Apr 30, 2026, 08:45 AM UTC
We are currently investigating this issue.
-
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.
-
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.
-
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.
-
resolved Apr 30, 2026, 10:15 AM UTC
The incident has been resolved
Read the full incident report →
- 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
-
investigating Apr 23, 2026, 03:45 PM UTC
We are currently investigating this issue.
-
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.
-
resolved Apr 23, 2026, 04:41 PM UTC
Netskope has identified the root cause and is implementing a potential mitigation strategy.
-
monitoring Apr 23, 2026, 05:24 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Apr 23, 2026, 05:57 PM UTC
The issue has been mitigated, we are continuing to monitor the results.
-
resolved Apr 23, 2026, 06:24 PM UTC
The incident has been resolved
Read the full incident report →
- Detected by Pingoru
- Apr 10, 2026, 09:13 AM UTC
- Resolved
- Apr 10, 2026, 07:20 PM UTC
- Duration
- 10h 7m
Timeline · 11 updates
Read the full incident report →
- 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
-
investigating Apr 07, 2026, 02:06 AM UTC
We are currently investigating this issue.
-
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.
-
resolved Apr 07, 2026, 02:40 AM UTC
The incident has been resolved
Read the full incident report →
- Detected by Pingoru
- Apr 02, 2026, 12:16 PM UTC
- Resolved
- Apr 03, 2026, 10:48 AM UTC
- Duration
- 22h 32m
Timeline · 8 updates
-
investigating Apr 02, 2026, 12:16 PM UTC
We are currently investigating this issue.
-
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.
-
resolved Apr 02, 2026, 12:28 PM UTC
Netskope continues to investigate the issue.
-
resolved Apr 02, 2026, 01:51 PM UTC
Netskope continues to actively investigate the issue and is working to identify the root cause.
-
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.
-
monitoring Apr 02, 2026, 03:27 PM UTC
The issue has been mitigated, we are continuing to monitor the results.
-
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.
-
resolved Apr 03, 2026, 10:48 AM UTC
The incident has been resolved
Read the full incident report →
- 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
-
investigating Mar 30, 2026, 06:06 PM UTC
We are currently investigating this issue.
-
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.
-
resolved Mar 30, 2026, 07:05 PM UTC
Netskope is actively working on implementing the mitigation strategy
-
resolved Mar 30, 2026, 08:05 PM UTC
Netskope continues to actively implement a mitigation strategy.
-
monitoring Mar 30, 2026, 09:28 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 30, 2026, 10:41 PM UTC
All affected nodes have been restored to an online status.
-
monitoring Mar 30, 2026, 11:02 PM UTC
The issue has been mitigated, we are continuing to monitor the results.
-
resolved Mar 30, 2026, 11:45 PM UTC
The incident has been resolved
Read the full incident report →
- 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
Read the full incident report →