# 429 Too Many Requests and Cloudflare Error 1015

A rate limit asks the client to slow down. Wait for the retry period, reduce requests, and identify what the site limits before changing IP.

## Why it happens

A site can count requests by IP, account, session, or another signal. A shared IP is one possible cause, not a conclusion you can draw from the error alone.

Cloudflare Error 1015 is a rate limit. Its guidance recommends waiting and avoiding rapid retries. See [Cloudflare's Error 1015 guidance](https://developers.cloudflare.com/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1015/).

## What the page says

Any of these is a string the page showed:

- "429 Too Many Requests"
- "Rate limit exceeded"
- "Slow down"
- "You are being rate limited"
- "Error 1015"

## What to do first

Honor the site's Retry-After header or stated wait time. Reduce request frequency and concurrency. If the limit is on an account or service plan, changing IP will not resolve that limit.

## When a different IP may help

If the site permits your task and evidence points to a shared-IP problem, the [quickstart](/docs) explains how to test Aluvia. Do not use repeated IP rotation as a substitute for the site's rate limits. Stop and contact the operator if the problem continues.

## About Aluvia

Aluvia is a local CLI and proxy daemon for the existing Chrome or Chromium browser. An eligible IP-related test needs command access to that browser's host, Node.js 18 or later, and a usable local browser. First 10 MB free without an account, API key or payment; then 2 USD per GB. Initial setup can restart Chrome.

If a separate IP-related problem is established after the checks above, follow the [complete trial steps](/docs), including result checks, undo and the human payment handoff.

## Related guide

[Distinguish other Cloudflare errors](/unblock/cloudflare)

---

Source: https://aluvia.io/unblock/rate-limit