Minor impactResolvedCDN

Cloudflare incident: Issues with 1.1.1.1 for Families

Cloudflare reported this minor-impact incident on its official status page on Sep 23, 2026, 00:42 UTC. It was resolved after 44 min.

Right now Cloudflare is operational. Live Cloudflare status →

🔔 Get alerted when Cloudflare has issuesFree · email alerts · no credit card
Sep 23, 2026, 00:42 UTC
started
Sep 23, 2026, 01:26 UTC
resolved
44 min
duration
Minor
impact

Timeline

updates from Cloudflare's status page ↗
  1. resolvedSep 23, 2026, 01:26 UTC

    This incident has been resolved.

  2. monitoringSep 23, 2026, 01:21 UTC

    A fix has been implemented and we are monitoring the results.

  3. identifiedSep 23, 2026, 00:55 UTC

    The issue has been identified and a fix is being implemented.

  4. investigatingSep 23, 2026, 00:42 UTC

    Cloudflare is aware of, and investigating, an issue which impacts DNS over HTTPS requests to 1.1.1.1 for Families (1.1.1.2 and 1.1.1.3) Authoritative DNS provided by Cloudflare is unaffected. Further detail will be provided as more information becomes available.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Cloudflare's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Cloudflare have incidents?

Cloudflare reported 38 incidents in the last 90 days, 1 of them major or critical. A typical incident lasted 1h 28m. See Cloudflare's uptime and incident history

← Previous: Cloudflare One Clients are incorrectly challenged on some sites (Sep 22, 2026)Next: Elevated number of R2 503 errors in Australian Eastern Coast region (Sep 23, 2026) →
Cloudflare incident on Sep 23, 2026: Issues with 1.1.1.1 for Families · APIStatus.watch