How to Choose the Right Subnet Size for Proxy Pools: A Guide for Scraping and Arbitrage

When purchasing proxies for scraping, multi-accounting, or arbitrage, you have likely encountered the parameter "subnet size" — /24, /26, /29, and others. Many ignore this setting, only to later face mass bans of the entire proxy pool. In this guide, we will explore what a subnet is, how it affects the security of your tasks, and how to properly choose the size for different working scenarios.

A subnet defines how "close" the IP addresses in your proxy pool are located. An incorrect choice can lead to chain bans — when the ban of one IP affects all other addresses in the same subnet. This is especially critical for working with Facebook Ads, Instagram, scraping marketplaces, and other tasks where platforms actively monitor suspicious activity.

What is a subnet and how does it work

A subnet is a range of IP addresses that belong to the same logical group. When you purchase a proxy pool, the provider may assign you addresses from the same subnet or different ones. This is determined by the subnet mask parameter, which is written in the format /24, /26, /29, and so on.

The number after the slash indicates how many bits in the IP address are reserved for identifying the network. The smaller this number, the more addresses are included in one subnet. For example:

• /24 — the subnet contains 256 IP addresses (e.g., 192.168.1.0 — 192.168.1.255)
• /26 — the subnet contains 64 IP addresses
• /29 — the subnet contains 8 IP addresses
• /30 — the subnet contains 4 IP addresses

Why is this important? Many platforms (Google, Facebook, Instagram, Wildberries) track not only specific IP addresses but entire subnets. If suspicious activity arises from a /24 subnet — mass account registrations, scraping, manipulation — the platform may block the entire subnet. This is called a chain ban.

Differences between /24, /26, /29, and other sizes

Let's examine the main subnet sizes offered by proxy providers and their practical significance for various tasks.

Subnet /24 — the most common and cheapest option. All 256 addresses are in one subnet, making them vulnerable to mass bans. Suitable only for simple tasks where bans are not critical: scraping public data, checking website availability, SEO position monitoring.

Subnet /26 — an intermediate option. A pool of 100 proxies will be distributed across at least 2 subnets (of 64 addresses each). This reduces the risk of chain bans but does not eliminate them entirely. Optimal for scraping marketplaces (Wildberries, Ozon), monitoring competitors' prices, and collecting contacts.

Subnet /29 — more isolated IPs. A pool of 100 proxies will be distributed across at least 13 subnets (of 8 addresses each). Even if one subnet gets blocked, you will lose a maximum of 8 proxies out of 100. Recommended for traffic arbitrage, multi-accounting on social media, and working with anti-detect browsers (Dolphin Anty, AdsPower).

Subnet /30 and above — maximum isolation. Every 2-4 IP addresses are in a separate subnet. This is a premium option for critical tasks: farming Facebook Ads accounts, managing expensive client Instagram accounts, working with banking and payment systems.

How a subnet affects bans and chain bans

A chain ban is a situation where the platform blocks not just one IP address but the entire subnet. This happens when the anti-fraud system detects suspicious activity from several IPs in the same subnet and concludes that the entire subnet belongs to one violator or botnet.

How platforms identify suspicious subnets:

• Mass account registration — if 50 Facebook accounts are registered from a /24 subnet within an hour, this is a clear sign of automation
• Similar behavior — all accounts perform similar actions (likes, follows, posts) at the same time
• Scraping — thousands of requests to APIs or web pages from one subnet in a short time
• Suspicious fingerprints — different accounts from one subnet have similar browser fingerprints, despite using anti-detect tools

For working with datacenter proxies, the subnet is particularly critical, as these IPs are initially under close scrutiny from anti-fraud systems. If you are using datacenter proxies for arbitrage or multi-accounting, be sure to choose a subnet of /29 or smaller.

Choosing a subnet for scraping and data collection

Scraping is a task where the subnet affects the stability of operation and the number of successful requests. Different types of scraping require different levels of IP address isolation.

