Anycast and CDN exits: why some IPs look like they are everywhere
One IP, many locations. How anycast works, what it does to geolocation, and why a CDN edge is a poor identity for a store.
One address, many places
With anycast, the same prefix is announced from many PoPs. Routers send each user to the nearest one, so the "same IP" can serve users in Tokyo, Frankfurt and Virginia.
1.1.1.1 is the classic example. Traceroute from two countries can end in different cities for one address.
What that does to geolocation
IP geolocation databases are built from registration data, latency measurements and crowdsourced hints. Anycast breaks the assumption that an IP lives in one place:
- The registered country may differ from where you actually exit.
- City-level data can be wrong by hundreds of kilometres.
- Different databases disagree with each other.
This is why geolocation on CDN addresses is noisy, and why a "country mismatch" flag on a CDN IP should be read carefully.
Why a CDN exit is a bad store identity
- The address is shared by many unrelated users at the same time.
- It can change PoP between sessions without warning.
- Platform risk systems treat CDN edges as shared infrastructure, not as a household.
For browsing and reading, fine. For registration and seller accounts, use a stable address from a consumer ISP instead.
How to check
Ask: is the announcing AS a CDN (Cloudflare, Akamai, Fastly) rather than an ISP? Our checker labels the network type as CDN edge when that is the case — and the advice changes accordingly.