Netskope incident

Service Impact to FR4 Data Center.

Critical Resolved View vendor source →

Netskope experienced a critical incident on February 6, 2025 affecting FR4 — Frankfurt, Germany, lasting 1d. The incident has been resolved; the full update timeline is below.

Started
Feb 06, 2025, 06:18 PM UTC
Resolved
Feb 07, 2025, 06:47 PM UTC
Duration
1d
Detected by Pingoru
Feb 06, 2025, 06:18 PM UTC

Affected components

FR4 — Frankfurt, Germany

Update timeline

  1. investigating Feb 06, 2025, 06:18 PM UTC

    We are currently investigating this issue.

  2. resolved Feb 06, 2025, 06:18 PM UTC

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

  3. resolved Feb 06, 2025, 07:01 PM UTC

    Netskope has identified a potential root cause and is implementing a mitigation strategy

  4. resolved Feb 06, 2025, 07:47 PM UTC

    Netskope continues to work on the mitigation strategy

  5. resolved Feb 06, 2025, 09:04 PM UTC

    Netskope continues to work on the mitigation strategy

  6. resolved Feb 06, 2025, 10:48 PM UTC

    The mitigation strategy has been implemented and its being validated

  7. resolved Feb 07, 2025, 02:58 AM UTC

    Unfortunately, the deployed fix did not work as intended, Netskope continues to work towards the mitigation strategy

  8. resolved Feb 07, 2025, 06:47 AM UTC

    Netskope is actively working towards resolving the issue

  9. resolved Feb 07, 2025, 09:50 AM UTC

    Additional measures implemented to address this incident are currently being monitored

  10. resolved Feb 07, 2025, 01:58 PM UTC

    Netskope continues to monitor to ensure that the mitigation strategy has been successful. No issues have been detected at this time.

  11. resolved Feb 07, 2025, 04:48 PM UTC

    Netskope continues to monitor and there have been no further signs of degradation after implementing the previous mitigation strategy. Netskope is performing additional checks before confirming the issue is fully mitigated and resolved at this time.

  12. resolved Feb 07, 2025, 06:47 PM UTC

    The incident has been resolved