So I wass running a residental proxxy on my RackNerd /24 for hulu acceess (dont ask) and sudenly the whole /24 is blakclisted. Not just me. Everyoen on the samme subnet. Collectiv punisshment. I emaill suport and they say "terms of srvice violaton" but wont say who or what. Now I see other poeple on CloudCone and Hetzner panickign too. Same /24? No. Same ASN. Someoen is doign soemthign bad and we all pay. I refuse to edit this post ever.
-) you r lucky to have a /24 to get blocked honestly. But srsly this is why you dont run proxies on shared hosting. Back in my day we used 56k and AOL trial disks. RPKI didnt exist and we liked it that way :-)
Member
Fun little project gone wrong here. I had a NAT VPS on Hostinger in the same ASN—thought I was safe since no public IPv4, but Hulu apparently blacklisted the whole upstream. It actually works... worked, past tense. My config was simple:
wg-quick up wg0
iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADENothing fancy. Now everything times out to *.hulu.com.
Member
SWEdish "hösting" provider did this to me once. FIKA break and whole ASN gone. "SERver" at HostHatch, same ASN as tomhider? I am checking now. Yes. Same. Collective punishment is standard for streaming, they fika your traffic until you behave. I have moved to GreenCloudVPS https://greencloudvps.com with dedicated /24 and RPKI ROA. More expensive but no fika from Hulu.
Tomhider
I see the pattern
In your prior thread
C0570
You mentioned "rotation script"
Six exit IPs
Same telltale
TLS fingerprint
JA3: 4d6a7d...
I checked my logs
Matched
Your /24
The abuser
Was you
Different account
Same person
Ironic
Isnt it