Cloudflare Error 1015 and 1010 Through a Proxy: Causes
Find out whether you hit a rate limit (1015) or a browser-signature rule (1010), why a new IP does not fix 1010, and how to slow down properly.
The 3 most common causes
Cause 1: too many requests in a short period. That is 1015. The owner sets a rule that counts requests, usually per IP address, over a period and a threshold; when you pass it the action applies for the rule's duration (from 10 seconds on a Free plan up to a day on Business and Enterprise). Parallel downloads and tight loops get there quickly.
Cause 2: the client does not look like a browser. 1010 is the browser-signature error. Cloudflare names one case: a request to a pages.dev or workers.dev address with a User-Agent that Browser Integrity Check treats as a non-browser client, for example the default Python urllib agent. The owner can also ban a browser signature outright.
Cause 3: a rule counts something other than your IP. On some plans a rate limit can count by ASN, country, path or headers, so a new IP may not reset anything. Do not assume the IP is the only thing the site looks at.
The site received too many requests and temporarily blocked access (a block action returns HTTP 429 by default)
Slow down, wait, spread requests over time; the page does not give a wait time
1010 Access denied
Access refused based on the browser signature (HTTP 403)
Not the IP: check the User-Agent and headers; for API use send a User-Agent that names your application
1020 / 1005
A firewall rule or a banned ASN
Only the site owner can change it; see the 1020 / 1005 guide
From the Cloudflare documentation pages for errors 1015, 1010, 1020 and 1005 and the rate limiting and Browser Integrity Check pages, read on 16 November 2026. Wait times and thresholds are set per site; none are published for a given visitor.
The 1xxx number is in the page body; the HTTP status (429 for rate limiting, 403 for 1010) is in the response header. Do not treat a captcha page or a plain 403 from the origin server as 1015 or 1010.
Step 2: For 1015, stop and wait
Pause all requests from that IP. Cloudflare says repeated attempts in a short span may extend the block and gives no fixed wait time, so wait several minutes, then try one request.
Step 3: Lower your request rate and parallelism
Cut the number of parallel connections, add a pause between requests, cache what does not change, and honour a Retry-After header when the site sends one (see the Python example).
Step 4: For 1010, fix the client, not the IP
Check which User-Agent and headers your tool sends. For your own scripts and API calls, send a descriptive User-Agent that names the application, as Cloudflare advises for API clients. Test the same URL in an ordinary browser.
Step 5: If you still need access, ask the owner
Cloudflare cannot lift an individual block and says visitors should contact the website owner. Send the Ray ID from the error page and describe what you are doing.
Python example: retry with a growing pause
import time
import requests
PROXY = "http://LOGIN:PASSWORD@HOST:PORT"
PROXIES = {"http": PROXY, "https": PROXY}
# A User-Agent that names your application (Cloudflare's advice for API clients)
HEADERS = {"User-Agent": "my-app/1.0 (contact: [email protected])"}
def fetch(url, tries=4, pause=30):
for _ in range(tries):
r = requests.get(url, proxies=PROXIES, headers=HEADERS, timeout=30)
if r.status_code != 429 and "1015" not in r.text:
return r
retry_after = r.headers.get("Retry-After", "")
time.sleep(int(retry_after) if retry_after.isdigit() else pause)
pause *= 2 # wait longer each time instead of retrying at once
return r
r = fetch("https://example.com/api/items")
print(r.status_code, r.headers.get("cf-ray"))
Example only: replace the placeholder values. It waits for Retry-After when sent and otherwise doubles the pause on each retry. Use it only on sites and APIs you are allowed to query.
If it still fails
1015 comes back right after the wait
Check Check how many requests and parallel connections you send; the rule may count a short window
Fix Halve the request rate and wait longer before the next try
Stop when Stop after three blocks in a row and read the site's API terms or contact the owner
1015 on every IP I switch to
Check See whether the rule counts something other than the IP, such as a path or headers
Fix Slow down overall; changing IPs does not change a rule that counts something else
Stop when Stop switching IPs; it can keep triggering the same limit
1010 on a script, not in the browser
Check Compare the User-Agent and headers of the script with the browser
Fix Send a descriptive User-Agent for API calls, or use the official API
Stop when Stop if the owner has banned your client signature; ask the owner
Connection error before any Cloudflare page
Check Check address, port, protocol (HTTP 2222 or SOCKS5 3333) and login
Fix Fix the proxy settings first; this is not a 1xxx error
Stop when Open a ticket with the order number if the proxy does not connect
Rotating residential traffic for work within a site's limits
A rotating line spreads your own load across IPs and lets you check a page from another country; it does not remove a site's rate limit and sites can count requests by other characteristics. Rotating residential traffic is sold per GB: Budget line US$1.50 per GB, Premium line US$5.00 per GB, purchased traffic does not expire, 195+ countries, HTTP on port 2222 and SOCKS5 on port 3333. A new IP is used for each new connection unless you open a session.
There is no free trial; the smallest purchase is 1 GB. We cannot promise any site accepts a given IP.
The site has received too many requests from you in a set period and has temporarily blocked access. The owner sets the limit; Cloudflare does not lift individual blocks.
It depends on the rule. Cloudflare documents the duration as set by the owner, from 10 seconds on a Free plan up to a day on Business and Enterprise, and the 1015 page gives no fixed time. Wait, then send one request.
Access was denied based on the browser signature. It can be an owner rule, or a request to a pages.dev or workers.dev hostname with a User-Agent that Browser Integrity Check treats as a non-browser client.
No. A rate limit counts requests by a rule the owner wrote; IP address is one option and others exist. Lower your rate, and ask the owner if you need more.
Real household IPs in 195+ countries; the Premium line adds state and major-city targeting. A new IP on every new connection, or keep sticky sessions. From US$1.50/GB, US$1.35/GB at 100 GB. HTTP and SOCKS5.
Read on 16 November 2026: 1015 means the site has received too many requests and temporarily blocked access; the owner's rate-limiting rules cap how many requests a visitor can make in a set period; visitors should wait and try again later because repeated attempts in a short span may extend the block; Cloudflare does not set these rules and cannot lift an individual block; the page gives no wait time.
Read on 16 November 2026: 1010 means the owner banned access based on the browser's signature; it also appears for requests to pages.dev or workers.dev hostnames with a User-Agent that Browser Integrity Check treats as a non-browser client (the default Python urllib agent is an example); API clients are told to send a descriptive User-Agent that names the application, such as my-app/1.0, which does not need to look like a browser.
Read on 16 November 2026: a rate limiting rule counts requests per characteristic (IP address is the default option; other characteristics such as ASN, country, path or headers exist on some plans), over a period and a threshold; after the limit is reached the action applies for the configured duration (10 seconds on Free, up to 1 hour on Pro, up to 1 day on Business and Enterprise); a Block action returns 429 by default; blocked visitors can see error 1015.
Read on 16 November 2026: Browser Integrity Check is on by default; it looks at HTTP headers commonly abused by spammers and challenges visitors without a user agent or with a non-standard user agent; owners can turn it off or skip it for selected requests.
Proxy302 product facts and price list
Product observation · Confirmed on:
Product facts file of the site (prices in US$, 1 PTC = US$1, protocols and ports, countries, traffic that does not expire, no free trial). Checked on 16 November 2026.
Ready to try it?
Create an account, top up once, then pick rotating residential, static ISP or datacenter IPs and have one running in your browser within minutes.