How to Fix Cloudflare Error 1009 (Country or Region Blocked)

By ErrorFix · Updated October 22, 2026 · 5 min read

What Error 1009 means

Cloudflare's 1xxx error family covers DNS, proxy, and security-configuration problems, and Error 1009 sits in the security corner. The page reads "Access Denied" and says your country or region is banned, with a Ray ID printed at the bottom. That wording is the whole story: the owner of the website has banned the country or region your IP address appears to come from, and Cloudflare is simply enforcing their rule. The ban is not about you personally — it is about where your connection looks like it comes from.

It helps to keep 1009 straight from its neighbors, because they look similar but need different fixes. Error 1010 bans your browser's signature (Browser Integrity Check), Error 1015 rate-limits you for too many requests, Error 1020 matches a custom WAF rule the owner wrote, and Errors 1005 or 1006 through 1008 ban your network or IP address. Only 1009 is a country-wide ban. If your page says your country or region is banned, these are the right steps; if it says anything else, look up that exact code instead.

Common causes

• A deliberate country block by the site owner: the most common trigger. Owners block entire countries to stop fraud, abuse, or scraping from specific regions, or to limit their service to certain markets. If your whole country is on the list, every IP from there gets the 1009 page.
• Traveling abroad: the site works at home but shows 1009 on a hotel or roaming connection, because your IP now geolocates to a country the owner banned. This is the most common everyday encounter with this error.
• A VPN exiting in a banned country: your VPN server's country is what Cloudflare sees, not your physical location. One wrong server choice — or an auto-selected server abroad — puts you behind a foreign geo-block.
• An IP that geolocates incorrectly: carrier and corporate networks sometimes assign IPs whose geolocation records point to another country. You are really at home, but Cloudflare believes you are somewhere banned, and there is nothing on your device that can change that belief.
• An inherited or overly broad security rule: the owner may have copied a template rule, bundled countries into one block, or left an old rule in place long after the original threat passed — and never realized legitimate visitors were being turned away.

How to fix Error 1009 — step by step

Steps 1 through 4 are for visitors. Steps 5 and 6 are for site owners.

1. Confirm the page is a country or region ban, not a different block. Cloudflare's Error 1009 page reads Access Denied and states that your country or region is banned — sometimes shown as Errors 1009 Access Denied: Country or region banned, with a Ray ID at the bottom. This wording matters because neighboring codes look similar: 1010 bans your browser's signature, 1015 rate-limits you, 1020 matches a custom WAF rule, and 1005 or 1006 through 1008 ban your network or IP address. If your page says your country or region is banned, you are dealing with a geo-block and the steps below apply. If it says something else, look up that exact code instead.
2. Visitor: test whether your location is the trigger. The 1009 block is keyed to the country Cloudflare geolocates from your IP address, so check whether the site loads from a different place. Switch from Wi-Fi to mobile data, try the site in an incognito or private window with extensions off, or open it on a different device. If the site loads on mobile data but not on Wi-Fi, the blocked country is tied to one of your networks — for example a work VPN exiting in another country or a carrier whose IPs geolocate abroad. If the site fails everywhere, your whole country may be on the owner's banned list.
3. Visitor: switch to a network in an allowed country. If you are traveling, or your VPN exits in a country the owner banned, that is the most common everyday cause. Disconnect the VPN and reload, or change the VPN server to a country you know the site allows — your home country is the safest bet. Keep the same server location for the whole session, since hopping countries mid-session can trigger fresh blocks. If you suspect your IP is geolocated incorrectly (your carrier assigns you a foreign IP), test on another network and report the wrong geolocation to your internet provider.
4. Visitor: contact the site owner and ask to be allowed. Only the site owner can remove a 1009 block — Cloudflare support cannot override a customer's own security settings. Copy the Ray ID and the IP address shown at the bottom of the error page, then reach the owner through their contact email, social accounts, or support form. Tell them you are seeing Cloudflare Error 1009 (country or region banned), include your IP and Ray ID, and ask them to allow your IP address or your country. The Ray ID lets them find the exact blocked request in their Security Events log, which makes their job much faster.
5. Site owner: allow the visitor's country or IP under Security rules. Log in to the Cloudflare dashboard, select the domain, and go to Security, then Events to find the blocked request by its Ray ID — this shows which rule fired and the country Cloudflare detected. Then go to Security, then IP Access Rules (or your WAF custom rules, depending on your plan) and add an Allow rule: by country for everyone in that country, or by the specific IP address for a single visitor. Save the rule, then have the visitor reload — the block lifts immediately since the evaluation happens on the next request.
6. Site owner: replace blanket country blocks with lighter checks. Country-wide bans often catch legitimate visitors — travelers, VPN users, mis-geolocated carrier IPs, and search engine crawlers. Instead of a hard block, change the rule's action to Managed Challenge so real people in the country can still pass by completing a verification, and reserve blocking for patterns that actually look abusive. If you must block whole countries, review the Security Events log periodically for spikes of 1009 responses and keep an allowlist for known good traffic like payment gateways, certificate authorities, and search crawlers.

Did this fix it? Quick checklist

• The error page says your country or region is banned — you confirmed it is Error 1009, not 1010, 1015, or 1020
• You tested the site on another network (mobile data or a different Wi-Fi) to see whether the block follows your location
• If you use a VPN, you disconnected it or switched its server to a country the site allows, and kept that server for the whole session
• You sent the site owner your Ray ID and IP address and they added an Allow rule — the block lifts on the very next page load

If you are the owner and a visitor still reports 1009 after you allowed their country, double-check which rule is firing: look up their Ray ID under Security, then Events, because a second, more specific rule (for example a custom WAF rule or a lingering country entry) may be blocking them before the allow rule is evaluated. Also confirm Cloudflare's detected country matches reality — occasionally the geolocation data for an IP is stale, and the fix is to allow the actual country on the block instead of the one the visitor claims to be in.