Netskope Outage History

Netskope is up right now

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

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

Source: https://trust.netskope.com

Critical September 12, 2025

Service Impact to BOM1, BOM2 Data Center.

Detected by Pingoru
Sep 12, 2025, 09:19 AM UTC
Resolved
Sep 12, 2025, 11:50 AM UTC
Duration
2h 31m
Affected: BOM1 — Mumbai, IndiaBOM2 — Mumbai, India
Timeline · 6 updates
  1. investigating Sep 12, 2025, 09:19 AM UTC

    We are currently investigating this issue.

  2. resolved Sep 12, 2025, 09:19 AM UTC

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

  3. resolved Sep 12, 2025, 10:35 AM UTC

    Netskope identified an issue with one of the peering ISPs. To mitigate, we removed BOM2 from the New Edge traffic management system and applied Traffic Engineering on BOM1 to route around the problematic ISP.

  4. resolved Sep 12, 2025, 10:56 AM UTC

    Netskope confirmed that the issue in BOM1 was resolved through Traffic Engineering. The same measures were implemented in BOM2, which has now been successfully reinstated into the New Edge Traffic Management system.

  5. monitoring Sep 12, 2025, 10:56 AM UTC

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

  6. resolved Sep 12, 2025, 11:50 AM UTC

    The incident has been resolved

Read the full incident report →

Major September 11, 2025

NPA Service Impact to tenants provisioned in AM2, FRA2 Management Plane and MIL1 Dataplane

Detected by Pingoru
Sep 11, 2025, 08:10 AM UTC
Resolved
Sep 11, 2025, 11:30 AM UTC
Duration
3h 20m
Affected: AM2 — Amsterdam, NetherlandsFRA2 — Frankfurt, GermanyMIL1 — Milan, Italy
Timeline · 6 updates
  1. investigating Sep 11, 2025, 08:10 AM UTC

    We are currently investigating this issue.

  2. resolved Sep 11, 2025, 08:10 AM UTC

    We are investigating a service impacting incident for tenants provisioned at the AM2, FRA2 Management Plane and MIL1 Dataplane for the following service(s) Private Access. Full details can be found on the support portal.

  3. resolved Sep 11, 2025, 09:10 AM UTC

    Netskope has identified that the issue originated from the MIL1 POP and the POP has been removed from New Edge Traffic Management system for NPA services around 8:50 AM UTC, the issue is mitigated. Netskope continues to perform a detailed root cause analysis.

  4. monitoring Sep 11, 2025, 09:14 AM UTC

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

  5. resolved Sep 11, 2025, 10:18 AM UTC

    Netskope has identified the root cause at the MIL1 POP, implemented a fix, and re-enabled NPA services at this site. We continue to closely monitor performance before declaring the issue fully resolved.

  6. resolved Sep 11, 2025, 11:30 AM UTC

    The incident has been resolved

Read the full incident report →

Critical August 20, 2025

Service Impact to AM2, FR4, and ZUR2 Data Center.

Detected by Pingoru
Aug 20, 2025, 08:35 AM UTC
Resolved
Aug 20, 2025, 10:30 AM UTC
Duration
1h 55m
Affected: AM2 — Amsterdam, NetherlandsFR4 — Frankfurt, GermanyZUR2 — Zurich, Switzerland
Timeline · 4 updates
  1. investigating Aug 20, 2025, 08:35 AM UTC

    We are currently investigating this issue.

  2. resolved Aug 20, 2025, 08:35 AM UTC

    We are investigating a service impacting incident at the AM2, FR4 and ZUR2 datacenter(s) for the following service(s) Management Console WebUI. Full details can be found on the support portal.

  3. resolved Aug 20, 2025, 09:35 AM UTC

    Netskope has identified the issue to be with the DNS component. The mitigation strategy is being formulated to mitigate the impact.

  4. resolved Aug 20, 2025, 10:30 AM UTC

    The incident has been resolved

Read the full incident report →

Critical August 15, 2025

Service Impact to DFW1, DFW4 Data Center.

