today 01:01 UTCResolvedThis incident has been resolved.
today 00:52 UTCMonitoringThe network with the offending route leak has fixed the issue on their end. We are currently monitoring the effect of this fix.
today 00:06 UTCIdentifiedWe have reached out to the network where we see an active hijack of 1.1.1.0/24. 1.0.0.1 and public resolver IPv6 prefixes are fully operational and reachable at this time.
13 Nov 23:53 UTCInvestigatingCloudflare is aware of, and investigating, an issue which potentially impacts multiple users in Canada that use 1.1.1.1 public resolver. Further detail will be provided as more information becomes available.
Around it
From the sources ChangeIntel reads; a match in time is not a cause
14 Nov 2026 · 01:01:20 UTCSummaryThe network with the offending route leak has fixed the issue on their end. We are currently monitoring the effect of this fix. → This incident has been resolved.
14 Nov 2026 · 00:55:45 UTCSummaryWe have reached out to the network where we see an active hijack of 1.1.1.0/24. 1.0.0.1 and public resolver IPv6 prefixes are fully operational and reachable at this time. → The network with the offending route leak has fixed the issue on their end. We are currently monitoring the effect of this fix.
14 Nov 2026 · 00:09:34 UTCSummaryCloudflare is aware of, and investigating, an issue which potentially impacts multiple users in Canada that use 1.1.1.1 public resolver. Further detail will be provided as more information becomes available. → We have reached out to the network where we see an active hijack of 1.1.1.0/24. 1.0.0.1 and public resolver IPv6 prefixes are fully operational and reachable at this time.