Resolved after 8 hours 31 minutes, affecting AM2 — Amsterdam, Netherlands and MEL2 — Melbourne, Australia and 1 more, on May 19, 2026.
The incident has been resolved
Affected components
Update timeline
- investigating May 19, 2026, 10:55 AM UTC
We are currently investigating this issue.
- resolved May 19, 2026, 10:55 AM UTC
We are investigating a service impacting incident at the ZUR2 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.
- resolved May 19, 2026, 12:01 PM UTC
Netskope is actively investigating to isolate the root cause of this issue.
- resolved May 19, 2026, 01:05 PM UTC
Netskope continues to investigate to identify a root cause.
- resolved May 19, 2026, 02:24 PM UTC
Netskope continues to investigate to identify a root cause.
- resolved May 19, 2026, 03:37 PM UTC
Netskope continues to actively investigate the root cause.
- resolved May 19, 2026, 04:34 PM UTC
Netskope continues to investigate to identify a root cause.
- monitoring May 19, 2026, 05:21 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring May 19, 2026, 06:08 PM UTC
The issue has been mitigated, we are continuing to monitor the results.
- resolved May 19, 2026, 06:13 PM UTC
The incident has been resolved
- resolved May 19, 2026, 07:26 PM UTC
The incident has been resolved.
Your product runs on more than Netskope
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.