Detected by Pingoru
Aug 15, 2025, 06:17 PM UTC
Resolved
Aug 15, 2025, 09:00 PM UTC
Duration
2h 43m
Affected: DFW1 — Dallas, United StatesDFW4 — Dallas, United States
Timeline · 5 updates
  1. investigating Aug 15, 2025, 06:17 PM UTC

    We are currently investigating this issue.

  2. resolved Aug 15, 2025, 06:17 PM UTC

    We are investigating a service impacting incident at the DFW1, DFW4 datacenter(s) for the following service(s) AuthService. Full details can be found on the support portal.

  3. resolved Aug 15, 2025, 07:36 PM UTC

    Our investigation of the incident is still ongoing. More details will be provided as soon as available. Full details can be found on the support portal.

  4. monitoring Aug 15, 2025, 07:59 PM UTC

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

  5. resolved Aug 15, 2025, 09:00 PM UTC

    The incident has been resolved

Read the full incident report →

Major August 11, 2025

Service Impact to SJC1, SJC2, SV5 Data Center.

Detected by Pingoru
Aug 11, 2025, 02:32 PM UTC
Resolved
Aug 11, 2025, 04:38 PM UTC
Duration
2h 6m
Affected: SJC1 — San Jose, United StatesSJC2 — San Jose, United StatesSV5 — San Jose, United States
Timeline · 4 updates
  1. investigating Aug 11, 2025, 02:32 PM UTC

    We are currently investigating this issue.

  2. resolved Aug 11, 2025, 02:32 PM UTC

    We are investigating a service impacting incident at the SJC1, SJC2, SV5 datacenter(s) for the following service(s) Advanced Analytics. Full details can be found on the support portal.

  3. monitoring Aug 11, 2025, 03:39 PM UTC

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

  4. resolved Aug 11, 2025, 04:38 PM UTC

    The incident has been resolved

Read the full incident report →

Minor August 6, 2025

Service Impact to JED2 Data Center.

Detected by Pingoru
Aug 06, 2025, 07:14 PM UTC
Resolved
Aug 07, 2025, 01:10 AM UTC
Duration
5h 56m
Affected: JED2 — Jeddah, Saudi Arabia
Timeline · 6 updates
  1. investigating Aug 06, 2025, 07:14 PM UTC

    We are currently investigating this issue.

  2. resolved Aug 06, 2025, 07:14 PM UTC

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

  3. monitoring Aug 06, 2025, 08:05 PM UTC

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

  4. resolved Aug 06, 2025, 09:56 PM UTC

    Netskope continues to monitor the data center before fully restoring service

  5. resolved Aug 07, 2025, 01:04 AM UTC

    The data center has been put back into operation. Netskope will continue monitoring the site

  6. resolved Aug 07, 2025, 01:10 AM UTC

    The incident has been resolved

Read the full incident report →

Critical August 5, 2025

BWAN Management and Client Connectivity in US Down

Detected by Pingoru
Aug 05, 2025, 04:26 PM UTC
Resolved
Aug 05, 2025, 06:05 PM UTC
Duration
1h 39m
Affected: ATL1 — Atlanta, United StatesATL2 — Atlanta, United StatesBOS1 — Boston, United StatesDEN1 — Denver, United StatesDFW1 — Dallas, United StatesDFW3 — Dallas, United StatesDFW4 — Dallas, United StatesIAD2 — Washington, United StatesIAD4 — Washington, United StatesJNB1 — Johannesburg, South AfricaLAX1 — Los Angeles, United StatesMIA1 — Miami, United StatesMIA2 — Miami, United StatesNYC1 — LaGuardia, United StatesNYC2 — LaGuardia, United StatesNYC3 — LaGuardia, United StatesNYC4 — LaGuardia, United StatesORD1 — Chicago, United StatesORD2 — Chicago, United StatesPHL1 — Philadelphia, United StatesPHX1 — Phoenix, United StatesSEA2 — Seattle, United StatesSFO1 — San Francisco, United StatesSJC1 — San Jose, United StatesSJC2 — San Jose, United StatesSTL1 — St. Louis, United StatesSV5 — San Jose, United States
Timeline · 5 updates
  1. investigating Aug 05, 2025, 04:26 PM UTC

    We are currently investigating this issue.

  2. resolved Aug 05, 2025, 04:26 PM UTC

    We are investigating a service impacting incident in multiple US datacenter(s) for the following service(s): SD-WAN. Full details can be found on the support portal.

  3. resolved Aug 05, 2025, 06:05 PM UTC

    The incident has been resolved

  4. monitoring Aug 05, 2025, 07:15 PM UTC

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

  5. resolved Aug 05, 2025, 07:16 PM UTC

    Netskope has mitigated the issue.

Read the full incident report →

