Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Issues with 1.1.1.1 public resolver in Canada

Started 13 Nov 23:53 UTC, resolved today 01:01 UTC: it lasted 1 h 7 min.

1 h 7 min How long it lasted, from the provider's times
4Updates posted
6Other incidents at the same time

What it affected

As the provider names it

Recursive DNS

What the provider posted

Newest first
  1. today 01:01 UTCResolvedThis incident has been resolved.
  2. 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.
  3. 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.
  4. 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

Keep track

What changed

  1. Resolved: 14 Nov 2026 01:01 UTC · Status: Monitoring → Resolved · Incident state: Ongoing → Ended
  2. Status: Identified → Monitoring
  3. Status: Investigating → Identified
Page history

Changes are dated when recorded; day views use the last saved version from that UTC day, and citations stay fixed.

Cite this version
Field-level log (8)

Up to 100 recent field edits are shown; older edits may be outside retention.

  1. 14 Nov 2026 · 01:06:25 UTC Resolved14 Nov 2026 01:01 UTC
  2. 14 Nov 2026 · 01:06:25 UTC StageMonitoring → Resolved
  3. 14 Nov 2026 · 01:06:25 UTC Observed stateOngoing → Ended
  4. 14 Nov 2026 · 01:01:20 UTC SummaryThe 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.
  5. 14 Nov 2026 · 00:55:45 UTC StageIdentified → Monitoring
  6. 14 Nov 2026 · 00:55:45 UTC SummaryWe 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.
  7. 14 Nov 2026 · 00:09:34 UTC StageInvestigating → Identified
  8. 14 Nov 2026 · 00:09:34 UTC SummaryCloudflare 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.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 14 Nov 08:15 UTC · 274 of 275 readable · 269 fully read · documentation 469/469 current