based on user reports and queries over the last 24 hours
Cloudflare DNS outage statistics
After switching nameservers to Cloudflare, sites often go dark for up to 48 hours — that''s normal propagation lag. But if it''s been longer, check that your A or CNAME records actually point to the right IP. A common trap: the orange cloud (proxy) icon is on when it should be off, or vice versa. Go to DNS > Records and verify each entry manually.
This error means the resolver can''t find your domain at all. Usually the root cause is one of these:
- The NS records at your registrar still point to the old provider
- You deleted a required record by accident
- The zone was paused in the dashboard under ''Overview''
Fix: go to your registrar''s DNS panel and confirm the nameservers match exactly what Cloudflare assigned — two entries, no typos.
If your host uses a self-signed cert and you set SSL mode to ''Full (Strict)'', visitors get an SSL handshake error. Drop the mode to ''Full'' (not Strict) in SSL/TLS settings, or install a valid origin certificate via the Origin Server tab.
- MX records must not be proxied — the orange cloud icon breaks mail routing entirely
- SPF record should include Cloudflare''s IPs only if you route mail through their infrastructure
- After any MX change, give it 30–60 minutes before testing delivery
Switching your system DNS to 1.1.1.1 speeds up most queries, but if latency spikes, your ISP may be intercepting port 53 traffic. Try DNS-over-HTTPS instead: configure it in your OS or browser settings pointing to https://cloudflare-dns.com/dns-query.
The token was probably scoped too narrowly. Open the API Tokens page, click Edit on your token, and make sure the Zone > DNS > Edit permission is included for the correct zone. Also check the token hasn''t expired — there''s an optional TTL that''s easy to miss during setup.
Cloudflare DNS
Your message will be published in about
5 minutes
Service administration will see your message
