Direct Answer
Cloudflare error 1015 ("You are being rate limited") means a website's Cloudflare rate-limiting rule has temporarily blocked your IP for sending more requests in a short window than its policy allows. It is a per-IP, time-based throttle, not a permanent ban. The fix is to slow down, space out requests, and bring your traffic back under the site's limit.
What Is Cloudflare Error 1015?
Error 1015 is the code Cloudflare returns when a site you are visiting has a rate-limiting rule and your IP address has exceeded it. The page reads "You are being rate limited" and usually comes back with HTTP status 429 (Too Many Requests). It is generated at Cloudflare's edge, before your request ever reaches the website's own servers.
Three facts make 1015 different from a hard block:
- It is per IP. The counter that tripped is tied to your specific IP address, not your account or browser.
- It is time-windowed. Rules count requests inside a window (for example, more than 50 requests in 10 seconds) and then enforce a cooldown.
- It is temporary. The block lifts automatically once the cooldown expires. You did not earn a permanent ban — you hit a speed limit.
The site operator — not Cloudflare — chooses the threshold, the window, and how long the timeout lasts. That is why the same behaviour trips 1015 on one site and passes cleanly on another.
Why Am I Seeing Error 1015?
A 1015 always comes down to one thing: too many requests from one IP, too fast, against a rule that site set. The usual triggers:
- Automated traffic without pacing. A scraper, crawler, or script firing requests as fast as the network allows is the most common cause. Sites set rate limits precisely to catch unthrottled automation.
- Aggressive concurrency. Many parallel workers all routed through a single IP multiply your effective request rate, even if each worker feels modest on its own.
- Retry storms. Code that retries failed requests immediately, with no backoff, can spike your rate the moment a site gets slow.
- A shared IP behind CGNAT. On a network using Carrier-Grade NAT, many users share one public IPv4 address, so the requests of strangers can count toward the same limit you do. This is rarer but real.
- A strict rule on a sensitive endpoint. Login pages, search, and pricing APIs often carry tighter limits than the rest of a site.
In every case the lever is the same: your IP's request rate crossed the site's line. Fix the rate and the 1015 goes away.
How to Fix Cloudflare Error 1015
The fixes fall into two groups: what a normal visitor does, and what a developer running automated requests does.
If you are a regular visitor
- Wait. The block is time-based. Stop refreshing, wait out the cooldown (often under a minute), and try again. Repeated reloads only reset the timer against you.
- Disable a misbehaving extension or VPN. Some browser extensions and shared VPN exit IPs fire background requests or share an IP with heavy users. Turning them off can drop you below the limit.
- Check you are not on a busy shared connection. On public Wi-Fi or a CGNAT network, other people's traffic may be pushing the shared IP over the line.
- Contact the site owner. If you keep hitting 1015 during normal use, the operator can review the rule or whitelist legitimate traffic. This is the intended escalation path — Cloudflare itself points blocked users back to the site owner.
If you run scripts or scrapers
- Slow down. Add a deliberate delay between requests and randomised jitter so the pattern looks human-paced rather than machine-gun.
- Honor
Retry-After. A 429 response often includes aRetry-Afterheader telling you exactly how long to wait. Respect it instead of retrying blindly. - Add exponential backoff. When you hit a limit, wait progressively longer before each retry rather than hammering immediately.
- Cache and deduplicate. Do not re-fetch pages you already have. Caching cuts your request count without losing data.
- Read the rules. Check
robots.txt, any published API rate limits, and the site's terms, and stay inside them. Many sites offer an official API that removes the need to scrape the HTML at all. - Distribute genuinely high legitimate load. If your work honestly needs more volume than one IP's budget allows, spread it across multiple rotating IPs so no single IP exceeds the per-IP limit — see the table below.
None of these steps defeat Cloudflare's protection. They bring your traffic back inside the limit the site author chose, which is exactly what the rule is asking you to do.
What Not to Do
A few common reactions make things worse:
- Refreshing in a panic. Every reload is another request against the limit, extending the cooldown.
- Removing all delays after the block clears. You will trip the same rule within seconds.
- Cycling IPs purely to keep pushing past a limit. If your rate is the problem, a new IP just hits the same wall — and a site can escalate from a soft 1015 to a longer block when it sees the pattern. IP rotation is a tool for distributing legitimate load, not for ignoring a site's stated limits.
The honest reading of a 1015 is simple: the site asked you to slow down. The durable fix is to slow down.
Error 1015 vs. Other Cloudflare Codes
1015 is one of several Cloudflare status pages. Knowing which one you have tells you what to do.
| Code | Message | What it means | Typical fix |
|---|---|---|---|
| 1015 | You are being rate limited | Your IP exceeded a per-IP request limit | Slow down, wait out the cooldown, pace requests |
| 1020 | Access denied | A firewall (WAF) rule blocked the request | Review the request; contact the site owner if legitimate |
| 1006 / 1007 / 1008 | Access denied — your IP is banned | The site explicitly blocked the IP or its range | Contact the site owner; the block is deliberate, not rate-based |
| 429 | Too Many Requests | The HTTP status that usually accompanies 1015 | Honor Retry-After, back off, reduce rate |
| 503 | Service unavailable | Server overloaded or under challenge | Retry later with backoff |
If you see 1015 or 429, the problem is your request rate and the fix is pacing. If you see 1006–1008 or 1020, the problem is a deliberate block or firewall rule, and rotating IPs or pacing will not address the underlying decision — contacting the operator is the right move.
When Distributed Rotation Genuinely Helps
For legitimate work that needs real volume — large-scale price monitoring, SERP tracking, or market research — one IP simply does not have the request budget to gather everything inside a site's per-IP limit. Spreading that load across many IPs keeps each IP comfortably under the threshold, the same way a team of people browsing is not one person hammering a page.
This is where real mobile IPs differ from datacenter ranges. Because of CGNAT, a single mobile IP is already shared by thousands of genuine subscribers, so it reads as ordinary consumer traffic and carries high IP reputation. Rotating across real German mobile endpoints — with sticky sessions where a task needs to hold one IP, and on-demand rotation where it does not — lets you distribute legitimate load across many trustworthy IPs instead of overloading one.
Two caveats, stated plainly. First, distribution is not a licence to ignore limits: pace each IP, respect each site's terms, and stay within the law — see the EU legal view on web scraping and are mobile proxies legal. Second, rotation does not "beat" Cloudflare; it spreads honest traffic so no single IP looks abusive. If a site has told you not to access something, more IPs is not the answer.
GermanProxy.io provides dedicated and shared German 5G mobile endpoints (Blue and Red Premium Mobile Network), HTTP and SOCKS5, with fair-use 20 GB/day per connection — built for legitimate, well-paced data work, not for overrunning a site's limits.
FAQ
What does Cloudflare error 1015 mean?
Error 1015 is Cloudflare's "You are being rate limited" message. A site operator has set a rate-limiting rule, and your IP exceeded the allowed number of requests within a defined time window. Cloudflare then blocks further requests from that IP for a set cooldown period — typically seconds to minutes, occasionally up to an hour, depending on the rule.
How long does Cloudflare error 1015 last?
It depends entirely on the rule the site configured. The block is temporary and clears automatically once the cooldown expires — often 10 seconds to a few minutes, sometimes up to an hour for stricter rules. There is no fixed global duration; each site sets its own window and timeout.
Is error 1015 the same as being IP-banned?
No. A 1015 is a temporary, automatic throttle tied to request volume, and it lifts on its own. A ban is a deliberate, often longer or permanent block. If the same IP keeps tripping the limit, however, a site may escalate to a longer block, so repeatedly hammering the limit is the wrong response.
Will switching IPs fix Cloudflare error 1015?
Switching IPs resets the per-IP counter, so a fresh IP starts at zero. But if your request rate is the underlying problem, you will just trip the limit again on the new IP. The durable fix is to lower the rate and distribute legitimate load properly — not to cycle IPs to keep pushing past a limit.
How do I avoid hitting Cloudflare rate limits when scraping?
Pace requests to a human-like rate, add delays and jitter between calls, honor robots.txt and any published API limits, cache responses you have already fetched, and respect Retry-After headers. For genuinely high legitimate volume, spread requests across rotating IPs so no single IP exceeds the site's per-IP budget. See our Python and Scrapy guides for pacing in code.
Can a mobile proxy help with error 1015?
It can help distribute legitimate load: rotating across real German mobile IPs means no single IP carries your entire request volume, which keeps each IP under a site's per-IP rate limit. It is not a way to defeat a site's protections — pair it with sensible pacing and respect for each site's terms.
CTA
Doing legitimate, high-volume data work that needs to stay under per-IP limits? Our German 5G mobile proxies let you distribute load across real, high-reputation mobile IPs — browse the plans or see how to test your setup.
Get a German mobile proxy: Real 4G/5G IPs from Germany, fair-use 20 GB/day — compare German mobile proxy plans or get a dedicated proxy on the Blue network.