Netskope Outage History

Netskope is up right now

Netskope had 75 outages in the last 2 years totaling 519h 46m of downtime — averaging 3.1 incidents per month.

There were 75 Netskope outages since October 11, 2025 totaling 519h 46m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://trust.netskope.com

Major October 20, 2026

Service Impact to US-BWAN Data Center.

Detected by Pingoru
Oct 20, 2026, 06:20 PM UTC
Resolved
Oct 20, 2026, 08:58 PM UTC
Duration
2h 38m
Affected: US-BWAN
Timeline · 5 updates
  1. investigating Oct 20, 2026, 06:20 PM UTC

    We are currently investigating this issue.

  2. monitoring Oct 20, 2026, 06:20 PM UTC

    We are investigating a service impacting incident at the US-BWAN 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.

  3. monitoring Oct 20, 2026, 06:38 PM UTC

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

  4. monitoring Oct 20, 2026, 07:43 PM UTC

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

  5. resolved Oct 20, 2026, 08:58 PM UTC

    The incident has been resolved.

Read the full incident report →

Major October 14, 2026

Service Impact to SV5 Data Center.

Detected by Pingoru
Oct 14, 2026, 07:37 PM UTC
Resolved
Oct 14, 2026, 10:10 PM UTC
Duration
2h 33m
Affected: SV5 — San Jose, United States
Timeline · 6 updates
  1. investigating Oct 14, 2026, 07:37 PM UTC

    We are currently investigating this issue.

  2. resolved Oct 14, 2026, 07:37 PM UTC

    We are investigating a service impacting incident at the SV5 datacenter(s) for the following service(s) DEM. Additional details on the scope of impact are currently being assessed and will be provided within the support portal once an article is provided.

  3. monitoring Oct 14, 2026, 08:08 PM UTC

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

  4. resolved Oct 14, 2026, 08:57 PM UTC

    Netskope continues to monitor the platform

  5. monitoring Oct 14, 2026, 09:48 PM UTC

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

  6. resolved Oct 14, 2026, 10:10 PM UTC

    The incident has been resolved.

Read the full incident report →

Critical October 9, 2026

Service Impact to SJC2 Data Center.

Detected by Pingoru
Oct 09, 2026, 02:45 PM UTC
Resolved
Oct 09, 2026, 07:11 PM UTC
Duration
4h 26m
Affected: SJC2 — San Jose, United States
Timeline · 6 updates
  1. investigating Oct 09, 2026, 02:45 PM UTC

    We are currently investigating this issue.

  2. resolved Oct 09, 2026, 02:45 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 Oct 09, 2026, 03:28 PM UTC

    Netskope continues to investigate the issue

  4. monitoring Oct 09, 2026, 04:04 PM UTC

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

  5. monitoring Oct 09, 2026, 04:53 PM UTC

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

  6. resolved Oct 09, 2026, 07:11 PM UTC

    The incident has been resolved.

Read the full incident report →

Major October 9, 2026

Service Impact to FRA2 Data Center.

Detected by Pingoru
Oct 09, 2026, 09:42 AM UTC
Resolved
Oct 09, 2026, 11:43 AM UTC
Duration
2h 1m
Affected: FRA2 — Frankfurt, Germany
Timeline · 4 updates
  1. investigating Oct 09, 2026, 09:42 AM UTC

    We are currently investigating this issue.

  2. resolved Oct 09, 2026, 09:42 AM UTC

    We are investigating a service impacting incident at the FRA2 datacenter(s) for the following service(s) Management Console WebUI. Additional details on the scope of impact are currently being assessed and will be provided within the support portal once an article is provided.

  3. monitoring Oct 09, 2026, 10:07 AM UTC

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

  4. resolved Oct 09, 2026, 11:43 AM UTC

    The incident has been resolved.

Read the full incident report →

Major October 8, 2026

Service Impact to All MP Data Center.

Detected by Pingoru
Oct 08, 2026, 09:48 PM UTC
Resolved
Oct 08, 2026, 11:01 PM UTC
Duration
1h 13m
Timeline · 5 updates
  1. investigating Oct 08, 2026, 09:48 PM UTC

    We are currently investigating this issue.

  2. resolved Oct 08, 2026, 09:48 PM UTC

    We are investigating a service impacting incident at the SJC1 datacenter(s) for the following service(s) All Services, Event Logging. Additional details on the scope of impact are currently being assessed and will be provided within the support portal once an article is provided.

  3. monitoring Oct 08, 2026, 10:14 PM UTC

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

  4. monitoring Oct 08, 2026, 10:40 PM UTC

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

  5. resolved Oct 08, 2026, 11:01 PM UTC

    The incident has been resolved.

