Hacker News Reader

Comment by yegor | Hacker News Reader

There are ways to get around it. I'm confident you will see much fewer CAPTCHAs on our network, as we have mitigations in place for it.

View on HN

I don't know much about VPNs but that statement is one of my red flags: when a VPN provider is vague about ip reputation migrations I assume they're buying residential proxys.

We do use those for geo-unblocking, but they're not used for anti-CAPTCHA mitigations. We own and operate special purposes ASes and IP prefixes for that.

All of this can also be (verifiably) disabled by the end user in the web control panel.

> We own and operate special purposes ASes and IP prefixes for that.

The part that seems shady to me is how you do this without being caught by the up database providers are marked as a non-residential ip.

My read of GP's reply is: they use residential proxies to get around geo-blocking, and separately have special purpose ASs to avoid captchas. They're separate solutions serving separate needs; connecting to Netflix gets you the residential IP, regular browsing would get you the other one.

> We do use those for geo-unblocking

What steps, if any, are you taking to make sure you are sourcing your residential proxies ethically? Honest question.

Impossible unless you have a number of IP addresses that gets close to your total number of customers online.

As soon as a service starts seeing a dozen users from a single IP, they're gonna start throwing CAPTCHAs on them more.

A single IPv6 /32 contains 4 billion /64s. Most CAPTCHA delivery domains support IPv6.

Reply on news.ycombinator.com