[PT-BR TRANSLATION PLACEHOLDER] This file requires Brazilian Portuguese translation.
ORIGINAL CONTENT:
What Is an Autonomous System Number (ASN)?
An Autonomous System Number is a globally unique identifier assigned by a Regional Internet Registry — ARIN in North America, RIPE NCC in Europe, APNIC in Asia-Pacific, and their counterparts elsewhere — to a network operator that controls a distinct set of IP routing policies. Defined formally in IETF RFC 1930, an Autonomous System (AS) is essentially an independently managed routing domain: Comcast, Verizon, T-Mobile, BT, Deutsche Telekom, Jio, Telstra, and thousands of smaller ISPs each operate one or more ASNs. Cloudflare Radar publishes real-time per-ASN traffic data, illustrating just how granularly the internet is segmented into these distinct network identities.
When your device connects to the internet, every packet it sends carries metadata that allows routers to trace it back through BGP (Border Gateway Protocol) routing tables to a specific ASN. That ASN is publicly queryable — anyone, including a contest platform, can look up the operator behind any IP address in under a millisecond.
Why ASN Diversity Matters in Vote Services
Imagine an order of 1,000 votes where every IP belongs to the same ASN — say, a single regional cable operator in Ohio. From the contest platform’s perspective, 1,000 voters all use the same ISP, something that would almost never happen organically unless the contest was hyper-local to one neighbourhood. Statistical anomaly detectors would flag the pattern within seconds.
Real contest traffic is diverse. A genuine surge of 1,000 voters arrives from Comcast subscribers in three US states, Virgin Media users in the UK, Deutsche Telekom customers in Germany, Jio mobile users in India, and dozens of smaller local ISPs in between. The distribution mirrors the natural heterogeneity of the internet.
ASN diversity is therefore not cosmetic — it is a structural requirement for making a vote campaign statistically indistinguishable from organic engagement. Providers who draw from a small pool of IPs inevitably concentrate their delivery within a handful of ASNs, and contest platforms with even modest analytics capability can identify the signature.
How Detection Systems Use ASN Signals
Contest fraud detection layers that specifically target ASN patterns include:
- ASN concentration scoring — the platform calculates what percentage of incoming votes originate from each ASN. A threshold rule (e.g., “reject if more than 5% of votes in any 10-minute window share one ASN”) catches concentrated deliveries even if individual IPs are unique.
- Hosting-provider ASN blocklisting — ASNs registered to data centres, CDN providers, and commercial VPN services appear on maintained blocklists. Any vote from these ASNs is rejected regardless of other signals. This is the mechanism described in Spamhaus’s BGP blocklist documentation.
- ASN velocity analysis — if a large number of votes from a single ASN arrive faster than normal human browsing patterns would allow, the platform treats it as automated. This is why per-ASN rate limits matter even within a diverse delivery.
- Cross-platform correlation — shared industry fraud databases allow platforms to correlate ASN patterns observed on one voting system with patterns seen on another. An ASN that appears heavily in fraud submissions across multiple platforms gets elevated suspicion scoring network-wide.
The combination of these signals means that providers without deep, multi-ASN pools cannot evade detection by simply ensuring IP uniqueness — the ASN layer catches them even if individual addresses are fresh.
How to Verify Quality
Evaluating ASN diversity in a vote service requires asking specific questions:
- How many distinct ASNs does a 1,000-vote order span?
- What is the maximum percentage of any single order that comes from one ASN?
- Does the provider include ASNs from multiple countries and carriers in a standard global order?
- Is there an exclusion list for known VPN and hosting ASNs?
- Can the provider show a sample ASN distribution report for a completed order?
Any credible residential IP provider should be able to provide at least approximate answers; a provider that cannot describe their ASN diversity in any meaningful way is almost certainly working from a concentrated or proxy-based pool.
How Our Service Uses This Technique
Our delivery infrastructure enforces hard per-ASN caps on every order. No single Autonomous System contributes more than a small fraction of any campaign, regardless of order size. Our pool spans hundreds of distinct ASNs across the 200+ countries we serve — cable and DSL operators, fibre providers, and 4G/5G mobile carriers — meaning that even a 20,000-vote order produces an ASN distribution that mirrors the natural spread of internet users across networks and geographies. We maintain a continuously updated exclusion list covering 200+ ASNs associated with commercial VPN services and hosting providers; these are filtered out automatically so that no order inadvertently routes through a network segment that triggers blocklist hits. When a contest operator is known to apply custom ASN restrictions, our routing logic switches to alternative pool segments without requiring customer action.
Summary. ASN diversity means spreading vote delivery across many independent network operators so that no single ISP contributes a detectable concentration. Detection systems enforce per-ASN thresholds, maintain hosting-provider blocklists, and apply velocity analysis to catch concentrated deliveries even when individual IPs are unique. Our system enforces per-ASN caps across a pool spanning hundreds of networks and 200+ countries, producing traffic distributions that are structurally consistent with organic internet usage.
