Netskope Outage History

Netskope is up right now

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

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

Source: https://trust.netskope.com

Major January 23, 2026

Service Impact to BOM2 Data Center.

Detected by Pingoru
Jan 23, 2026, 05:37 AM UTC
Resolved
Jan 24, 2026, 08:00 AM UTC
Duration
1d 2h
Affected: BOM2 — Mumbai, India
Timeline · 3 updates
  1. investigating Jan 23, 2026, 05:37 AM UTC

    We are currently investigating this issue.

  2. resolved Jan 23, 2026, 05:37 AM UTC

    We are investigating a service impacting incident at the BOM2 datacenter(s) for the following service(s) Cloud Access Security Broker, Netskope Client, 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 Jan 24, 2026, 08:00 AM UTC

    The incident has been resolved

Read the full incident report →

Major January 21, 2026

Service Impact to SJC2 Data Center.

Detected by Pingoru
Jan 21, 2026, 06:58 PM UTC
Resolved
Jan 22, 2026, 02:13 AM UTC
Duration
7h 15m
Affected: SJC2 — San Jose, United States
Timeline · 5 updates
  1. investigating Jan 21, 2026, 06:58 PM UTC

    We are currently investigating this issue.

  2. resolved Jan 21, 2026, 06:58 PM UTC

    We are investigating a service impacting incident at the SJC2 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 Jan 21, 2026, 08:03 PM UTC

    Netskope has identified a mitigation strategy and is currently working on validating it

  4. monitoring Jan 22, 2026, 12:51 AM UTC

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

  5. resolved Jan 22, 2026, 02:13 AM UTC

    The incident has been resolved

Read the full incident report →

Critical January 21, 2026

Service Impact to LON2, MAN1 Data Center.

Detected by Pingoru
Jan 21, 2026, 09:52 AM UTC
Resolved
Jan 21, 2026, 01:30 PM UTC
Duration
3h 38m
Affected: LON2 — London, United KingdomMAN1 — Manchester, United Kingdom
Timeline · 6 updates
  1. investigating Jan 21, 2026, 09:52 AM UTC

    We are currently investigating this issue.

  2. resolved Jan 21, 2026, 09:52 AM UTC

    We are investigating a service impacting incident at the LON2, MAN1 datacenter(s) for the following service(s) 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.

  3. resolved Jan 21, 2026, 11:01 AM UTC

    Netskope continues to investigate the issue.

  4. resolved Jan 21, 2026, 11:45 AM UTC

    Netskope identified an issue involving one of its service providers in the EU region. The issue was automatically mitigated at 11:10 UTC with no manual intervention required from Netskope. We are actively working with the service provider to complete a detailed root cause analysis and will share further updates as they become available.

  5. monitoring Jan 21, 2026, 11:46 AM UTC

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

  6. resolved Jan 21, 2026, 01:30 PM UTC

    The incident has been resolved

Read the full incident report →

Major January 19, 2026

Service Impact to AKL1 Data Center.

Detected by Pingoru
Jan 19, 2026, 11:19 PM UTC
Resolved
Jan 20, 2026, 04:00 AM UTC
Duration
4h 41m
Affected: AKL1 — Auckland, New Zealand
Timeline · 6 updates
  1. investigating Jan 19, 2026, 11:19 PM UTC

    We are currently investigating this issue.

  2. resolved Jan 19, 2026, 11:19 PM UTC

    We are investigating a service impacting incident at the AKL1 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 Jan 19, 2026, 11:45 PM UTC

    AKL1 removed from NewEdge to allow customers to connect to alternative nearby data centers while the investigation continues

  4. monitoring Jan 20, 2026, 01:07 AM UTC

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

  5. monitoring Jan 20, 2026, 01:40 AM UTC

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

  6. resolved Jan 20, 2026, 04:00 AM UTC

    The incident has been resolved

Read the full incident report →

Major December 17, 2025

Netskope Chromebook Extension Issue