Critical August 2, 2025

Service Impact to RUH1 Data Center.

Detected by Pingoru
Aug 02, 2025, 07:30 PM UTC
Resolved
Aug 02, 2025, 09:30 PM UTC
Duration
2h
Affected: JED1 — Jeddah, Saudi ArabiaJED2 — Jeddah, Saudi Arabia
Timeline · 3 updates
  1. investigating Aug 02, 2025, 07:30 PM UTC

    We are currently investigating this issue.

  2. resolved Aug 02, 2025, 07:30 PM UTC

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

  3. resolved Aug 02, 2025, 09:30 PM UTC

    The incident has been resolved

Read the full incident report →

Major July 1, 2025

Service Impact to HYD1 Data Center.

Detected by Pingoru
Jul 01, 2025, 10:10 PM UTC
Resolved
Jul 01, 2025, 11:30 PM UTC
Duration
1h 20m
Affected: HYD1 — Hyderabad, India
Timeline · 4 updates
  1. investigating Jul 01, 2025, 10:10 PM UTC

    We are currently investigating this issue.

  2. resolved Jul 01, 2025, 10:10 PM UTC

    Netskope considers this incident fully resolved following thorough monitoring.

  3. monitoring Jul 01, 2025, 11:07 PM UTC

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

  4. resolved Jul 01, 2025, 11:30 PM UTC

    The incident has been resolved

Read the full incident report →

Minor June 27, 2025

Service Impact to MIA2 Data Center.

Detected by Pingoru
Jun 27, 2025, 09:12 PM UTC
Resolved
Jun 28, 2025, 03:09 AM UTC
Duration
5h 57m
Affected: MIA2 — Miami, United States
Timeline · 7 updates
  1. investigating Jun 27, 2025, 09:12 PM UTC

    We are currently investigating this issue.

  2. resolved Jun 27, 2025, 09:12 PM UTC

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

  3. resolved Jun 27, 2025, 10:07 PM UTC

    The site vendor has confirmed the energy issue is now resolved. Netskope is working on bringing the site back to operational status

  4. resolved Jun 27, 2025, 11:27 PM UTC

    Netskope team continues to work in bringing the site back to operation.

  5. resolved Jun 28, 2025, 12:43 AM UTC

    Netskope continues to work on restoring the services

  6. monitoring Jun 28, 2025, 01:28 AM UTC

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

  7. resolved Jun 28, 2025, 03:09 AM UTC

    The incident has been resolved

Read the full incident report →

Critical June 16, 2025

Performance degradation in Europe region

Detected by Pingoru
Jun 16, 2025, 08:45 AM UTC
Resolved
Jun 16, 2025, 09:45 AM UTC
Duration
1h
Affected: BCN1 — Barcelona, SpainDUB1 — Dublin, IrelandMAD1 — Madrid, SpainMAD2 — Madrid, SpainMAN1 — Manchester, United KingdomMIL2 — Milan, Italy
Timeline · 3 updates
  1. investigating Jun 16, 2025, 08:45 AM UTC

    We are currently investigating this issue.

  2. resolved Jun 16, 2025, 08:45 AM UTC

    We are investigating a performance degradation at the multiple datacenter(s) in Europe region for the Secure Web Gateway. Full details can be found on the support portal.

  3. resolved Jun 16, 2025, 09:45 AM UTC

    The incident has been resolved

Read the full incident report →

Critical June 16, 2025

Service Impact to BOM1, BOM2, DEL1, DEL2, HYD1, MAA1, MAA2 Data Center.

Detected by Pingoru
Jun 16, 2025, 08:30 AM UTC
Resolved
Jun 16, 2025, 10:00 AM UTC
Duration
1h 30m
Affected: BOM1 — Mumbai, IndiaBOM2 — Mumbai, IndiaDEL1 — Delhi, IndiaDEL2 — Delhi, IndiaHYD1 — Hyderabad, IndiaMAA1 — Chennai, IndiaMAA2 — Chennai, India
Timeline · 4 updates
  1. investigating Jun 16, 2025, 08:30 AM UTC

    We are currently investigating this issue.

  2. resolved Jun 16, 2025, 08:30 AM UTC

    We are investigating a service impacting incident at the BOM1, BOM2, DEL1, DEL2, HYD1, MAA1, MAA2 datacenter(s) for the following service(s) GSLB. Full details can be found on the support portal.

  3. resolved Jun 16, 2025, 09:32 AM UTC

    Netskope has identified the potential root cause and is working on a resolution strategy.

  4. resolved Jun 16, 2025, 10:00 AM UTC

    The incident has been resolved

