Is Cloudflare Down? Live status & outage reports

Service info and troubleshooting

Site returns Error 522 or 523

Both errors mean the connection between Cloudflare and your origin server timed out or was refused. Check that your server is actually running and not overloaded. Make sure your firewall isn't blocking Cloudflare's IP ranges — this is a common culprit. You can find the current list of Cloudflare IPs at cloudflare.com/ips and whitelist them explicitly.

Dashboard login fails or loops

If you can't get into your Cloudflare account, first rule out a stale session: clear cookies for cloudflare.com and try an incognito window. If two-factor authentication is the blocker — backup codes are your only way in without the authenticator app, so keep them somewhere safe. Account lockouts after failed attempts usually lift within 30 minutes.

SSL errors on your domain

Error 525 or 526 typically means the SSL certificate on your origin server is missing, expired, or self-signed when Cloudflare expects a valid one. Check your SSL/TLS mode in the dashboard — switching from Full (Strict) to Full can buy you time while you fix the cert. Never leave it on Flexible in production; it creates a false sense of security.

DNS changes not propagating

• After updating DNS records, propagation can take up to 48 hours globally, but usually happens within an hour.
• Use dig or nslookup to check what different resolvers are currently returning for your domain.
• If records seem stuck, verify TTL values — a TTL of 86400 means resolvers cache the old value for a full day.
• Purge the cache in the dashboard under Caching → Configuration if you're testing cached responses.

Pages or Workers deployment errors

Deployments fail most often because of build command mismatches or environment variables that aren't set in the project settings. Double-check that your framework preset matches what's actually in the repo. Worker script errors usually show up in real-time logs under Workers → your worker → Logs — that's the fastest place to spot a syntax or runtime issue.

High latency despite CDN being active

If response times are still slow, the likely reason is that caching isn't actually kicking in. Check the CF-Cache-Status response header — a MISS or BYPASS means every request hits your origin. Review your Cache Rules and make sure the content type and URL pattern are actually matched. Also confirm that Cache-Control headers from your server aren't set to no-store.