Detected by Pingoru
Dec 17, 2025, 07:19 PM UTC
Resolved
Dec 17, 2025, 09:44 PM UTC
Duration
2h 25m
Timeline · 4 updates
  1. investigating Dec 17, 2025, 07:19 PM UTC

    We are currently investigating this issue.

  2. resolved Dec 17, 2025, 07:19 PM UTC

    Customers that upgraded the Netskope Chromebook Extension to v132.1.0.0 may encounter intermittent website accessibility issues.

  3. resolved Dec 17, 2025, 07:27 PM UTC

    Netskope has provided mitigation instructions via the linked support portal article. This incident will remain open for a period of time before being set to resolved.

  4. resolved Dec 17, 2025, 09:44 PM UTC

    The incident has been resolved

Read the full incident report →

Major November 28, 2025

Service Impact to LON1, LON2, MAN1 Data Center.

Detected by Pingoru
Nov 28, 2025, 08:50 AM UTC
Resolved
Nov 28, 2025, 10:40 AM UTC
Duration
1h 50m
Affected: LON1 — London, United KingdomLON2 — London, United KingdomMAN1 — Manchester, United Kingdom
Timeline · 3 updates
  1. investigating Nov 28, 2025, 08:50 AM UTC

    We are currently investigating this issue.

  2. resolved Nov 28, 2025, 08:50 AM UTC

    We are investigating a service impacting incident at the LON1, LON2, MAN1 datacenter(s) for the following service(s) IPSEC, Netskope Client, Private Access. Full details can be found on the support portal.

  3. resolved Nov 28, 2025, 10:40 AM UTC

    The incident has been resolved

Read the full incident report →

Critical November 12, 2025

Service Impact - Netskope Client - All MP data centers

Detected by Pingoru
Nov 12, 2025, 01:00 PM UTC
Resolved
Nov 19, 2025, 03:01 AM UTC
Duration
6d 14h
Timeline · 6 updates
  1. investigating Nov 12, 2025, 01:00 PM UTC

    We are currently investigating this issue.

  2. resolved Nov 12, 2025, 01:00 PM UTC

    We are investigating a service impacting incident for all MP datacenters related to the Netskope Client. Full details can be found on the support portal.

  3. resolved Nov 14, 2025, 08:06 AM UTC

    Netskope is targeting emergency hotfix release r132.0.7 to address the issue between Monday and Tuesday of next week. Netskope will provide confirmation of the hotfix availability once it has been successfully deployed to all commercial and compliance management plane environments.

  4. resolved Nov 18, 2025, 02:46 PM UTC

    Netskope has started deploying the r132.0.7 hot fix client release to all management planes beginning November 17th. Details regarding the deployment schedule, status, and recommended customer action has been updated in the support portal article. Once deployment has been completed to all management planes, the incident will be marked resolved.

  5. resolved Nov 19, 2025, 03:01 AM UTC

    The incident has been resolved

  6. resolved Nov 19, 2025, 03:01 AM UTC

    Netskope has completed the deployment of the r132.0.7 hot fix client release. The incident is now resolved.

Read the full incident report →

Critical November 8, 2025

Service Impact for NPA to several Data Centers

