Why Nepali Visitors Get Blocked From Your Website — Especially on Hostinger
If Nepali visitors report your website won't load — but it works fine from other countries — this is likely why. We're seeing this most on Hostinger-hosted sites in particular.
The Cause
Nepal has limited IPv4 addresses, so ISPs like WorldLink and Vianet share one public IP across many customers (CGNAT). If even one person on that shared IP does something abusive, the whole IP gets a bad reputation on AbuseIPDB — and hosting providers auto-block flagged IPs at the firewall level.
Hostinger is the provider most affected by this. Its firewall leans heavily on AbuseIPDB and similar blocklists, and its own support docs confirm it auto-blocks IPs based on these scores — which is why this issue shows up so consistently on Hostinger-hosted sites compared to other hosts. Innocent users sharing the same flagged IP get blocked too, through no fault of their own.
Contacting your ISP won't fix this long-term — the IP gets reused and re-flagged.
Two Fixes
1. Add an IPv6 (AAAA) record IPv6 addresses aren't shared the same way, so they're rarely flagged. Easy to add, but only works if the visitor's device/ISP supports IPv6 (not universal in Nepal yet).
2. Enable Cloudflare Proxy (recommended) Routes traffic through Cloudflare so your real server IP is never exposed. Even if your Hostinger IP is blacklisted, visitors never touch it directly. Also gives you free DDoS protection and caching.
- Move DNS to Cloudflare → keep the record's cloud icon orange (Proxied).
Check It Yourself
Go to abuseipdb.com/check → enter the IP → check the abuse score. A shared ISP IP with a non-zero score confirms this is the issue.
Bottom Line
This is a shared-IP reputation problem, not a bug in your site — and if you're on Hostinger, you're more likely to run into it than on most other hosts. IPv6 helps partially; Cloudflare proxy is the more complete fix.
Sources: AbuseIPDB · Hostinger support · Cloudflare — CGNAT bias research