Read the full incident report →

Major October 8, 2026

Service Impact to BWAN Management UI - Specific MPs

Detected by Pingoru
Oct 08, 2026, 03:29 PM UTC
Resolved
Oct 08, 2026, 06:54 PM UTC
Duration
3h 25m
Affected: AM2 — Amsterdam, NetherlandsFR4 — Frankfurt, GermanyRUH1 — Riyadh, Saudi ArabiaSIN2 — Singapore, SingaporeZUR2 — Zurich, Switzerland
Timeline · 5 updates
  1. investigating Oct 08, 2026, 03:29 PM UTC

    We are currently investigating this issue.

  2. resolved Oct 08, 2026, 03:29 PM UTC

    We are investigating a service impacting incident affecting certain management plane data centers including SIN2, FR4, AM2, RUH1, and ZUR2 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.

  3. monitoring Oct 08, 2026, 05:29 PM UTC

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

  4. monitoring Oct 08, 2026, 06:23 PM UTC

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

  5. resolved Oct 08, 2026, 06:54 PM UTC

    The incident has been resolved.

Read the full incident report →

Critical October 6, 2026

Service Impact to DFW3 Data Center.

Detected by Pingoru
Oct 06, 2026, 09:42 PM UTC
Resolved
Oct 06, 2026, 10:44 PM UTC
Duration
1h 2m
Affected: DFW3 — Dallas, United States
Timeline · 5 updates
  1. investigating Oct 06, 2026, 09:42 PM UTC

    We are currently investigating this issue.

  2. resolved Oct 06, 2026, 09:42 PM UTC

    We are investigating a service impacting incident at the DFW3 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.

  3. monitoring Oct 06, 2026, 09:42 PM UTC

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

  4. monitoring Oct 06, 2026, 09:59 PM UTC

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

  5. resolved Oct 06, 2026, 10:44 PM UTC

    The incident has been resolved.

Read the full incident report →

Major September 27, 2026

Service Impact to SJC1 Data Center.

Detected by Pingoru
Sep 27, 2026, 08:04 AM UTC
Resolved
Sep 27, 2026, 10:18 AM UTC
Duration
2h 14m
Affected: SJC1 — San Jose, United States
Timeline · 5 updates
  1. investigating Sep 27, 2026, 08:04 AM UTC

    We are currently investigating this issue.

  2. resolved Sep 27, 2026, 08:04 AM UTC

    We are investigating a service impacting incident at the SJC1 datacenter(s) for the following service(s) CASB API Data Protection. 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 Sep 27, 2026, 08:38 AM UTC

    Netskope continues to investigate an anomaly identified in the SJC1 Management Plane.

  4. monitoring Sep 27, 2026, 09:55 AM UTC

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

  5. resolved Sep 27, 2026, 10:18 AM UTC

    The incident has been resolved.

Read the full incident report →

Major September 26, 2026

Service Impact to All DPs Data Center.

Detected by Pingoru
Sep 26, 2026, 04:22 AM UTC
Resolved
Sep 26, 2026, 06:10 AM UTC
Duration
1h 48m
Timeline · 5 updates
  1. investigating Sep 26, 2026, 04:22 AM UTC

    We are currently investigating this issue.

  2. resolved Sep 26, 2026, 04:22 AM UTC

    We are investigating a service impacting incident at the All DPs datacenter(s) for the following service(s) NPA Clientless Access. Additional details on the scope of impact are currently being assessed and will be provided within the support portal once an article is provided.

  3. resolved Sep 26, 2026, 04:47 AM UTC

    Netskope has identified the root cause of the interruption and is actively working to implement the required mitigation to restore normal service.

  4. monitoring Sep 26, 2026, 04:57 AM UTC

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

  5. resolved Sep 26, 2026, 06:10 AM UTC

    The incident has been resolved.

Read the full incident report →

Major September 22, 2026

Service Impact to SIN1, SIN3 Data Center.