Detected by Pingoru
Nov 08, 2025, 12:50 AM UTC
Resolved
Nov 08, 2025, 11:13 AM UTC
Duration
10h 23m
Affected: AKL1 — Auckland, New ZealandAMS1 — Amsterdam, NetherlandsBCN1 — Barcelona, SpainBKK1 — Bangkok, ThailandBNE1 — Brisbane, AustraliaBOM1 — Mumbai, IndiaBOM2 — Mumbai, IndiaBRU1 — Brussels, BelgiumCCU1 — Kolkata, IndiaCPT1 — Cape Town, South AfricaDEL1 — Delhi, IndiaDEL2 — Delhi, IndiaDUB1 — Dublin, IrelandDUS1 — Düsseldorf, GermanyDXB1 — Dubai, United Arab EmiratesFRA1 — Frankfurt, GermanyGVA1 — Geneva, SwitzerlandHEL1 — Helsinki, FinlandHKG1 — Hong Kong, ChinaHKG2 — Hong Kong, ChinaHYD1 — Hyderabad, IndiaICN1 — Incheon, South KoreaJED1 — Jeddah, Saudi ArabiaJED2 — Jeddah, Saudi ArabiaJNB1 — Johannesburg, South AfricaKUL1 — Kuala Lumpur, MalaysiaLIS1 — Lisbon, PortugalLON1 — London, United KingdomLON2 — London, United KingdomLOS1 — Lagos, NigeriaMAA1 — Chennai, IndiaMAA2 — Chennai, IndiaMAD1 — Madrid, SpainMAD2 — Madrid, SpainMAN1 — Manchester, United KingdomMCT1 — Muscat, OmanMEL1 — Melbourne, AustraliaMEL3 — Melbourne, AustraliaMIL1 — Milan, ItalyMIL2 — Milan, ItalyMNL1 — Manila, PhilippinesMRS1 — Marseille, FranceMUC1 — Munich, GermanyNRT2 — Tokyo, JapanNRT3 — Tokyo, JapanOSA1 — Osaka, JapanOSA2 — Osaka, JapanPAR1 — Paris, FrancePAR2 — Paris, FrancePAR3 — Paris, FrancePEK1 — Beijing, ChinaPER1 — Perth, AustraliaPRG1 — Prague, Czech RepublicPVG1 — Shanghai, ChinaPVG2 — Shanghai, ChinaRUH2 — Riyadh, Saudi ArabiaSIN1 — Singapore, SingaporeSIN3 — Singapore, SingaporeSTO1 — Stockholm, SwedenSYD1 — Sydney, AustraliaSYD2 — Sydney, AustraliaSZX1 — Shenzhen, ChinaTLV1 — Tel Aviv, IsraelTPE1 — Taipei, TaiwanVIE1 — Vienna, AustriaWAW1 — Warsaw, PolandZUR1 — Zurich, Switzerland
Timeline · 6 updates
  1. investigating Nov 08, 2025, 12:50 AM UTC

    We are currently investigating this issue.

  2. resolved Nov 08, 2025, 12:50 AM UTC

    We are investigating service impacting incident at several data centers for the Private Access accessibility issue. Full details can be found on the support portal.

  3. resolved Nov 08, 2025, 02:30 AM UTC

    Netskope has identified that the issue is related to a recent NPA deployment. A rollback of the code has been completed across APAC-based DP's and we have confirmation that the issue has been resolved for those specific data centers. A roll back is now being completed within the EU-based DP's listed.

  4. resolved Nov 08, 2025, 02:40 AM UTC

    Netskope has completed the roll back activity for EU-based DP's. Testing and validation is now commencing at this time.

  5. resolved Nov 08, 2025, 03:22 AM UTC

    Validations have been completed and we have confirmed the issue has been mitigated post roll back activity. Root cause investigation remains underway.

  6. resolved Nov 08, 2025, 11:13 AM UTC

    The incident has been resolved

Read the full incident report →

Major October 31, 2025

Service Impact to LOS1 Data Center.

Detected by Pingoru
Oct 31, 2025, 01:28 PM UTC
Resolved
Nov 02, 2025, 12:44 PM UTC
Duration
1d 23h
Affected: LOS1 — Lagos, Nigeria
Timeline · 8 updates
  1. investigating Oct 31, 2025, 01:28 PM UTC

    We are currently investigating this issue.

  2. resolved Oct 31, 2025, 01:28 PM UTC

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

  3. resolved Oct 31, 2025, 01:33 PM UTC

    Netskope has removed the LOS1 data center from NewEdge to force new client connections to alternative, nearby data centers while the investigation continues into potential root cause.

  4. monitoring Oct 31, 2025, 01:57 PM UTC

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

  5. resolved Oct 31, 2025, 05:29 PM UTC

    Netskope has identified the potential root cause as linked to a fiber cut disruption within the region. A case is opened with the IX vendor and they are actively working on restoration efforts. LOS1 will remain out of NewEdge until the IX issue has been completely resolved in order to ensure customers have the fastest connectivity and lowest latency options when steering through LOS1.

  6. resolved Nov 01, 2025, 03:14 PM UTC

    Netskope has received an update from the vendor that work continues on restoration efforts to the IX issue caused by the regional fiber cut damage. Once Netskope receives confirmation that restoration of the link has been restored, testing and validation will be performed when the IX link is reactivated. Once validations are successful, Netskope will re-enable LOS1 within the NewEdge network.

  7. resolved Nov 02, 2025, 12:43 PM UTC

    The vendor has completed the necessary repairs on the fiber link issue and connectivity with the IX has been fully restored with the LOS1 data center. Upon completing validation tests, LOS1 was reintroduced back into the NewEdge network successfully. The incident is now resolved.

  8. resolved Nov 02, 2025, 12:44 PM UTC

    The incident has been resolved

