based on user reports and queries over the last 24 hours
Cloudflare outage statistics
- Enterprise customers: Submit ticket at dash.cloudflare.com/support;
- Community forum at community.cloudflare.com for general questions;
- Report abuse at https://www.cloudflare.com/abuse;
- Email support@cloudflare.com (Enterprise customers);
- Emergency hotline for Enterprise customers (provided in dashboard);
- Check documentation at developers.cloudflare.com;
- Developer Discord at discord.cloudflare.com.
- X (Twitter) - https://x.com/Cloudflare;
- X (Status) - https://x.com/CloudflareStatus;
- Blog - https://blog.cloudflare.com;
- Status Page - https://www.cloudflarestatus.com;
- Developer Docs - https://developers.cloudflare.com;
- Community - https://community.cloudflare.com;
- LinkedIn - https://www.linkedin.com/company/cloudflare.
When Cloudflare experiences an outage, websites protected by Cloudflare may show error pages or become completely inaccessible.
- Check Cloudflare status at https://www.cloudflarestatus.com for real-time service health;
- Verify if issue is Cloudflare-wide or specific to one website;
- Try accessing websites from different networks or devices;
- Check if your IP has been blocked by Cloudflare security;
- Wait during confirmed outages as Cloudflare resolves issues quickly;
- Contact website owner if only one site is affected;
- Clear DNS cache on your device.
These errors indicate Cloudflare cannot connect to the origin server properly.
- For website owners: Check if origin server is online and accessible;
- Verify firewall allows Cloudflare IP ranges at cloudflare.com/ips;
- Check origin server logs for connection errors;
- Ensure SSL/TLS settings match between Cloudflare and origin;
- Verify DNS records point to correct origin IP;
- Check if origin server is overloaded or crashed;
- Review rate limiting rules that might block Cloudflare;
- For visitors: Wait and retry, or contact website owner.
Error 1020 indicates Cloudflare firewall rules are blocking your access.
- Check if your IP address has been blacklisted;
- Disable VPN or proxy that might trigger security rules;
- Clear browser cookies and cache completely;
- Try accessing from different network or device;
- Complete CAPTCHA challenge if presented;
- Contact website owner to whitelist your IP;
- Check if your browser user-agent is blocked;
- Ensure JavaScript is enabled in browser.
DNS problems include "DNS_PROBE_FINISHED_NXDOMAIN" or inability to resolve domain names.
- Flush DNS cache (Windows: ipconfig /flushdns; Mac: sudo dscacheutil -flushcache);
- Change DNS servers to Cloudflare's 1.1.1.1 and 1.0.0.1;
- Check if domain DNS records are properly configured in Cloudflare dashboard;
- Verify nameservers point to Cloudflare (check with whois lookup);
- Wait up to 24-48 hours for DNS propagation after changes;
- Use nslookup or dig commands to troubleshoot DNS;
- Check if domain registration is active and not expired;
- Try different DNS resolver to isolate issue.
SSL issues include "ERR_SSL_VERSION_OR_CIPHER_MISMATCH" or invalid certificate errors.
- Verify SSL/TLS mode in Cloudflare dashboard (Full, Full Strict, Flexible);
- Ensure origin server has valid SSL certificate installed;
- Check certificate hasn't expired in Cloudflare SSL/TLS settings;
- Wait 24 hours after enabling Universal SSL for activation;
- Clear browser SSL state and cache;
- Disable SSL/TLS in browser temporarily to test;
- Check minimum TLS version requirements;
- Use Cloudflare's Origin CA certificate on origin server.
Performance problems include slow page loads, timeouts, or high response times.
- Check Cloudflare Analytics for traffic patterns and bottlenecks;
- Enable caching rules for static content;
- Optimize cache settings and purge cache if stale;
- Review Page Rules that might affect performance;
- Enable Auto Minify for CSS, JavaScript, and HTML;
- Check origin server performance and response times;
- Use Argo Smart Routing for improved routing (paid feature);
- Review and optimize Worker scripts if using Cloudflare Workers.
Overly aggressive DDoS protection may block legitimate users or services.
- Adjust Security Level in Cloudflare dashboard (High to Medium);
- Review Firewall Rules and disable overly restrictive ones;
- Whitelist known good IP addresses or ranges;
- Check Challenge Passage setting duration;
- Review Rate Limiting rules for false positives;
- Disable "I'm Under Attack" mode if accidentally enabled;
- Add bypass rules for APIs or automated services;
- Monitor Security Events logs for patterns.
API problems include authentication errors, rate limiting, or failed requests.
- Verify API token has correct permissions at dash.cloudflare.com/profile/api-tokens;
- Check API rate limits (standard: 1200 requests per 5 minutes);
- Review API documentation at developers.cloudflare.com/api;
- Ensure correct API endpoint and version being used;
- Check authentication method (API key vs token);
- Review error responses for specific error codes;
- Test API calls using Cloudflare API documentation examples;
- Check if account has necessary plan level for API features.
Cloudflare
Your message will be published in about
5 minutes
Service administration will see your message