User talk:176.123.13.14


 * Comment: The Proxy API Checker seems to think this individual IP is fine, but because it's a range block we can't just unblock this one. Anarchyte  ( talk  &#8226;  work ) 13:55, 11 May 2021 (UTC)


 * Unblocking around the /22 would probably be fine. We'd likely need to reblock 176.123.0.0/21 and 176.123.8.0/22, as they both seem to be owned by AlexNet. I'm on the fence about 176.123.16.0/20, it seems that they offer hosting, colocation, vps, asdl, wimax, and fttx. What are your thoughts?  SQL Query me!  20:34, 11 May 2021 (UTC)
 * I'm not sure what to say about this. The range is AlexHost, a webhost and colocation provider in Moldova - they don't appear to offer residential services at all so I'm curious how the user is getting internet access on one of their IPs unless they're being routed to a proxy or VPN running on AlexHost's services. I'm concerned that AlexHost is a DMCA-ignored hosting provider, but I don't know if that matters for our purposes. My block is related to a common ANI vandal known to use open proxies landing on this range, but this isn't a checkuser block - if you think you can adjust the blocked ranges to accommodate the user, please feel free. Ivanvector's squirrel (trees/nuts) 19:00, 12 May 2021 (UTC)
 * Thanks for your reply! It looks like AlexHost sub-delegates 176.123.12.0/22, which is currently assigned to https://www.metropolitni.cz, a residential provider. A weird setup for sure. I'll unblock the /19, and break up the blocks per my plan above. SQL Query me!  04:38, 13 May 2021 (UTC)
 * Thanks. I am from Czech Republic, not Moldova. --176.123.13.14 (talk) 18:33, 14 May 2021 (UTC)