Simple scraping of public data (news, articles, open directories):

• Optimal subnet: /24 — /26
• Why: These sites rarely block subnets; simply rotating IPs is sufficient
• Number of proxies: 10-50 per task
• Rotation speed: every 5-10 requests

Scraping marketplaces (Wildberries, Ozon, Yandex.Market):

• Optimal subnet: /26 — /29
• Why: Marketplaces actively combat scrapers and monitor subnets
• Number of proxies: 50-200 per task
• Rotation speed: every 2-5 requests
• Additionally: Use delays between requests (2-5 seconds), simulate human behavior

Scraping social media (Instagram, VK, Facebook):

• Optimal subnet: /29 or different subnets
• Why: Social networks have powerful anti-fraud systems and aggressively block subnets
• Number of proxies: 100+ per task
• Proxy type: Better to use residential proxies instead of datacenter
• Rotation speed: every request or every 2-3 requests

Scraping with authorization (restricted sections of websites, personal accounts):

• Optimal subnet: /30 or different subnets
• Why: Each account must have its "own" IP; changing IP during a session raises suspicions
• Number of proxies: 1 proxy = 1 account
• Sticky sessions: Always use sticky sessions — one IP for the entire working period

Optimal subnet for arbitrage and advertising accounts

Traffic arbitrage is one of the most demanding tasks for proxy quality and subnet. Facebook Ads, TikTok Ads, Google Ads have advanced multi-accounting detection systems that analyze not only IPs but also subnets, ASN (autonomous systems), geolocation, and many other parameters.

Farming Facebook Ads accounts:

• Minimum subnet: /29 (8 IPs in the subnet)
• Recommended subnet: /30 (4 IPs in the subnet) or different subnets
• Proxy type: Mobile proxies — the lowest risk of bans
• Rule: 1 proxy = 1 Facebook account for the entire lifecycle
• Do not change IP after warming up the account — this will raise suspicions

Launching TikTok Ads campaigns:

• Optimal subnet: /29 — /30
• TikTok is less strict about subnets than Facebook, but still monitors patterns
• Datacenter proxies with a good reputation can be used
• Always use an anti-detect browser (Dolphin Anty, AdsPower) with unique fingerprints

Google Ads and Yandex.Direct:

• Optimal subnet: /26 — /29
• Google and Yandex are more lenient towards multi-accounting if accounts do not violate rules
• One /26 subnet can be used for 10-15 accounts
• The main thing is not to launch prohibited offers and not to violate advertising policies

Arbitrage of cryptocurrency offers:

• Optimal subnet: /30 or different subnets
• Crypto offers are often banned, so maximum isolation is needed
• Use residential or mobile proxies from different countries
• Change the proxy pool every 2-4 weeks to reduce risk

Subnet for multi-accounting on social media

Multi-accounting on Instagram, TikTok, VK, Telegram requires a special approach to choosing a subnet. Social networks continuously improve algorithms for detecting related accounts, and the subnet is one of the key parameters by which they determine connections.

Managing client accounts (SMM agency):

• Optimal subnet: /29 or different subnets
• Why: Each client account must appear independent
• Number of proxies: 1 proxy = 1-3 accounts maximum
• Use sticky sessions — one IP for the entire month of working with the account
• Set up in Dolphin Anty or AdsPower to bind profiles to proxies

Mass posting and automation (Instagram, TikTok):

• Minimum subnet: /26
• Recommended subnet: /29
• If using automation (bots for likes, follows), the subnet is critical
• Instagram easily identifies mass actions from one /24 subnet
• Add random delays between actions: 30-120 seconds

Farming accounts for sale:

• Optimal subnet: /29 — /30
• Farming accounts is a high-risk task; the subnet must be as isolated as possible
• Register no more than 5-10 accounts per day from one subnet
• Use mobile proxies — they are less likely to fall under chain bans
• Warm up accounts for at least 2 weeks before selling

