Subnet
A subnet's a carved-out piece of a larger IP network. CIDR notation and a subnet mask define it, grouping IP addresses under a common routing domain. It makes traffic management and network segmentation more efficient. In large-scale proxy setups, subnets spread IP allocation across regions. Millions of residential IPs stay organized, routable, and manageable, dodging pattern-based detection.
Quick Facts
- Also known as
- Subnetwork, network segment, IP block
- IP source
- Residential IP pools segmented across regional CIDR blocks
- Detection risk
- Low , proper subnet diversity prevents IP block correlation
- Typical use
- Geo-targeted scraping, enterprise proxy routing, IP pool segmentation
- Price range
- $0.27–$0.79/GB
How a subnet works
When a proxy network gets a scraping request for a specific region, routing protocols send it to an IP from the subnet assigned to that area, using CIDR notation like 192.168.1.0/24 to define which addresses fit there. Each subnet has a subnet mask setting the range of usable IPs, helping you allocate dense address pools to high-demand regions and fewer to low-traffic areas. Geonode's got 2.5M+ residential IPs split this way over 195+ countries, so requests rotate across subnets instead of hitting one IP block. But just rotating subnets won’t fool anyone if you don’t randomize request timing and user-agent variance. Sites with ASN+GeoIP checks will still block dense subnets alone. Subnet diversity's needed, not a magic bullet.
Subnet vs. Full IP Pool
A full IP pool is your whole inventory of proxy addresses across the network. A subnet is a CIDR-defined piece tied to a routing domain or region. Targeting requests at the subnet level lets enterprise scrapers manage IP allocation for each market. For instance, you might lock a /20 block for EU e-commerce targets. Routing blindly over the full pool risks reusing IPs across regions, leading to bans.
Why this is different
Advantages
- Subnet isolation cuts IP reuse overhead by roughly 40% compared to full-pool rotation because each CIDR block stays scoped to one region and doesn't bleed into others. No cross-contamination here.
- A /20 block (4,096 IPs) keeps per-IP request rates under 5 req/min per target domain at 20K requests/min. If you're trying to avoid rate-limit flags from Cloudflare and Akamai, this helps a lot.
- Failures stay contained: burn a /24 block, and only 256 IPs take the hit, not your whole setup.
- Geographic isolation means if a German retailer flags your block, it doesn't mess with your UK IPs. Simple but effective.
Tradeoffs
- Larger subnets create more shared-IP abuse risk. A /16 block means 65,536 IPs share reputation history. One idiot messes up and everyone pays.
- IPv6 subnets need separate routing. Don't expect them to play nice with IPv4.
- Subnet exhaustion is real. Saturate your /22 and you'll have to expand or start queuing requests.
- Wrong subnet masks cause IP overlap. It's not fun when UK requests route through a US subnet, breaking geo-targeting.
Examples in practice
Real-world deployments of Subnet , where it works and where alternatives win.
Amazon Price Feed Scraping
Scraping Amazon feeds on 50+ subnets hits 10K requests/min per subnet. Go larger, like a single /20 at Amazon.com, and bam, you'll hit 503s fast.
Booking.com Rate Limit Bypass
UK traffic on Booking.com needs at least a /22 (256+ IPs) to dodge HTTP 429s. A /28 (16 IPs) will burn out in under 10 minutes at 2 req/sec. Booking.com triggers rate-limits at the ASN level.
Google SERP Rank Monitoring
Monitoring Google's search ranks needs /24 subnets per region. It covers over 195 countries, keeping request density low enough to avoid Google's automated query detection.
Alibaba and eBay Competitor Pricing
Scraping pricing on Alibaba and eBay with rotating IPs keeps requests under the abuse limits, around 1 req/sec per IP on eBay before CAPTCHAs show up.
Netflix Ad Placement Verification
Matching ad verification traffic on Netflix to organic viewership per region. This prevents spikes that stand out against normal user patterns.
Bloomberg and Reuters Financial Feed Access
Pulling market data from Bloomberg Terminal APIs and Reuters Eikon using /24 subnets stays under their thresholds. Watch out for those 500 API calls per hour restrictions on Bloomberg's commercial tier.
Common misconceptions
Common myths about Subnet , and what is actually true.
| Myth | Reality |
|---|---|
Two IPs in the same subnet are independent. | Reputation and bans often apply to the whole range, so same-subnet IPs share fate. |
A subnet is just a group of random IPs. | It is a contiguous, mathematically defined range based on the network mask. |
Subnet diversity doesn't matter for scraping. | Spreading across diverse subnets reduces correlated, range-level blocking. |
Need Subnets?
2.5M+ residential IPs, 195+ countries, from $0.27/GB.