Read the full incident report →

Major October 29, 2025

Service Impact to WAW1 Data Center.

Detected by Pingoru
Oct 29, 2025, 11:04 AM UTC
Resolved
Oct 30, 2025, 12:22 AM UTC
Duration
13h 18m
Affected: WAW1 — Warsaw, Poland
Timeline · 7 updates
  1. investigating Oct 29, 2025, 11:04 AM UTC

    We are currently investigating this issue.

  2. resolved Oct 29, 2025, 11:04 AM UTC

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

  3. resolved Oct 29, 2025, 11:25 AM UTC

    This issue has been mitigated by removing WAW1 from NewEdge traffic management system.

  4. monitoring Oct 29, 2025, 11:25 AM UTC

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

  5. resolved Oct 29, 2025, 02:28 PM UTC

    Netskope continues to investigate for a possible root cause of the issue and WAW1 will remain out of NewEdge until the issue has been identified and resolved.

  6. resolved Oct 30, 2025, 12:21 AM UTC

    Netskope addressed the root cause of the issue and the WAW1 POP has been reintroduced back into the NewEdge network.

  7. resolved Oct 30, 2025, 12:22 AM UTC

    The incident has been resolved

Read the full incident report →

Critical October 24, 2025

Service Impact to MAN1 Data Center.

Detected by Pingoru
Oct 24, 2025, 11:02 AM UTC
Resolved
Oct 24, 2025, 12:19 PM UTC
Duration
1h 17m
Affected: DUB1 — Dublin, IrelandMAN1 — Manchester, United Kingdom
Timeline · 4 updates
  1. investigating Oct 24, 2025, 11:02 AM UTC

    We are currently investigating this issue.

  2. resolved Oct 24, 2025, 11:02 AM UTC

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

  3. resolved Oct 24, 2025, 11:58 AM UTC

    Netskope has identified the root cause and applying a fix to mitigate the impact.

  4. resolved Oct 24, 2025, 12:19 PM UTC

    The incident has been resolved

Read the full incident report →

Major October 20, 2025

Service Impact to PVG1, SZX1 Data Center.

Detected by Pingoru
Oct 20, 2025, 02:44 AM UTC
Resolved
Oct 20, 2025, 03:05 AM UTC
Duration
21m
Affected: PVG1 — Shanghai, ChinaSZX1 — Shenzhen, China
Timeline · 3 updates
  1. investigating Oct 20, 2025, 02:44 AM UTC

    We are currently investigating this issue.

  2. resolved Oct 20, 2025, 02:44 AM UTC

    We are investigating a service impacting incident at the PVG1, SZX1 datacenter(s) for the following service(s) Gateway, GSLB, Netskope Client, NPA Gateway, NPA Stitcher, Private Access, Secure Web Gateway. Full details can be found on the support portal.

  3. resolved Oct 20, 2025, 03:05 AM UTC

    The incident has been resolved

Read the full incident report →

Major October 17, 2025

Service Impact to ORD1 Data Center.

Detected by Pingoru
Oct 17, 2025, 07:50 PM UTC
Resolved
Oct 17, 2025, 10:03 PM UTC
Duration
2h 13m
Affected: ORD1 — Chicago, United States
Timeline · 5 updates
  1. investigating Oct 17, 2025, 07:50 PM UTC

    We are currently investigating this issue.

  2. resolved Oct 17, 2025, 07:50 PM UTC

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

  3. resolved Oct 17, 2025, 08:53 PM UTC

    Netskope identified a network routing path that was contributing to service disruption. The affected route was removed, and traffic has stabilized. We are currently monitoring performance and customer impact, and no further issues have been reported since mitigation. The ORD1 POP has been returned to NewEdge network, following verification of stability.

  4. monitoring Oct 17, 2025, 08:55 PM UTC

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

  5. resolved Oct 17, 2025, 10:03 PM UTC

    The incident has been resolved