Working with VK and Telegram:

• Optimal subnet: /26 — /29
• VK and Telegram are less strict about subnets than Western social networks
• Datacenter proxies with a /26 subnet can be used
• The main thing is not to spam and not to violate platform rules

How a subnet affects the cost of proxies

The subnet directly affects the cost of the proxy pool. The smaller the subnet (greater isolation), the more expensive the proxies. This is because it is more challenging for the provider to allocate IP addresses from different subnets — it requires more IP space and complicates infrastructure management.

It is important to understand that saving on the subnet can lead to much greater losses. For example:

• You bought 100 /24 proxies for 5000 rubles
• Alternative: 100 /29 proxies for 6500 rubles (+30%)
• After a chain ban, you lost all 100 /24 proxies = loss of 5000 rubles + time for setup
• With /29 proxies, you would have lost a maximum of 8-10 IPs = loss of 520-650 rubles
• Conclusion: an overpayment of 1500 rubles would have saved you 4500 rubles and a week of work

Practical recommendations for setup

Choosing a subnet is just the first step. It is important to properly configure the use of the proxy pool to minimize the risk of bans and maximize work efficiency.

1. Load distribution across subnets:

• Do not use all IPs from one subnet simultaneously
• If you have a pool of 100 /26 proxies (2 subnets of 64 IPs), distribute tasks: 50 IPs for scraping, 50 IPs in reserve
• Rotate subnets: work with the first for a week, then switch to the second
• This reduces the likelihood that the platform will notice a pattern of activity

2. Monitoring the health of subnets:

• Keep logs: which IPs from which subnet received a ban
• If 10+ IPs from a /24 subnet are blocked — the entire subnet is at risk, stop using it
• Use IP checking tools: whoer.net, 2ip.ru, scamalytics.com
• Check the blacklist status of subnets once a week

3. Combining different types of proxies:

• For critical tasks (Facebook Ads), use mobile proxies with a /30 subnet
• For scraping — datacenter proxies with a /26 subnet
• For warming up accounts — residential proxies with different subnets
• Do not mix proxy types for one task — this creates a suspicious pattern

4. Configuration in anti-detect browsers:

• In Dolphin Anty / AdsPower, create tags to group profiles by subnets
• Example: tag "subnet_192.168.1" for all profiles on IP 192.168.1.x
• If one subnet is compromised, you can quickly find all related profiles
• Set up automatic proxy rotation within the subnet (if using /24)

5. Testing before scaling:

• Purchase a test pool of 10-20 proxies with the desired subnet
• Test the operation on your task for 1-2 weeks
• If there are no bans — scale up to the required volume
• If there are bans — reduce the subnet (/26 → /29) or change the type of proxy

Conclusion

Subnet size is a critically important parameter when choosing a proxy pool, directly affecting the risk of bans and work efficiency. For simple scraping, a subnet of /24-/26 is sufficient; for multi-accounting and SMM, a minimum of /29 is needed, while for arbitrage and farming Facebook Ads — /30 or different subnets.

Key takeaways from the article:

• Subnet /24 contains 256 IPs — high risk of chain bans, suitable only for simple tasks
• Subnet /29 contains 8 IPs — optimal balance of price and security for most tasks
• Subnet /30 and different subnets — maximum isolation for critical tasks
• Overpayment for a smaller subnet (20-30%) pays off by reducing the risk of bans
• Always test proxies on a small pool before scaling

If you plan to work with scraping, arbitrage, or multi-accounting, we recommend starting with residential proxies with a /29 subnet — they provide the optimal balance of price, security, and operational stability. For tasks where speed is critical and high anonymity is not required, datacenter proxies can be used, but with a mandatory subnet of /26 or smaller.

Remember: saving on the subnet can result in losing the entire proxy pool and associated accounts. Choose the subnet based on the task, not just the price.