Cloudflare Error 1015: you are being rate limited
Treat 1015 as a rate-limit response. Identify the request pattern, affected client identity and configured threshold before increasing limits or disabling a control. Slow or stop the offending pattern first. This source-reviewed guide keeps the next step tied to the evidence you can collect safely.
Capture the exact symptom and scope first
Treat 1015 as a rate-limit response. Identify the request pattern, affected client identity and configured threshold before increasing limits or disabling a control. Slow or stop the offending pattern first.
- Record the exact visible message and timestamp.
- Check whether the symptom affects one target or several.
- Preserve the relevant log, response or configuration state.
- Choose the next step only after identifying the affected layer.
Why this branch first: The exact error, timestamp and scope determine the next branch more safely than broad resets or deletes.
Choose a local-first diagnostic tool
Use a TroubleByte tool to inspect an error, DNS record or local system context before changing settings.
TroubleByte diagnostic path
Record route, client and rate.
Find the matching limit.
Reduce unexpected request bursts.
Verify intended traffic without broad bypasses.
Original TroubleByte diagnostic map. It summarizes the cited troubleshooting order; it is not a vendor screenshot.
Use the symptom to choose the next branch
Does the evidence point to one affected target rather than a wider platform or network failure?
Keep the investigation narrow and correct the affected target or configuration only.
Stop making isolated changes and investigate the shared host, network, storage or platform layer.
Do you have the exact message, timestamp and relevant log or response evidence?
Use that evidence to follow the scoped diagnostic flow and verify one targeted change.
Capture it first; broad resets, deletes and policy changes are premature.
Original TroubleByte decision aid derived from the cited troubleshooting scope. It does not replace vendor documentation.
What this usually means
Cloudflare documents Error 1015 as a rate-limiting condition. It indicates that a request pattern exceeded a configured or platform-enforced threshold; it does not prove the client is malicious or that the origin is down. The safe diagnostic split is whether one client, route, credential or automated workflow exceeds the limit, then whether the configured rule matches intended traffic.
What we verified from the source material
Cloudflare documents Error 1015 as a rate-limiting condition. It indicates that a request pattern exceeded a configured or platform-enforced threshold; it does not prove the client is malicious or that the origin is down. The safe diagnostic split is whether one client, route, credential or automated workflow exceeds the limit, then whether the configured rule matches intended traffic.
Prerequisites and checks
Prepare first
- Do not disable a broad rate-limit rule merely to restore one client.
- Use a controlled client or test token when reproducing API traffic.
- Preserve the threshold and action before editing a rule.
Checks that prevent the wrong fix
- Capture the affected URL, timestamp, client identity and request rate.
- Check whether the problem affects one route or all site traffic.
- Review the matching rate-limit rule or relevant product limit before changing it.
Applies to
Solutions, in order
Capture the exact symptom and scope first
- Record the exact visible message and timestamp.
- Check whether the symptom affects one target or several.
- Preserve the relevant log, response or configuration state.
- Choose the next step only after identifying the affected layer.
Why this can work: The exact error, timestamp and scope determine the next branch more safely than broad resets or deletes.
Match the response to the request pattern and limit
- Capture the affected route and request pattern.
- Find the relevant rate-limit event or rule.
- Reduce or correct the client request behavior where possible.
- Change only the threshold or exception that the evidence supports.
Why this can work: Apply a narrow correction that follows the observed evidence, then verify the original symptom is gone.
How to know the fix actually worked
- Confirm the intended request rate succeeds after a narrow correction.
- Confirm abusive or excessive patterns remain limited as designed.
Do not count a temporary disappearance of the symptom as a confirmed fix if the problem normally returns after a restart, reconnect or several minutes of use.
When not to keep changing things
- If the traffic is unexpected, credentialed or costly, stop before raising thresholds and investigate the client or automation first.
Escalation: Escalate with route, timestamp, client identifier, request rate and matching rule configuration—not only a screenshot of 1015.
Sources used for this record
Primary · checked Sep 25, 2026Cloudflare — Cloudflare 1xxx errorsOfficial documentation used to verify the scoped troubleshooting guidance.Corroborating · checked Sep 25, 2026Cloudflare — Error diagnostic headersOfficial documentation used to verify the scoped troubleshooting guidance.Discuss this exact problem
Share what happened on your system, ask a focused follow-up question, or add evidence that may help someone with the same symptom. Community posts are separate from TroubleByte editorial verification.
Start a discussion
Revision history
Show 1 recorded revision
2026-09-25 — Created from current official documentation with scoped decisions, explicit stop conditions and an original TroubleByte diagnostic diagram.