Read the full incident report →

Critical October 15, 2025

Misclassification of a Subset of Domains as Uncategorized

Detected by Pingoru
Oct 15, 2025, 12:00 PM UTC
Resolved
Oct 15, 2025, 01:30 PM UTC
Duration
1h 30m
Affected: AM2 — Amsterdam, NetherlandsSJC2 — San Jose, United States
Timeline · 3 updates
  1. investigating Oct 15, 2025, 12:00 PM UTC

    We are currently investigating this issue.

  2. resolved Oct 15, 2025, 12:00 PM UTC

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

  3. resolved Oct 15, 2025, 01:30 PM UTC

    The incident has been resolved

Read the full incident report →

Critical September 30, 2025

Service Impact to AM2, DFW3, FR4, FRA2, LON3, SJC1, SJC2 Data Center.

Detected by Pingoru
Sep 30, 2025, 03:14 PM UTC
Resolved
Oct 01, 2025, 12:21 PM UTC
Duration
21h 7m
Affected: AM2 — Amsterdam, NetherlandsDFW3 — Dallas, United StatesFR4 — Frankfurt, GermanyFRA2 — Frankfurt, GermanyLON3 — London, United KingdomSJC1 — San Jose, United StatesSJC2 — San Jose, United StatesSV5 — San Jose, United StatesZUR2 — Zurich, Switzerland
Timeline · 8 updates
  1. investigating Sep 30, 2025, 03:14 PM UTC

    We are currently investigating this issue.

  2. resolved Sep 30, 2025, 03:14 PM UTC

    We are investigating a service impacting incident at the AM2, DFW3, FR4, FRA2, LON3, SJC1, SJC2 datacenter(s) for the following service(s) Event Logging. Full details can be found on the support portal.

  3. resolved Sep 30, 2025, 03:36 PM UTC

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

  4. resolved Sep 30, 2025, 03:54 PM UTC

    Netskope has confirmed that the mitigation strategy implemented was successful in isolating the issue and preventing further impact on SkopeIT application events and alerts. Root cause investigation remains underway. Additional details can be found in the support portal.

  5. monitoring Sep 30, 2025, 04:39 PM UTC

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

  6. resolved Sep 30, 2025, 04:40 PM UTC

    Currently the platform is processing the delayed SkopeIT application events and alerts within all impacted MPs. Current estimated completion time has been provided within the support portal article. The incident will be marked resolved once all event lag has been completely processed.

  7. resolved Oct 01, 2025, 12:26 AM UTC

    The majority of MP’s have had their application event and alert lag drained. SJC1, SJC2 and DFW3 remain in a processing status with estimate of roughly 1 to 2 hours remaining.

  8. resolved Oct 01, 2025, 12:21 PM UTC

    The incident has been resolved

Read the full incident report →

Major September 26, 2025

Service Impact to NRT2 Data Center.

Detected by Pingoru
Sep 26, 2025, 12:00 AM UTC
Resolved
Sep 26, 2025, 01:11 AM UTC
Duration
1h 11m
Affected: NRT2 — Tokyo, Japan
Timeline · 3 updates
  1. investigating Sep 26, 2025, 12:00 AM UTC

    We are currently investigating this issue.

  2. resolved Sep 26, 2025, 12:00 AM UTC

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

  3. resolved Sep 26, 2025, 01:11 AM UTC

    The incident has been resolved

Read the full incident report →

Major September 24, 2025

Service Impact to PHL1 Data Center.

Detected by Pingoru
Sep 24, 2025, 04:45 PM UTC
Resolved
Sep 24, 2025, 07:47 PM UTC
Duration
3h 2m
Affected: PHL1 — Philadelphia, United States
Timeline · 4 updates
  1. investigating Sep 24, 2025, 04:45 PM UTC

    We are currently investigating this issue.

  2. resolved Sep 24, 2025, 04:45 PM UTC

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

  3. resolved Sep 24, 2025, 06:34 PM UTC

    Netskope is bringing PHL1 POP back into NewEdge rotation

  4. resolved Sep 24, 2025, 07:47 PM UTC

    The incident has been resolved

Read the full incident report →

Critical September 24, 2025

Service Impact to SJC1, SJC2, FRA2 Data Center.