Detected by Pingoru
Sep 22, 2026, 03:45 PM UTC
Resolved
Sep 28, 2026, 02:08 PM UTC
Duration
5d 22h
Affected: SIN1 — Singapore, SingaporeSIN3 — Singapore, Singapore
Timeline · 8 updates
  1. investigating Sep 22, 2026, 03:45 PM UTC

    We are currently investigating this issue.

  2. resolved Sep 22, 2026, 03:45 PM UTC

    We are investigating a service impacting incident at the SIN1, SIN3 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.

  3. resolved Sep 22, 2026, 09:09 PM UTC

    Netskope continues to actively monitor for status updates from several affected transit providers.

  4. resolved Sep 23, 2026, 03:46 AM UTC

    Netskope continues to monitor transit provider updates while platform engineering teams work with backbone partners to optimize traffic rerouting around the confirmed undersea fiber cuts.

  5. resolved Sep 23, 2026, 01:59 PM UTC

    Netskope has received reports that improvements have been seen through various changes made by the transit providers. More information can be found in the support portal.

  6. resolved Sep 24, 2026, 01:35 PM UTC

    Netskope has not received any new information or updates on the status of the undersea repairs at this time and will continue to actively monitor for any changes.

  7. monitoring Sep 28, 2026, 01:08 PM UTC

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

  8. resolved Sep 28, 2026, 02:08 PM UTC

    The incident has been resolved.

Read the full incident report →

Critical September 17, 2026

Service Impact to LON2 Data Center.

Detected by Pingoru
Sep 17, 2026, 05:20 PM UTC
Resolved
Sep 17, 2026, 05:26 PM UTC
Duration
6m
Affected: LON2 — London, United Kingdom
Timeline · 3 updates
  1. investigating Sep 17, 2026, 05:20 PM UTC

    We are currently investigating this issue.

  2. resolved Sep 17, 2026, 05:20 PM UTC

    Netskope identified a service impacting incident that occurred earlier today at the LON2 datacenter(s) for the following service(s) Data Protection. Additional details on the scope of impact are available within the provided link to the corresponding support portal article. The incident and impact is fully resolved at this point in time.

  3. resolved Sep 17, 2026, 05:26 PM UTC

    The incident has been resolved.

Read the full incident report →

Major September 8, 2026

Service Impact to IAD2, IAD4, ORD2 Data Center.

Detected by Pingoru
Sep 08, 2026, 11:24 AM UTC
Resolved
Sep 08, 2026, 01:10 PM UTC
Duration
1h 46m
Affected: IAD2 — Washington, United StatesIAD4 — Washington, United StatesORD2 — Chicago, United States
Timeline · 5 updates
  1. investigating Sep 08, 2026, 11:24 AM UTC

    We are currently investigating this issue.

  2. resolved Sep 08, 2026, 11:24 AM UTC

    We are investigating a service impacting incident at the IAD2, IAD4, ORD2 datacenter(s) for the following service(s) NPA Stitcher. Additional details on the scope of impact are currently being assessed and will be provided within the support portal once an article is provided.

  3. resolved Sep 08, 2026, 12:30 PM UTC

    Netskope has identified an extended network route from certain locations to the affected PoPs, impacting traffic from publishers hosted on AWS infrastructure. Netskope is actively working on mitigation.

  4. monitoring Sep 08, 2026, 12:52 PM UTC

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

  5. resolved Sep 08, 2026, 01:10 PM UTC

    The incident has been resolved.

Read the full incident report →

Major September 8, 2026

Service Impact to All MPs Data Center.

Detected by Pingoru
Sep 08, 2026, 02:44 AM UTC
Resolved
Sep 08, 2026, 03:21 AM UTC
Duration
37m
Affected: AM2 — Amsterdam, NetherlandsBOM3 — Mumbai, IndiaDFW3 — Dallas, United StatesFR4 — Frankfurt, GermanyFRA2 — Frankfurt, GermanyLON3 — London, United KingdomMEL2 — Melbourne, AustraliaRUH1 — Riyadh, Saudi ArabiaSIN2 — Singapore, SingaporeSJC1 — San Jose, United StatesSJC2 — San Jose, United StatesSV5 — San Jose, United StatesZUR2 — Zurich, SwitzerlandAP-BWANAU-BWANEU-BWANKSA-BWANUS-BWAN
Timeline · 3 updates
  1. investigating Sep 08, 2026, 02:44 AM UTC

    We are currently investigating this issue.

  2. resolved Sep 08, 2026, 02:44 AM UTC

    We are investigating a service impacting incident at the All MPs 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 Sep 08, 2026, 03:21 AM UTC

    The incident has been resolved.