Read the full incident report →

Major June 13, 2025

Service Impact to BOM1, BOM2, CCU1, DEL1, DEL2, HYD1, MAA1, MAA2 Data Center.

Detected by Pingoru
Jun 13, 2025, 10:32 AM UTC
Resolved
Jun 13, 2025, 12:15 PM UTC
Duration
1h 43m
Affected: BOM1 — Mumbai, IndiaBOM2 — Mumbai, IndiaCCU1 — Kolkata, IndiaDEL1 — Delhi, IndiaDEL2 — Delhi, IndiaHYD1 — Hyderabad, IndiaMAA1 — Chennai, IndiaMAA2 — Chennai, India
Timeline · 4 updates
  1. investigating Jun 13, 2025, 10:32 AM UTC

    We are currently investigating this issue.

  2. resolved Jun 13, 2025, 10:32 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) GSLB. Full details can be found on the support portal.

  3. resolved Jun 13, 2025, 12:04 PM UTC

    Netskope has identified the potential root cause and is working on mitigation strategy.

  4. resolved Jun 13, 2025, 12:15 PM UTC

    The incident has been resolved

Read the full incident report →

Major May 28, 2025

Service Impact to NRT3 Data Center.

Detected by Pingoru
May 28, 2025, 07:20 AM UTC
Resolved
May 28, 2025, 01:10 PM UTC
Duration
5h 50m
Affected: NRT3 — Tokyo, Japan
Timeline · 5 updates
  1. investigating May 28, 2025, 07:20 AM UTC

    We are currently investigating this issue.

  2. resolved May 28, 2025, 07:20 AM UTC

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

  3. resolved May 28, 2025, 08:06 AM UTC

    Netskope has performed configuration changes to ensure all new CFW connections for GSLB enabled tenants will be routed to alternate POPs in the NewEdge traffic management.

  4. monitoring May 28, 2025, 08:36 AM UTC

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

  5. resolved May 28, 2025, 01:10 PM UTC

    The incident has been resolved

Read the full incident report →

Major May 23, 2025

Service Impact to SJC1, SJC2 Data Center.

Detected by Pingoru
May 23, 2025, 03:35 AM UTC
Resolved
May 23, 2025, 06:35 AM UTC
Duration
3h
Affected: SJC1 — San Jose, United StatesSJC2 — San Jose, United States
Timeline · 3 updates
  1. investigating May 23, 2025, 03:35 AM UTC

    We are currently investigating this issue.

  2. resolved May 23, 2025, 03:35 AM UTC

    We are investigating a service impacting incident at the SJC1, SJC2 datacenter(s) for the following service(s) Incident Management System. Full details can be found on the support portal.

  3. resolved May 23, 2025, 06:35 AM UTC

    The incident has been resolved

Read the full incident report →

Minor May 20, 2025

Service Impact to YYZ1 Data Center.

Detected by Pingoru
May 20, 2025, 01:00 PM UTC
Resolved
May 20, 2025, 02:30 PM UTC
Duration
1h 30m
Affected: YYZ1 — Toronto, Canada
Timeline · 3 updates
  1. investigating May 20, 2025, 01:00 PM UTC

    We are currently investigating this issue.

  2. resolved May 20, 2025, 01:00 PM UTC

    We are investigating a service impacting incident at the YYZ1 datacenter(s) for the following service(s) Secure Web Gateway. Customers steering traffic to YYZ1 and utilizing Netskope's DEIP (dedicated egress IP) service are impacted.

  3. resolved May 20, 2025, 02:30 PM UTC

    The incident has been resolved

Read the full incident report →

Critical May 7, 2025

Service Impact to SJC2, LON3, MEL2, ZUR2, SIN2, RUH1 and FRA2 Data Centers.

