User talk:176.123.13.14

This user's unblock request has been reviewed by an administrator, who declined the request. Other administrators may also review this block, but should not override the decision without good reason (see the blocking policy).

176.123.13.14 (block log • active blocks • global blocks • contribs • deleted contribs • filter log • creation log • change block settings • unblock • checkuser (log))

---

Request reason:

My internet connection. 176.123.13.14 (talk) 20:36, 7 May 2021 (UTC)

Decline reason:

I am declining your unblock request because it does not address the reason for your block, or because it is inadequate for other reasons. To be unblocked, you must convince the reviewing administrator(s) that

• the block is not necessary to prevent damage or disruption to Wikipedia, or
• the block is no longer necessary because you
  1. understand what you have been blocked for,
  2. will not continue to cause damage or disruption, and
  3. will make useful contributions instead.

Please read the guide to appealing blocks for more information. 331dot (talk) 07:37, 8 May 2021 (UTC)

---

If you want to make any further unblock requests, please read the guide to appealing blocks first, then use the {{unblock}} template again. If you make too many unconvincing or disruptive unblock requests, you may be prevented from editing this page until your block has expired. Do not remove this unblock review while you are blocked.

This user's unblock request has been reviewed by an administrator, who accepted the request.

176.123.13.14 (block log • active blocks • global blocks • contribs • deleted contribs • filter log • creation log • change block settings • unblock • checkuser (log))

---

Request reason:

This is my normal internet connection at the cottage, for which I pay for an internet provider, a regular provider in the Czech Republic. I've never damaged anything and I don't understand why blocking my IP address should be useful or evan necessary. I don't know what anyone else did from this address before, but I don't even see any edits there.

Accept reason:

I've changed the block so that it should leave out the residential range. SQL^{Query me!} 04:41, 13 May 2021 (UTC)

• 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 • work) 13:55, 11 May 2021 (UTC)

@Anarchyte: 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. @Ivanvector: 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)

@Ivanvector: 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)

---