Read the full incident report →

Critical September 2, 2026

Service Impact to Multiple Data Centers

Detected by Pingoru
Sep 02, 2026, 02:27 PM UTC
Resolved
Sep 07, 2026, 08:00 AM UTC
Duration
4d 17h
Affected: BOS1 — Boston, United StatesDFW3 — Dallas, United StatesHNL1 — Honolulu, United StatesLAX1 — Los Angeles, United StatesLAX2 — Los Angeles, United StatesNYC2 — LaGuardia, United StatesPHX1 — Phoenix, United StatesQRO1 — Querétaro, MexicoSV5 — San Jose, United StatesYYZ1 — Toronto, CanadaYYZ3 — Toronto, Canada
Timeline · 9 updates

Read the full incident report →

Critical September 2, 2026

Service Impact to SIN2 Data Center.

Detected by Pingoru
Sep 02, 2026, 07:42 AM UTC
Resolved
Sep 02, 2026, 08:15 AM UTC
Duration
33m
Affected: SIN2 — Singapore, Singapore
Timeline · 4 updates
  1. investigating Sep 02, 2026, 07:42 AM UTC

    We are currently investigating this issue.

  2. resolved Sep 02, 2026, 07:42 AM UTC

    We are investigating a service impacting incident at the SIN2 datacenter(s) for the following service(s) Management Console WebUI. Additional details on the scope of impact are currently being assessed and will be provided within the support portal once an article is provided.

  3. monitoring Sep 02, 2026, 08:11 AM UTC

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

  4. resolved Sep 02, 2026, 08:15 AM UTC

    The incident has been resolved.

Read the full incident report →

Critical August 28, 2026

Service Impact to ATL1, BOS1, DFW1, FR4, FRA1, IAD2, LIM1, NYC2, ORD2, SAO1, SJC2, YMQ3, YYZ3 Data Center.

Detected by Pingoru
Aug 28, 2026, 01:57 PM UTC
Resolved
Aug 29, 2026, 03:37 AM UTC
Duration
13h 40m
Affected: ATL1 — Atlanta, United StatesBOS1 — Boston, United StatesDFW1 — Dallas, United StatesFR4 — Frankfurt, GermanyFRA1 — Frankfurt, GermanyIAD2 — Washington, United StatesLIM1 — Lima, PeruNYC2 — LaGuardia, United StatesORD2 — Chicago, United StatesSAO1 — São Paulo, BrazilSCL2 — Santiago, ChileYMQ3 — Montreal, CanadaYYZ3 — Toronto, Canada
Timeline · 6 updates
  1. investigating Aug 28, 2026, 01:57 PM UTC

    We are currently investigating this issue.

  2. resolved Aug 28, 2026, 01:57 PM UTC

    We are investigating a service impacting incident at the ATL1, BOS1, DFW1, FR4, FRA1, IAD2, LIM1, NYC2, ORD2, SAO1, SJC2, YMQ3, YYZ3 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.

  3. resolved Aug 28, 2026, 04:37 PM UTC

    We are continuing to monitor the fix.

  4. investigating Aug 29, 2026, 12:50 AM UTC

    We are continuing to investgate this issue.

  5. monitoring Aug 29, 2026, 02:37 AM UTC

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

  6. resolved Aug 29, 2026, 03:37 AM UTC

    The incident has been resolved.

Read the full incident report →

Major August 28, 2026

Service Impact on All Management Planes

Detected by Pingoru
Aug 28, 2026, 12:26 PM UTC
Resolved
Aug 28, 2026, 08:55 PM UTC
Duration
8h 29m
Affected: AM2 — Amsterdam, NetherlandsBOM3 — Mumbai, IndiaDFW3 — Dallas, United StatesFR4 — Frankfurt, GermanyFRA2 — Frankfurt, GermanyLON3 — London, United KingdomMEL2 — Melbourne, AustraliaRUH1 — Riyadh, Saudi ArabiaSIN2 — Singapore, SingaporeSJC1 — San Jose, United StatesSJC2 — San Jose, United StatesSV5 — San Jose, United StatesZUR2 — Zurich, SwitzerlandAP-BWANAU-BWANEU-BWANKSA-BWANUS-BWAN
Timeline · 9 updates

