Service Impact to QRO1 Data Center.

Update timeline

1. investigating Oct 22, 2026, 05:17 PM UTC

   We are currently investigating this issue.

2. investigating Oct 22, 2026, 05:17 PM UTC

   We are investigating a service impacting incident at the QRO1 datacenter(s) for the following service(s) Gateway, Proxy Chaining, 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. investigating Oct 22, 2026, 06:04 PM UTC

   Netskope continues to actively investigate the ongoing service degradation. Our engineering teams are currently gathering and analyzing additional data to pinpoint the root cause and safely implement a mitigation strategy. As soon as we have more information, we will communicate it.

4. investigating Oct 22, 2026, 07:03 PM UTC

   The investigation into the service degradation is still ongoing. Netskope is currently checking network traffic to help isolate the root cause. As soon as we have more information, we will communicate it

5. investigating Oct 22, 2026, 07:45 PM UTC

   To help minimize impact for our users, Netskope has modified routing paths to optimize traffic flow to the affected POP. While this step aims to improve performance, we are still actively working to identify the root cause of the service degradation. As soon as we have more information, we will communicate it.

6. investigating Oct 22, 2026, 08:44 PM UTC

   Following a network analysis, Netskope identified an issue with a specific ISP link (Cogent). To restore optimal service, we are currently working to reroute traffic through an alternative, healthy ISP link. We will provide an update once we have more information.

7. monitoring Oct 22, 2026, 09:27 PM UTC

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

8. monitoring Oct 22, 2026, 10:31 PM UTC

   Following the recent change to remove the affected Cogent ISP link and redirect traffic to a healthy path, several customers have reported a return to stability and optimal performance. We will continue to monitor the service overnight and gather additional feedback tomorrow morning before officially marking this incident as mitigated.

9. monitoring Oct 23, 2026, 05:01 PM UTC

   After our monitoring period this morning, additional customers have reported stable and optimal performance. We will continue to monitor the service for the next couple of hours to ensure ongoing stability before officially marking this incident as mitigated.