Detected by Pingoru
May 07, 2025, 01:02 AM UTC
Resolved
May 07, 2025, 03:10 AM UTC
Duration
2h 8m
Affected: FRA2 — Frankfurt, GermanyLON3 — London, United KingdomMEL2 — Melbourne, AustraliaRUH1 — Riyadh, Saudi ArabiaSIN2 — Singapore, SingaporeSJC2 — San Jose, United StatesZUR2 — Zurich, Switzerland
Timeline · 6 updates
  1. investigating May 07, 2025, 01:02 AM UTC

    We are currently investigating this issue.

  2. resolved May 07, 2025, 01:02 AM UTC

    We are investigating a service impacting incident at the SJC2, LON3, MEL2, ZUR2, SIN2, RUH1 and FRA2 datacenters. Full details can be found on the support portal.

  3. resolved May 07, 2025, 02:47 AM UTC

    During the investigation, Netskope identified that the issue also impacted ZUR2 and SIN2 management planes. We are actively investigating the issue.

  4. resolved May 07, 2025, 02:53 AM UTC

    Netskope has identified that the issue has a global impact and also affects the RUH1 management plane.

  5. resolved May 07, 2025, 03:07 AM UTC

    Netskope identified the impact to be global, also affecting impacting FRA2 management plane. Netskope continues to investigate the issue.

  6. resolved May 07, 2025, 03:10 AM UTC

    The incident has been resolved

Read the full incident report →

Major April 11, 2025

Service Impact to G-Suite applications in All DPs (Data Center).

Detected by Pingoru
Apr 11, 2025, 09:40 AM UTC
Resolved
Apr 11, 2025, 12:00 PM UTC
Duration
2h 20m
Timeline · 5 updates
  1. investigating Apr 11, 2025, 09:40 AM UTC

    We are currently investigating this issue.

  2. resolved Apr 11, 2025, 09:40 AM UTC

    We are investigating a service impacting incident at the All DPs datacenter(s) for the G-suite applications. Full details can be found on the support portal.

  3. monitoring Apr 11, 2025, 11:41 AM UTC

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

  4. resolved Apr 11, 2025, 11:44 AM UTC

    Netskope has identified a potential root cause and recommends disabling a specific Chrome flag to mitigate the impact. Please see more details on the support portal

  5. resolved Apr 11, 2025, 12:00 PM UTC

    The incident has been resolved

Read the full incident report →

Critical April 4, 2025

Service Impact to SAO3 Data Center.

Detected by Pingoru
Apr 04, 2025, 08:55 PM UTC
Resolved
Apr 04, 2025, 09:18 PM UTC
Duration
23m
Affected: SAO3 — São Paulo, Brazil
Timeline · 4 updates
  1. investigating Apr 04, 2025, 08:55 PM UTC

    We are currently investigating this issue.

  2. resolved Apr 04, 2025, 08:55 PM UTC

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

  3. resolved Apr 04, 2025, 09:18 PM UTC

    The incident has been resolved

  4. monitoring Apr 04, 2025, 10:09 PM UTC

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

Read the full incident report →

Major April 3, 2025

Service Impact to PHX1 Data Center.

Detected by Pingoru
Apr 03, 2025, 03:14 AM UTC
Resolved
Apr 03, 2025, 05:50 AM UTC
Duration
2h 36m
Affected: PHX1 — Phoenix, United States
Timeline · 3 updates
  1. investigating Apr 03, 2025, 03:14 AM UTC

    We are currently investigating this issue.

  2. resolved Apr 03, 2025, 03:14 AM UTC

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

  3. resolved Apr 03, 2025, 05:50 AM UTC

    The incident has been resolved

Read the full incident report →

Critical March 24, 2025

Service Impact to SYD1, SYD2 Data Center.

Detected by Pingoru
Mar 24, 2025, 02:17 AM UTC
Resolved
Mar 24, 2025, 05:16 AM UTC
Duration
2h 59m
Affected: SYD1 — Sydney, AustraliaSYD2 — Sydney, Australia
Timeline · 5 updates
  1. investigating Mar 24, 2025, 02:17 AM UTC

    We are currently investigating this issue.

  2. resolved Mar 24, 2025, 02:17 AM UTC

    We are investigating a service impacting incident at the SYD1, SYD2 datacenter(s) for the following service(s) Core Services. Full details can be found on the support portal.

  3. resolved Mar 24, 2025, 04:36 AM UTC

    Netskope has identified a potential issue related to a specific transit path and Netskope is actively working to route traffic through an alternate path to restore optimal performance.

  4. resolved Mar 24, 2025, 05:04 AM UTC

    Netskope has adjusted traffic routing through an alternate path to restore optimal performance and is currently monitoring to confirm the resolution.

  5. resolved Mar 24, 2025, 05:16 AM UTC

    The incident has been resolved

Read the full incident report →