Read the full incident report →

Major August 27, 2026

Service Impact to AU BWAN MP Data Center.

Detected by Pingoru
Aug 27, 2026, 08:04 AM UTC
Resolved
Aug 28, 2026, 12:57 AM UTC
Duration
16h 53m
Timeline · 8 updates
  1. investigating Aug 27, 2026, 08:04 AM UTC

    We are currently investigating this issue.

  2. resolved Aug 27, 2026, 08:04 AM UTC

    We are investigating a service impacting incident at the Australia (AU) BWAN MP 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.

  3. resolved Aug 27, 2026, 02:12 PM UTC

    Netskope is working closely with our technology partner to implement mitigation measures. The next update will be provided by 7:00 PM UTC, or earlier if there are any new information to share.

  4. resolved Aug 27, 2026, 06:48 PM UTC

    Netskope continues to work diligently with the vendor to identify and implement the mitigation strategy required to resolve the issue and restore functionality. Netskope has requested an additional escalation with the vendor for visibility and support. Netskope will provide another update in two hours or as soon as an update has been provided by the vendor.

  5. resolved Aug 27, 2026, 09:38 PM UTC

    The vendor has traced the performance issues to a backend data processing backlog. Their engineering team is currently executing a mitigation strategy to clear the queue and restore normal query response times. We continue to monitor their remediation efforts and will provide further updates as service normalizes.

  6. monitoring Aug 27, 2026, 10:37 PM UTC

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

  7. monitoring Aug 28, 2026, 12:49 AM UTC

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

  8. resolved Aug 28, 2026, 12:57 AM UTC

    The incident has been resolved.

Read the full incident report →

Critical August 24, 2026

Service Impact to SJC1, SJC2, SV5 Data Center.

Detected by Pingoru
Aug 24, 2026, 11:59 PM UTC
Resolved
Aug 25, 2026, 12:57 AM UTC
Duration
58m
Affected: SJC1 — San Jose, United StatesSJC2 — San Jose, United StatesSV5 — San Jose, United States
Timeline · 5 updates
  1. investigating Aug 24, 2026, 11:59 PM UTC

    We are currently investigating this issue.

  2. resolved Aug 24, 2026, 11:59 PM UTC

    We are investigating a service impacting incident at the SJC1, SJC2, SV5 datacenter(s) for the following service(s) Advanced Analytics, CASB API Data Protection, DSPM. Additional details on the scope of impact are currently being assessed and will be provided within the support portal once an article is provided.

  3. monitoring Aug 25, 2026, 12:16 AM UTC

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

  4. monitoring Aug 25, 2026, 12:42 AM UTC

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

  5. resolved Aug 25, 2026, 12:57 AM UTC

    The incident has been resolved.

Read the full incident report →

Critical August 23, 2026

Service Impact to TLV1 Data Center.

Detected by Pingoru
Aug 23, 2026, 01:23 PM UTC
Resolved
Aug 23, 2026, 05:29 PM UTC
Duration
4h 6m
Affected: TLV1 — Tel Aviv, Israel
Timeline · 8 updates
  1. investigating Aug 23, 2026, 01:23 PM UTC

    We are currently investigating this issue.

  2. resolved Aug 23, 2026, 01:23 PM UTC

    We are investigating a service impacting incident at the TLV1 datacenter(s) for the following service(s) NPA Gateway, NPA Stitcher, Private Access, 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. monitoring Aug 23, 2026, 01:35 PM UTC

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

  4. resolved Aug 23, 2026, 02:20 PM UTC

    Netskope continues observing stable performance with no further disruptions. Our investigation indicates that the issue is tied to a local Internet Service Provider (ISP). We are actively working with them to resolve the underlying connectivity issue and restore full functionality before reintroducing the affected data center to our standard routing rotation.

  5. resolved Aug 23, 2026, 03:04 PM UTC

    ​The local ISP has confirmed that the underlying connectivity issue is resolved. Netskope is currently monitoring the environment to validate this fix. Once we verify sustained stability, we will safely reintroduce the affected data center into our standard routing rotation.

  6. resolved Aug 23, 2026, 04:09 PM UTC

    The root cause of this disruption has been identified as a fiber cut on the local ISP's network. Following their physical repairs, Netskope is now in the process of returning the affected data center to our standard routing rotation. Our engineering teams are actively conducting connectivity tests to validate performance and ensure a seamless transition for end-user traffic.

  7. monitoring Aug 23, 2026, 04:38 PM UTC

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

  8. resolved Aug 23, 2026, 05:29 PM UTC

    The incident has been resolved.

