Cloudflare Edge Errors
Access Denied
Reviewed for reference consistency: August 11, 2026
Access Denied
What 1020 Means
The 1020 error on the Cloudflare Edge Errors indicates access denied. This typically occurs due to blocked by a web application firewall (waf) rule.
Error 1020 fires when a firewall rule owned by the site matches the request and blocks it before it reaches the origin server. Such blocks are deliberate configuration rather than an outage: managed WAF rules, country or ASN blocks, and custom user-agent filters all produce this page.
Technical Background
Unlike 1015, which throttles request volume, 1020 is about content and identity: the edge inspected the request and matched a rule the site owner configured.
The Ray ID printed on the page lets the site administrator find the exact matching rule in the Security Events log.
Common Causes
- Blocked by a Web Application Firewall (WAF) rule
- Country or ASN block enforced by the site owner
- A custom firewall rule rejecting specific user agents
Typical Scenarios
- A request carrying an SQL-injection pattern trips a managed WAF rule
- An administrator blocks traffic from a region where the site does not operate
What to Know
An accidental block is reversed on the site side: the owner traces the Ray ID to its rule and adjusts or removes it. Visitors cannot bypass the page, because the decision happens at the edge before the origin is consulted.
Frequently Asked Questions
Common questions about Cloudflare 1020 error
The site's own firewall matched a rule — a managed WAF filter, a country or ASN block, or a custom user-agent rule — and stopped the request at the edge.
No. The block comes from rules the website owner configured; Cloudflare's edge only enforces them. Reversing an accidental block happens in the site's firewall settings, not in Cloudflare's status.
Related Error Codes
Related Errors From Other Categories
Similar error codes documented across different platforms and systems
Process Killed — the process was terminated by a SIGKILL signal
Signal 11 (SIGSEGV) — kernel signal for invalid memory reference segmentation fault
Exit Code 139 — process terminated by segmentation fault (Signal 11 / SIGSEGV)
Input/output error EIO — a read or write operation could not complete