IPv6 Subnet Banning on Instagram / Google

[VayneSimp]

I recently set up a /32 IPv6 Subnet on a Tier 1 US ISP, which I would consider pretty large to proxy instagram requests (few million per day)
I also have some friends that do google search requests, and the whole subnet now got

blocked from google search (receiving 403's only) &
blocked from instagram (receiving 429's only)

I now routed another fresh /32 from RIPE to my proxy server and set it up, to my surprise this fresh subnet that was never used was ratelimited from Instagram already (different RIPE org)
The 2 ranges are also not from the same /29 range that RIPE assigns, so now I am really wondering how they determine to ban such large ipv6 subnets.
At least google search works on the new /32 I set up.

If anyone has some insights on that I would be really happy

 

[maxpaincode]

If you were sending a couple of million then it makes sense you have to be stealth with that kind of stuff

 

[Deleted member 1686433]

If you were sending a couple of million then it makes sense you have to be stealth with that kind of stuff

Obviously he must be taking care of the requests, he is questioning about new ip ranges from different provider which got blocked without prior use

to my surprise this fresh subnet that was never used was ratelimited from Instagram already

So this is what i assume
Either the particular range from your new provider had bad ip reputation history (maybe their ip pool itself)
Or if your request failed after first response, they probably detected same pattern from your previous requests and blocked the ip
Im not networking expert but with my limited scraping experience thats all i can think of