Live / Cloudflare / Incident
Cloudflare: DNSSEC Configuration Change Issues
Cloudflare · cloudflare.comMinor incidentResolved2026-11-12 05:26 UTC
Public — what happened
Summary
Cloudflare reported a minor incident affecting customers' ability to turn DNSSEC signing, a domain security feature, on or off. The company said it began investigating at 04:53 UTC on 2026-11-12 and did not describe the full extent of the impact. By 05:03 UTC Cloudflare said it had identified the issue and was working on a fix, and by 05:06 UTC it said a fix was in place and it was monitoring. Cloudflare marked the incident resolved at 05:26 UTC.
Affected
DNSSEC Updates
Timeline
- Started — 2026-11-12 04:53 UTC
- Investigating — 2026-11-12 04:53 UTC (2 updates)
- Identified — 2026-11-12 05:03 UTC
- Monitoring — 2026-11-12 05:06 UTC
- Resolved — 2026-11-12 05:26 UTC · 33 min after it started
What SquidGrid measured
SquidGrid measured 158 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.