Spin up a farm on VPS - lose accounts before the first message. Run the same setup from a home PC - stable for months. Not luck. ASN classification - and after this article you'll know why datacenter is toxic for grey accounts and when VPS still makes sense.
Every network belongs to an autonomous system (ASN) classified as: commercial hosting (Datacenter), corporate/residential (Residential), or mobile (Cellular). This data is public and checked in milliseconds.
WhatsApp's antispam system checks incoming session ASN on WebSocket init. Hetzner, DigitalOcean, AWS, Vultr IPs - Datacenter pool. Used for industrial-scale spam bots. Reputation in these ranges is minimal by default.
Home and office internet - Residential pool. Same ranges used by families and businesses. Meta is lenient because bans there hit millions of real users.
No official Meta data on scoring specific providers. Practice is clear: accounts on hosting IPs die fast and predictably. More on three levels of infrastructure risk in a dedicated article.
Meta cross-checks at session login: SIM country code, IP geolocation, device timezone. Mismatch - signal.
Example: Russian or Kazakhstan number logs in via Hetzner server in Frankfurt. Number country - RU or KZ. IP - Germany. Timezone - anything depending on settings. Mismatch is instant and stacks on top of toxic datacenter ASN.
Home internet avoids this - IP geo matches number, timezone matches system. Looks like a normal local user.
Arbitrage team deployed automation on Windows VPS at Hetzner. Warmed accounts connected directly via server IP. Grid of 5 numbers got permanent ban within 10 minutes of session connect - before first commercial text. System reacted to toxic ASN, not content.
Reverse case: marketer set up 8 isolated antidetect profiles on home PC with regular dynamic IP. Accounts ran 2 months, 40–50 unique messages/day each, no captchas or blocks.
Common myth: "WhatsApp will link all accounts by one IP and ban the farm." Not true.
Offices and families routinely use multiple devices on one router with one external IP. Meta knows this and doesn't treat it as anomalous. What matters isn't session count on IP - it's profile quality and behavior pattern.
Operator benchmark: up to 10 accounts on one residential dynamic IP hold stable with basic hygiene. No official Meta threshold for when residential IP counts as a farm.
Home farm conditions:
Another myth: "Buy dedicated IP on Hetzner - it'll be clean." Dedicated IP may be clean of others' bans, but commercial datacenter ASN shows in first WHOIS line. Can't hide it. ASN reputation is primary; specific address history is secondary.
If you still need VPS for scale, some operators use residential proxies - IPs leased from real home users. Masks server nature.
Opinions split. Some say 2026 residential pools are heavily polluted and Meta detects them via frequent session drops and geo jumps within one session. Others call it workable with the right provider.
From the debate: residential proxies imitate home IP, they aren't it. Real home PC with live residential address stays more reliable for small farms.
Official WhatsApp Business API (Cloud API). IP type irrelevant - messages go through Meta infrastructure. Any hosting fine for backend, CRM integration, webhooks.
Grey scheme at large scale (50+ accounts). Home PC can't physically handle it. Only option - mobile or residential proxies from reliable providers with careful pool selection. Overlaps with why bulk services kill accounts on shared server infrastructure.
Passive OS Fingerprinting. Forum insiders claim Meta cross-matches ASN with TCP/IP stack params (MTU, TTL, Window Size). Linux server running Windows 11 antidetect - network flag mismatch may expose server nature. Unconfirmed, but plausible.
Device port scanning. Also forum-level: WhatsApp Web may probe local ports on auth. VPS often has RDP, VNC, virtualization ports open - not on home PC. No official data - another argument for real physical machine.
Both - unconfirmed community observations, not documented Meta mechanisms.
| Parameter | Datacenter (Hetzner etc.) | Home/office PC | Residential proxies |
|---|---|---|---|
| ASN reputation | ❌ Datacenter, toxic | ✅ Residential, clean | ⚠️ Pool-dependent |
| Geo match to number | ❌ Mismatch risk | ✅ Natural match | ⚠️ Geo jumps possible |
| Session stability | ❌ Ban before first message | ✅ Months if set up right | ⚠️ Drops possible |
| Scale (accounts) | ❌ Risky at any volume | ✅ Up to ~10 | ⚠️ For large farms |
| For WABA Cloud API | ✅ OK | ✅ OK | ✅ OK |
| Cost | Cheap | Free (own hardware) | Expensive ($/GB) |
If accounts run on VPS now - check which IP sessions use. If Datacenter ASN without residential proxies, moving to home PC or laptop with regular ISP is the first move before any other optimization.
Practical rule:
Datacenter saves server money and spends accounts. Home PC saves accounts and needs nothing extra.