Detected by Pingoru
Sep 24, 2025, 10:13 AM UTC
Resolved
Sep 24, 2025, 05:49 PM UTC
Duration
7h 36m
Affected: FRA2 — Frankfurt, GermanySJC1 — San Jose, United StatesSJC2 — San Jose, United States
Timeline · 6 updates
  1. investigating Sep 24, 2025, 10:13 AM UTC

    We are currently investigating this issue.

  2. resolved Sep 24, 2025, 10:13 AM UTC

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

  3. resolved Sep 24, 2025, 11:48 AM UTC

    Netskope has identified a widespread issue affecting one of the major global network transit carriers. Our teams are actively working with partners to optimize network paths and mitigate the impact.

  4. resolved Sep 24, 2025, 12:05 PM UTC

    Netskope has implemented a workaround to mitigate the Forensics data loss on the affected SJC1, SJC2, and FRA2 management planes, and confirms that no forensics loss has been observed since 11:20 AM UTC.

  5. monitoring Sep 24, 2025, 12:25 PM UTC

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

  6. resolved Sep 24, 2025, 05:49 PM UTC

    The incident has been resolved

Read the full incident report →

Major September 24, 2025

Service Impact to MNL1 Data Center.

Detected by Pingoru
Sep 24, 2025, 04:34 AM UTC
Resolved
Sep 24, 2025, 04:52 PM UTC
Duration
12h 18m
Affected: MNL1 — Manila, Philippines
Timeline · 5 updates
  1. investigating Sep 24, 2025, 04:34 AM UTC

    We are currently investigating this issue.

  2. resolved Sep 24, 2025, 04:34 AM UTC

    We are investigating a service impacting incident at the MNL1 datacenter(s) for the following service(s) Netskope Client, IPSec, and GRE. Full details can be found on the support portal.

  3. resolved Sep 24, 2025, 06:11 AM UTC

    During the investigation, Netskope identified that the issue may also be affecting customers steering traffic with client or IPSec/GRE methods through MNL1 POP. Hence, the IPSec/GRE services has also been disabled on MNL1, to mitigate further impact. The tunnels connected to MNL1 will failover to the secondary POP.

  4. resolved Sep 24, 2025, 01:15 PM UTC

    Netskope has identified the root cause of this issue to be wrt the routing changes on a common peering network. The validations are currently in progress after which the MNL1 POP will be re-introduced to NewEdge traffic management system.

  5. resolved Sep 24, 2025, 04:52 PM UTC

    The incident has been resolved

Read the full incident report →

Major September 16, 2025

Service Impact to DEL1 Data Center.

Detected by Pingoru
Sep 16, 2025, 07:49 AM UTC
Resolved
Sep 17, 2025, 11:30 AM UTC
Duration
1d 3h
Affected: DEL1 — Delhi, India
Timeline · 6 updates
  1. investigating Sep 16, 2025, 07:49 AM UTC

    We are currently investigating this issue.

  2. resolved Sep 16, 2025, 07:49 AM UTC

    We are investigating a service impacting incident at the DEL1 datacenter(s) for the following service(s) Cloud Firewall, Core Services, Private Access, Secure Web Gateway. Full details can be found on the support portal.

  3. resolved Sep 16, 2025, 08:26 AM UTC

    Netskope has removed DEL1 from NewEdge as a mitigation step at 08:03 UTC and is continuing to investigate the root cause.

  4. monitoring Sep 16, 2025, 08:29 AM UTC

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

  5. monitoring Sep 16, 2025, 10:36 AM UTC

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

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

    The incident has been resolved

Read the full incident report →

Critical September 15, 2025

Misclassification of a Subset of Domains as Unknown/Uncategorized

Detected by Pingoru
Sep 15, 2025, 01:00 PM UTC
Resolved
Sep 15, 2025, 04:20 PM UTC
Duration
3h 20m
Timeline · 3 updates
  1. investigating Sep 15, 2025, 01:00 PM UTC

    We are currently investigating this issue.

  2. resolved Sep 15, 2025, 01:00 PM UTC

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

  3. resolved Sep 15, 2025, 04:20 PM UTC

    The incident has been resolved

Read the full incident report →