Netskope experienced a major incident on October 31, 2025 affecting LOS1 — Lagos, Nigeria, lasting 1d 23h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 31, 2025, 01:28 PM UTC
We are currently investigating this issue.
- resolved Oct 31, 2025, 01:28 PM UTC
We are investigating a service impacting incident at the LOS1 datacenter(s) for the following service(s) NPA Gateway, Secure Web Gateway. Full details can be found on the support portal.
- resolved Oct 31, 2025, 01:33 PM UTC
Netskope has removed the LOS1 data center from NewEdge to force new client connections to alternative, nearby data centers while the investigation continues into potential root cause.
- monitoring Oct 31, 2025, 01:57 PM UTC
The issue has been mitigated, we are continuing to monitor the results.
- resolved Oct 31, 2025, 05:29 PM UTC
Netskope has identified the potential root cause as linked to a fiber cut disruption within the region. A case is opened with the IX vendor and they are actively working on restoration efforts. LOS1 will remain out of NewEdge until the IX issue has been completely resolved in order to ensure customers have the fastest connectivity and lowest latency options when steering through LOS1.
- resolved Nov 01, 2025, 03:14 PM UTC
Netskope has received an update from the vendor that work continues on restoration efforts to the IX issue caused by the regional fiber cut damage. Once Netskope receives confirmation that restoration of the link has been restored, testing and validation will be performed when the IX link is reactivated. Once validations are successful, Netskope will re-enable LOS1 within the NewEdge network.
- resolved Nov 02, 2025, 12:43 PM UTC
The vendor has completed the necessary repairs on the fiber link issue and connectivity with the IX has been fully restored with the LOS1 data center. Upon completing validation tests, LOS1 was reintroduced back into the NewEdge network successfully. The incident is now resolved.
- resolved Nov 02, 2025, 12:44 PM UTC
The incident has been resolved