Live / Cloudflare / Incident
Cloudflare: Issues with 1.1.1.1 public resolver in Canada
Cloudflare · cloudflare.comMinor incidentResolved2026-11-14 01:01 UTC
Public — what happened
Summary
Cloudflare said its 1.1.1.1 public DNS resolver may have caused problems for multiple users in Canada, starting at 23:53 UTC on 2026-11-13. About 13 minutes later it said it had found that another network was wrongly announcing routes for the 1.1.1.0/24 address range, and it contacted that network. Cloudflare said its alternate address 1.0.0.1 and its IPv6 resolver addresses were working normally throughout. The other network fixed the problem on its end, and Cloudflare marked the incident resolved at 01:01 UTC on 2026-11-14 after monitoring.
Affected
Recursive DNS
Timeline
- Started — 2026-11-13 23:53 UTC
- Investigating — 2026-11-13 23:53 UTC
- Identified — 2026-11-14 00:06 UTC
- Monitoring — 2026-11-14 00:52 UTC
- Resolved — 2026-11-14 01:01 UTC · 1h 08m after it started
What SquidGrid measured
SquidGrid measured 177 internet paths into Cloudflare’s network during this incident. None of them ran meaningfully slower than the same paths the day before.
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Cloudflare against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Cloudflare: paths off baseline right now, where on the route conditions change, and its full incident track record.
Included with any paid plan.
Open the Cloudflare report →
More from Cloudflare
Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.