> But first, the basic cause of this issue is not the VPN per se. Google simply sees a large volume of traffic coming from a single IP address, with no way of knowing that it's a VPN. The same behaviour has been reported by students of large educational institutions, where there is a large volume of users trying to connect to Google Scholar through the institution's single public IP address. The reality that there are hundreds, thousands or perhaps hundreds of thousands of individual users behind an IP address is not known to Google. The VPN provider or institution's network keeps track of the individual users while presenting a single connection to Google. There may be a rogue user somewhere on the network, or it may simply be the sheer number of attempted connections that triggers the blocking, but the point is that it has gone past the point of a CAPTCHA. I guess it's similar to power load shedding on an electricity network.
PING 1.1.1.1 (1.1.1.1): 56 data bytes
64 bytes from 1.1.1.1: icmp_seq=0 ttl=52 time=241.529 ms
64 bytes from 1.1.1.1: icmp_seq=1 ttl=52 time=318.034 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=52 time=337.291 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=52 time=255.748 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=52 time=247.765 ms
64 bytes from 1.1.1.1: icmp_seq=5 ttl=52 time=235.611 ms
64 bytes from 1.1.1.1: icmp_seq=6 ttl=52 time=239.427 ms
64 bytes from 1.1.1.1: icmp_seq=7 ttl=52 time=247.911 ms
64 bytes from 1.1.1.1: icmp_seq=8 ttl=52 time=260.911 ms
64 bytes from 1.1.1.1: icmp_seq=9 ttl=52 time=281.153 ms
64 bytes from 1.1.1.1: icmp_seq=10 ttl=52 time=300.363 ms
64 bytes from 1.1.1.1: icmp_seq=11 ttl=52 time=234.296 ms
No JavaScript at all