Read the full incident report →

Critical August 21, 2026

Service Impact to SMTP Data Protection Service affecting all MP's

Detected by Pingoru
Aug 21, 2026, 01:55 PM UTC
Resolved
Aug 24, 2026, 06:59 AM UTC
Duration
2d 17h
Affected: AM2 — Amsterdam, NetherlandsBOM3 — Mumbai, IndiaDFW3 — Dallas, United StatesFR4 — Frankfurt, GermanyFRA2 — Frankfurt, GermanyLON3 — London, United KingdomMEL2 — Melbourne, AustraliaRUH1 — Riyadh, Saudi ArabiaSIN2 — Singapore, SingaporeSJC1 — San Jose, United StatesSJC2 — San Jose, United StatesSV5 — San Jose, United StatesZUR2 — Zurich, SwitzerlandAP-BWANAU-BWANEU-BWANKSA-BWANUS-BWAN
Timeline · 14 updates

Read the full incident report →

Major August 20, 2026

Service Impact to BWAN firewall policy management interface

Detected by Pingoru
Aug 20, 2026, 02:43 PM UTC
Resolved
Aug 25, 2026, 07:15 AM UTC
Duration
4d 16h
Timeline · 5 updates
  1. investigating Aug 20, 2026, 02:43 PM UTC

    We are currently investigating this issue.

  2. resolved Aug 20, 2026, 02:43 PM UTC

    We are investigating a service impacting incident 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.

  3. resolved Aug 21, 2026, 08:34 PM UTC

    A fix has been created and is currently being tested before being deployed.

  4. resolved Aug 24, 2026, 07:52 AM UTC

    Netskope has developed and validated a fix for the BWAN firewall policy management interface. This fix is scheduled for deployment in the M47.4 release and the customers are advised to continue following the advisory to avoid editing existing VLAN-scoped firewall rules until the deployment is confirmed complete.

  5. resolved Aug 25, 2026, 07:15 AM UTC

    The incident has been resolved.

Read the full incident report →

Critical August 19, 2026

Service Impact to AM2, FR4 Data Center.

Detected by Pingoru
Aug 19, 2026, 11:40 PM UTC
Resolved
Aug 20, 2026, 01:30 AM UTC
Duration
1h 50m
Affected: AM2 — Amsterdam, NetherlandsFR4 — Frankfurt, Germany
Timeline · 5 updates
  1. investigating Aug 19, 2026, 11:40 PM UTC

    We are currently investigating this issue.

  2. resolved Aug 19, 2026, 11:40 PM UTC

    We are investigating a service impacting incident at the AM2, FR4 datacenter(s) for the following service(s) Core Services, Incident Management System, Management Console WebUI. Additional details on the scope of impact are currently being assessed and will be provided within the support portal once an article is provided.

  3. resolved Aug 20, 2026, 12:15 AM UTC

    Netskope is actively working to bring the remaining services back online. The recovery process is progressing steadily, and we will communicate further updates as soon as more details become available.

  4. resolved Aug 20, 2026, 01:22 AM UTC

    Services in FR4 have been restored and AM2 still in the recovery process. We are conducting additional validations across the environment and will notify you once we confirm the issue is completely mitigated.

  5. resolved Aug 20, 2026, 01:30 AM UTC

    The incident has been resolved.

Read the full incident report →

Major August 17, 2026

Service Impact to AM2, SJC1 Data Center.

Detected by Pingoru
Aug 17, 2026, 07:41 AM UTC
Resolved
Aug 17, 2026, 08:49 AM UTC
Duration
1h 8m
Affected: AM2 — Amsterdam, NetherlandsSJC1 — San Jose, United States
Timeline · 3 updates
  1. investigating Aug 17, 2026, 07:41 AM UTC

    We are currently investigating this issue.

  2. 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.

  3. resolved Aug 17, 2026, 08:49 AM UTC

    The incident has been resolved.

Read the full incident report →