Netskope Outage History

Netskope is up right now

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

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

Source: https://trust.netskope.com

Critical March 7, 2025

Service Impact to BSB1 Data Center.

Detected by Pingoru
Mar 07, 2025, 05:50 PM UTC
Resolved
Mar 07, 2025, 07:46 PM UTC
Duration
1h 56m
Affected: BSB1 — Brasília, Brazil
Timeline · 7 updates
  1. investigating Mar 07, 2025, 05:50 PM UTC

    We are currently investigating this issue.

  2. resolved Mar 07, 2025, 05:50 PM UTC

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

  3. resolved Mar 07, 2025, 06:05 PM UTC

    Netskope has removed the NPA gateway service from NewEdge for BSB1 to allow users to connect to alternative data centers.

  4. resolved Mar 07, 2025, 06:25 PM UTC

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

  5. resolved Mar 07, 2025, 06:51 PM UTC

    Netskope has completed implementation of the fix. BSB1 NPA service is being re-introduced into NewEdge.

  6. monitoring Mar 07, 2025, 06:57 PM UTC

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

  7. resolved Mar 07, 2025, 07:46 PM UTC

    The incident has been resolved

Read the full incident report →

Major March 7, 2025

Service Impact to SYD1 Data Center.

Detected by Pingoru
Mar 07, 2025, 01:30 PM UTC
Resolved
Mar 08, 2025, 02:30 AM UTC
Duration
13h
Affected: SYD1 — Sydney, Australia
Timeline · 3 updates
  1. investigating Mar 07, 2025, 01:30 PM UTC

    We are currently investigating this issue.

  2. resolved Mar 07, 2025, 01:30 PM UTC

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

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

    The incident has been resolved

Read the full incident report →

Critical March 3, 2025

Service Impact to ORD2 Data Center.

Detected by Pingoru
Mar 03, 2025, 10:16 PM UTC
Resolved
Mar 03, 2025, 10:40 PM UTC
Duration
24m
Affected: ORD2 — Chicago, United States
Timeline · 3 updates
  1. investigating Mar 03, 2025, 10:16 PM UTC

    We are currently investigating this issue.

  2. resolved Mar 03, 2025, 10:16 PM UTC

    We are investigating a service impacting incident at the ORD2 datacenter(s) for the following service(s) Remote Browser Isolation. Full details can be found on the support portal.

  3. resolved Mar 03, 2025, 10:40 PM UTC

    The incident has been resolved

Read the full incident report →

Minor January 22, 2025

Service Impact to AM2, FR4, LON3, SV5 Data Center.

Detected by Pingoru
Jan 22, 2025, 11:28 AM UTC
Resolved
Jan 24, 2025, 06:46 AM UTC
Duration
1d 19h
Affected: AM2 — Amsterdam, NetherlandsFR4 — Frankfurt, GermanyLON3 — London, United KingdomSV5 — San Jose, United States
Timeline · 3 updates
  1. resolved Jan 22, 2025, 11:28 AM UTC

    We are investigating a service impacting incident at the AM2, FR4, LON3, SV5 datacenter(s) for the following service(s) SMTP Data Protection. Full details can be found on the support portal.

  2. investigating Jan 22, 2025, 12:25 PM UTC

    We are currently investigating this issue.

  3. resolved Jan 24, 2025, 06:46 AM UTC

    The incident has been resolved

Read the full incident report →

Critical January 21, 2025

Service Impact to AKL1, BNE1, MEL1, MEL2, SYD1, SYD2 Data Center.

Detected by Pingoru
Jan 21, 2025, 10:30 PM UTC
Resolved
Jan 22, 2025, 02:10 AM UTC
Duration
3h 40m
Affected: AKL1 — Auckland, New ZealandBNE1 — Brisbane, AustraliaMEL1 — Melbourne, AustraliaMEL2 — Melbourne, AustraliaSYD1 — Sydney, AustraliaSYD2 — Sydney, Australia
Timeline · 3 updates
  1. investigating Jan 21, 2025, 10:30 PM UTC

    We are currently investigating this issue.

  2. resolved Jan 21, 2025, 10:30 PM UTC

    We are investigating a service impacting incident at the AKL1, BNE1, MEL1, MEL2, SYD1, SYD2 datacenter(s) for the following service(s) Private Access. Full details can be found on the support portal.

  3. resolved Jan 22, 2025, 02:10 AM UTC

    The incident has been resolved

Read the full incident report →

Major November 20, 2024

Service Impact to AM2, FRA1, MAD1, PAR2 Data Center.

Detected by Pingoru
Nov 20, 2024, 04:20 PM UTC
Resolved
Nov 20, 2024, 08:29 PM UTC
Duration
4h 9m
Affected: AM2 — Amsterdam, NetherlandsFRA1 — Frankfurt, GermanyMAD1 — Madrid, SpainPAR2 — Paris, France
Timeline · 3 updates
  1. resolved Nov 20, 2024, 04:20 PM UTC

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

  2. investigating Nov 20, 2024, 04:21 PM UTC

    We are currently investigating this issue.

  3. resolved Nov 20, 2024, 08:29 PM UTC

    The incident has been resolved

Read the full incident report →

Major October 29, 2024

Service Impact to Cloud AWS, BNE1, MEL1, MEL3, PER1, SYD1 Data Center.

Detected by Pingoru
Oct 29, 2024, 11:00 PM UTC
Resolved
Oct 30, 2024, 01:15 AM UTC
Duration
2h 15m
Affected: BNE1 — Brisbane, AustraliaMEL1 — Melbourne, AustraliaMEL3 — Melbourne, AustraliaPER1 — Perth, AustraliaSYD1 — Sydney, Australia
Timeline · 3 updates
  1. resolved Oct 29, 2024, 11:00 PM UTC

    We are investigating a service impacting incident at the Cloud AWS, BNE1, MEL1, MEL3, PER1, SYD1 datacenter(s) for the following service(s) Secure Web Gateway. Full details can be found on the support portal.

  2. resolved Oct 30, 2024, 01:15 AM UTC

    The incident has been resolved

  3. investigating Oct 30, 2024, 01:53 AM UTC

    We are currently investigating this issue.

Read the full incident report →

Major October 27, 2024

Service Impact to TPE1 Data Center.

Detected by Pingoru
Oct 27, 2024, 11:00 PM UTC
Resolved
Nov 06, 2024, 08:09 AM UTC
Duration
9d 9h
Affected: TPE1 — Taipei, Taiwan
Timeline · 3 updates
  1. resolved Oct 27, 2024, 11:00 PM UTC

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

  2. investigating Nov 06, 2024, 07:45 AM UTC

    We are currently investigating this issue.

  3. resolved Nov 06, 2024, 08:09 AM UTC

    The incident has been resolved

Read the full incident report →

Major October 21, 2024

Service Impact to SIN1 Data Center.

Detected by Pingoru
Oct 21, 2024, 11:30 AM UTC
Resolved
Oct 29, 2024, 01:00 AM UTC
Duration
7d 13h
Affected: SIN1 — Singapore, Singapore
Timeline · 3 updates
  1. resolved Oct 21, 2024, 11:30 AM UTC

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

  2. resolved Oct 29, 2024, 01:00 AM UTC

    The incident has been resolved

  3. investigating Oct 29, 2024, 07:59 AM UTC

    We are currently investigating this issue.

Read the full incident report →