Quick answer: Cloudflare Error 1015 means you’ve been rate limited—you sent too many requests in a short time, and the website temporarily blocked you to protect its resources.
What Is Cloudflare Error 1015?
Error 1015 is a rate limiting error thrown by Cloudflare when a client exceeds the allowed number of requests within a specific time window. It’s a protective measure to prevent abuse, DDoS attacks, and server overload.
How it works:
- Website owners set rules: “X requests per Y minutes”
- Cloudflare tracks every IP’s request count
- Exceed the limit → get Error 1015 for a set duration
Typical ban duration: 10 seconds to 24 hours (Free/Pro plans max 1 hour)
Cloudflare API limit: 1,200 requests per user every 5 minutes
Common Causes of Error 1015
| Cause | Why It Happens |
|---|---|
| Web scraping bots | Automated tools sending too many requests |
| Misconfigured proxies | Proxies flagged as suspicious |
| Browser extensions | Some extensions auto-refresh or send hidden requests |
| Shared IPs | Multiple users on same IP hitting the same site |
| VPN usage | VPN IPs are often shared and trigger limits |
| Mobile network IPs | Carrier NAT means many users share IPs |
| Legitimate heavy use | Just browsing too fast on a strict site |
How to Fix Error 1015: For Regular Users
1. Wait it out
The simplest fix. Check if the error message specifies a time, or just wait 15-30 minutes.
2. Switch networks
- Toggle Wi-Fi off/on
- Switch from Wi-Fi to mobile data
- This gives you a new IP address
3. Try a different browser
Use incognito/private mode, or switch browsers entirely. This rules out extension issues.
4. Disable browser extensions
Some extensions send background requests. Disable them temporarily to test.
5. Clear cookies and cache
Outdated cached data can sometimes cause verification issues.
6. Toggle airplane mode (mobile)
Keep it on for 10+ seconds to force a new IP assignment.
7. Request desktop site (mobile)
Some sites have stricter limits on mobile versions.
How to Fix Error 1015: For Web Scrapers
1. Stop immediately
Continuing to send requests will only extend your ban.
2. Reduce request frequency
Slow down. Add delays between requests—humans don’t click every second.
3. Rotate IPs
Different IPs for different requests prevents hitting per-IP limits.
4. Rotate User Agents
Match your User-Agent to each IP. Use current, popular browser strings.
5. Check your headers
Remove suspicious headers like X-Forwarded-For. Ensure headers match a real browser profile.
6. Respect robots.txt
Check the site’s allowed crawl rates and follow them.
7. Consider using a web scraping API
Some APIs handle rotation and rate limiting automatically.
How to Fix Error 1015: On Mobile Networks
Mobile users get Error 1015 frequently due to CGNAT (Carrier-Grade NAT)—many users share the same public IP.
Quick fixes for mobile:
- Toggle airplane mode – 10+ seconds, then reconnect
- Switch to Wi-Fi – Gives you a fresh IP
- Use a VPN – Change VPN servers until one works
- Request desktop site – Some sites have different limits per device type
How to Fix Error 1015: For Website Owners
If legitimate users are hitting Error 1015, adjust your settings:
1. Check rate limit rules
Cloudflare Dashboard → Security → WAF → Rate Limiting Rules
2. Increase thresholds
Give users more requests before triggering blocks.
3. Use CAPTCHA first
Set rules to “Challenge” (CAPTCHA) before blocking entirely. This filters bots without blocking real users.
4. Whitelist important crawlers
Allow Googlebot, Bingbot, and other legitimate search engines.
5. Review time windows
Maybe 60 seconds is too strict; try 2-5 minutes instead.
6. Delete old configurations
Outdated rules may conflict with current traffic patterns.
7. Contact Cloudflare support
If nothing else works, they can help diagnose.
Components of Cloudflare Rate Limiting
Every rate limiting rule has three parts:
- Request matching criteria
- Scheme (HTTP/HTTPS)
- Request path (e.g., /api/*)
- Request methods (GET, POST)
- Response codes
- Rate matching criteria
- Number of requests
- Time period (e.g., 100 requests in 60 seconds)
- Tracks per IP or per visitor
- Rule mitigation
- Action (Block, Challenge, JS Challenge)
- Ban duration
How to Avoid Error 1015 Long-Term
For regular users:
- Avoid hammering refresh buttons
- Disable auto-refresh extensions
- Use incognito mode for sensitive sites
- Clear cookies periodically
For scrapers:
- Implement polite crawling delays
- Use IP rotation
- Rotate User Agents with each IP
- Study each site’s specific limits
- Monitor response headers for rate limit warnings
For site owners:
- Set realistic rate limits
- Use challenges instead of blocks
- Monitor your event logs
- Create exceptions for trusted IPs
- Test rules before enabling
Error 1015 vs. Other Cloudflare Errors
| Error | Meaning | Fix |
|---|---|---|
| 1015 | Rate limited | Slow down, change IP |
| 1020 | Firewall rule blocked | IP banned, rule issue |
| 1010 | Browser integrity failed | Enable JS/cookies |
| 520-527 | Origin server error | Hosting issue |
Quick Summary
Error 1015 = “Too many requests, slow down.”
For users: Wait, switch networks, or use incognito mode.
For scrapers: Rotate IPs, reduce frequency, rotate User Agents.
For site owners: Adjust rate limit rules or use challenges instead of blocks.
The key to avoiding Error 1015 is simple: respect the limits. Whether you’re browsing or scraping, staying under the radar means acting more like a human and less like a machine.