You are browsing a shop, a forum or a game's website, and the page turns into Error 1015 "You are being rate limited." The site's rate-limiting rule counted too many requests in its time window and blocked yours for a while.
Stop refreshing, pause anything sending requests to that site, and wait. The owner set the rule and its duration. It looks alarming, but the message alone says nothing about an account suspension.
What error 1015 means
According to Cloudflare's rate-limit error documentation, the owner sets a limit on requests within a time period, and going over it triggers the error.
Cloudflare isn't picking you out. It only enforces the site's configuration, so the site's support team is the one that can restore access.
Visitor fixes for Cloudflare 1015
Hit error 1015 during ordinary browsing or gaming? Work through these in order.
Step 1
Stop the requests
Close duplicate tabs for the affected site and pause auto-refresh tools, scripts or extensions that keep hitting it. Each one adds to the count.
Step 2
Wait before retrying
Cloudflare warns that quick repeated attempts may extend a block, so leave the site idle. Follow any retry guidance on the page, then make one ordinary attempt. If it fails, pause again rather than refreshing in a loop.
Step 3
Check your normal connection
If you use an optional VPN or proxy, check whether the site permits it, and return to your normal connection for ordinary browsing where permitted. Hopping networks to keep blocked requests going does not fix the request rate.
Step 4
Contact the website
Send the URL, the approximate time with your timezone, the error text and a screenshot, plus the Ray ID if the page shows one. Say whether you were browsing normally or running approved automation, and keep account secrets out of the message.
How long the block lasts
For a timed block, as long as the mitigation timeout the owner configured. Cloudflare counts requests over one period and applies the action for a separate one, so a 10-second counting window says nothing about when access returns.
The rate-limiting availability table lists a 10-second mitigation timeout on Free, values up to one hour on Pro and up to one day on Business. Those are an owner's options, not typical waits, and the error number cannot say which one this site chose.
Cloudflare's duration reference adds that challenge actions on Free, Pro and Business throttle requests without a selectable duration, so those timeouts apply to blocks only.
If a response carries a Retry-After header, follow it. Otherwise ask the site for its retry guidance.
Why are you rate limited by Cloudflare?
A rate limit counts requests, not just clicks. One page load can fetch scripts, images and data, so several open tabs, an auto-refresh extension or a script retrying failed requests piles up traffic fast.
Shared connections count too when the rule counts by IP. An office connection, a VPN exit or a shared proxy puts many people behind one public address, and their combined traffic can reach its limit even if each person browses slowly.
IP is not the only option. Cloudflare's rate-limiting parameters also let the owner count by a cookie, a header or another property, depending on the plan. So a shared address is a possible cause, not a diagnosis from the error alone.
Proxy request rates and sticky sessions
If 1015 shows up through a proxy, ask two separate questions. How much traffic is your tool sending, and is the exit IP shared? A fresh IP looks like the quick fix, but buying another connection does nothing about the first.
Lower the request rate before you touch session settings. Pause the workload, cut parallel requests and stop immediate retries. For authorized automation, follow the site's published limits and use its official API when one exists for your task.
Sticky sessions ask for a consistent exit IP, and rotating sessions change addresses according to the provider's configuration. Neither gives you permission to exceed a website's limits, so pick the mode the work needs.
| Situation | Useful action | Why |
|---|---|---|
| Many tabs or workers access one site | Reduce simultaneous activity | Fewer requests arrive together |
| A client retries immediately after rejection | Pause and follow retry guidance | Retrying adds traffic while access is restricted |
| A permitted browsing session needs a consistent IP | Use sticky mode where supported | It requests a consistent exit address rather than a rotating one |
| A shared exit appears affected during normal browsing | Ask the website about permitted access | The owner can investigate the counter and rule |
For the connection model, read what a residential proxy is. 27Proxy sells residential activation codes in its residential GB category, including LokiProxy Residential Traffic. LokiProxy states its residential service offers rotating and sticky options. A residential address still comes with the destination's rules.
Fixes for site owners
Step 5
Identify the affected rule
Collect the visitor's URL, timestamp and error details and compare them with your security events and configured rate-limiting rules. Find what matched before you change a threshold.
Step 6
Inspect the rule configuration
Cloudflare's dashboard guide puts rate-limiting rules on the Security rules page. Check the matching expression, counting characteristics, request threshold, counting period and mitigation duration, and whether the rule includes cached assets.
Step 7
Adjust for legitimate traffic
Compare the rule's scope with what a normal page or workflow requests. Narrow an overly broad match, revise an unsuitable threshold or counting period, and consider shared-IP users. Where available, IP with NAT support helps tell apart visitors who share an address, so one office or VPN exit is less likely to trip a single counter.
Step 8
Validate the change
Cloudflare's threshold-selection guide recommends comparing regular traffic with attack or peak traffic. Its Request rate analysis tab is Enterprise-only, so use your plan's analytics and, where supported, the Log action to try a threshold before enforcing it. Then recheck the legitimate workflow.
Error 1015 vs 1005 vs 1020 vs 429
| Code | Meaning | Where to start |
|---|---|---|
| 1015 | Cloudflare rate-limiting restriction | Pause requests, and the owner checks rate settings |
| 1005 | The website has banned an autonomous system number, or ASN | Contact the owner about the network restriction |
| 1020 | An owner-configured Cloudflare security feature blocked the request | Owner identifies the blocking feature and rule |
| 429 | HTTP Too Many Requests | Reduce requests and follow Retry-After when supplied |
Cloudflare's pages for 1005, 1020 and 429 explain the differences, and Cloudflare documents HTTP 429 as the default status for a rate-limiting Block response.
As a visitor or gamer, stop, wait and write to the site if normal browsing stays blocked. For approved automation through a proxy, slow the request rate first, then pick sticky or rotating sessions for the task, for example with a LokiProxy Residential Traffic code. Site owners should start with the matching rule's threshold and counting characteristics.
FAQ
How long does error 1015 last?
A timed block ends when the owner's mitigation timeout runs out. Rapid retries can prolong it, so leave the site idle between attempts.
Is error 1015 a ban?
No. It is a temporary rate-limiting restriction, and the message alone does not point to a permanent account ban. Contact the website if ordinary browsing stays blocked.
Why do I get 1015 on a VPN?
A shared VPN exit can put several visitors' requests under one IP-based counter, and your own tabs or tools may add more. The website owner can check which rule applied.
Can I contact the site to restore access?
Yes, write to the website owner or its support team. They control the rate-limiting configuration, so the URL, time and screenshot help them investigate.
Does clearing cookies help with a rate limit?
No, and it is a poor first step. An IP-based counter lives outside your browser, so clearing cookies cannot reset it. It can also interfere with Cloudflare's NAT-aware visitor identification and leave you sharing a counter with other visitors.
Drafted with AI help from our notes, then checked and edited by Nazmul I.
