Getting 1015? Here’s why it happens and the exact fix.
You are seeing Cloudflare 1015 because the site Cloudflare rate limiting rule matched your request pattern. The fix: reduce request frequency, rotate IPs per request, and add random delays.
Each request from a unique IP gets its own rate counter at the Cloudflare edge.
Cloudflare rate rules use time windows (typically 1 minute). Spacing requests avoids hitting the threshold.
Limit to 10-15 parallel connections per target domain.
Cloudflare 1015 responses include Retry-After. Wait at least that duration before retrying.
import requests
import time
import random
# Per-request rotation -- each request gets a fresh IP
proxy = "http://USER:PASS@gw.knoxproxy.com:7000"
for i in range(200):
time.sleep(random.uniform(1, 2)) # polite pacing
r = requests.get(f"https://cf-site.example/api/items/{i}",
proxies={"https": proxy})
if r.status_code == 200:
process(r.json())Test your setup with our proxy checker, then contact support if 1015 still won’t clear.
Error 1015 is Cloudflare-specific rate limiting. Unlike HTTP 429 which comes from the origin server, 1015 comes from Cloudflare edge. The site owner defined rate rules in Cloudflare (e.g., max 100 requests per minute per IP to a path), and your traffic exceeded that threshold. Cloudflare enforces the limit at the edge before the request reaches the origin.
Enable per-request rotation. Each request from a different IP resets the rate counter.
Spread requests across time with delays. Rotation alone may not help if the rate rule is broad.
If 1015 appears even with per-request rotation and delays under 1 req/sec, the site may have extremely strict rate rules. Contact KnoxProxy support for target-specific pacing recommendations.
1015 is Cloudflare-specific rate limiting enforced at the edge, before your request reaches the origin server at all. HTTP 429, by contrast, comes from the origin server itself. Both effectively mean "slow down," but 1015 blocks the request earlier in the pipeline and wastes less of your bandwidth.
Yes, if the Cloudflare rate rule is scoped per-IP address. Each new IP address gets its own independent rate counter at the edge. Per-request rotation effectively gives you unlimited throughput within the per-IP limit, since no single address ever accumulates enough requests to trigger 1015.
Typically 1 to 10 minutes, depending on how the site owner configured the rate rule. The Retry-After header in the 1015 response tells you exactly when the limit expires for that specific IP, so you know when it is safe to retry.
KnoxProxy comes pre-configured to avoid the most common errors. Get started and fix 1015 for good.