Wikipedia:WikiProject Open proxies/Archives/Unblock/2009/December
This is an archive of past discussions on Wikipedia:WikiProject Open proxies. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current main page. |
222.166.160.232
- 222.166.160.232 · talk · contribs · block · log · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan
Reason: Sameboat has made an unblock request. עוד מישהו Od Mishehu 12:17, 2 December 2009 (UTC)
- {{notaproxy}}, IP unblocked. -- zzuuzz (talk) 12:27, 2 December 2009 (UTC)
207.73.252.254
- 207.73.252.254 · talk · contribs · block · log · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Belongs to a school district in Michigan ... if it's compromised, they'd probably like to know about it. Daniel Case (talk) 15:58, 9 December 2009 (UTC)
- {{notaproxy}} -- zzuuzz (talk) 16:17, 9 December 2009 (UTC)
119.82.248.67
- 119.82.248.67 · talk · contribs · block · log · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan
Reason: User talk:Meishern having collateral damage. Request a recheck of the IP address, or advice on whether IPBE would be appropriate in this case. Thanks! --Jayron32 22:01, 8 December 2009 (UTC)
- I checked it, it doesn't seem to be working anymore, but i'll have an admin verify that. Momo san Gespräch 15:33, 9 December 2009 (UTC)
- Inconclusive It's a large ISP closed proxy (proxy.ezecom.com.kh) with lots of proxy ports, and it routes traffic for lots of IPs. This user is undoubtedly collateral, rather than an open proxy user. It'll take a little while to conclude that this IP is not an open proxy. IPBE at your discretion - we'll probably be able to unblock this IP in the near future. -- zzuuzz (talk) 16:32, 9 December 2009 (UTC)
- Thanks. I'll issue an IPBE. The user's contribs indicate he's a good standing user editing in good faith, and I am inclined to believe he has no idea what is going on here. Feel free to revoke the IPBE if this IP address is unblocked. --Jayron32 18:18, 9 December 2009 (UTC)
- {{notaproxy}}, IP is now unblocked. -- zzuuzz (talk) 23:11, 11 December 2009 (UTC)
- Thanks. I'll issue an IPBE. The user's contribs indicate he's a good standing user editing in good faith, and I am inclined to believe he has no idea what is going on here. Feel free to revoke the IPBE if this IP address is unblocked. --Jayron32 18:18, 9 December 2009 (UTC)
- Inconclusive It's a large ISP closed proxy (proxy.ezecom.com.kh) with lots of proxy ports, and it routes traffic for lots of IPs. This user is undoubtedly collateral, rather than an open proxy user. It'll take a little while to conclude that this IP is not an open proxy. IPBE at your discretion - we'll probably be able to unblock this IP in the near future. -- zzuuzz (talk) 16:32, 9 December 2009 (UTC)
98.117.34.180
- 98.117.34.180 · talk · contribs · block · log · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan
Reason: Requesting an unblock. Anon claims it's no longer an open proxy. Nmap scan turns up 4567 as open. -Jeremy (v^_^v Stop... at a WHAMMY!!) 23:42, 10 December 2009 (UTC)
- {{notaproxy}}. This is not an open proxy, but it is the usual IP address of the recent open proxy talk page vandal. -- zzuuzz (talk) 09:27, 11 December 2009 (UTC)
194.106.220.19
- 194.106.220.19 · talk · contribs · block · log · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan
Reason: Unblock request reports a shared proxy, but claims it is not open. Requesting a more detailed investigation to see if unblocking is in order. --Jayron32 21:01, 17 December 2009 (UTC)
- {{notaproxy}} Exit for stale proxy, seems clean now. Q T C 06:42, 19 December 2009 (UTC)
149.169.218.77
- 149.169.218.77 · talk · contribs · block · log · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan
Reason: See User talk:Pkrecker. User is established, but infrequent, editor. Also seeking advice on IPBE if necessary in this case. --Jayron32 21:07, 17 December 2009 (UTC)
- {{notaproxy}}. Recently backdoored, apparently. -- zzuuzz (talk) 22:53, 21 December 2009 (UTC)
200.119.238.75
- 200.119.238.75 · talk · contribs · block · log · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Gogiva (talk · contribs) has requested removal of rangeblock; must be challenging this finding. Daniel Case (talk) 20:01, 23 December 2009 (UTC)
- According to active blocks, The IP in question is involved in a rangeblock. May want to look into an IP block exemption. Momo san Gespräch 20:33, 23 December 2009 (UTC)