Requested Unblock

202.27.212.175

202.27.212.175 · talk · contribs · block · log · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan

Reason: Requested unblock via unblock-en-l. I didn't see anything immediate, and all the google posts look old when the block was placed in '08. So I have unblocked for now. -- DQ (t) (e) 17:14, 4 June 2011 (UTC)[reply]

Seems reasonable to unblock, hash.es has last good in august of 2010, so it's likely dead. Whois indicates a wholesale provider, so it may have been reassigned and now interfere with genuine editors. Sailsbystars (talk) 00:54, 5 June 2011 (UTC)[reply]

202.49.134.179 · talk · contribs · block · log · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Sorry this was the original range that was blocked, the above IP looks like a closed proxy if a proxy on 3128 no? -- DQ (t) (e) 17:38, 5 June 2011 (UTC)[reply]

Additional Note: This IP had the IP above noted in it's block log. Also the IP listed is inactive on hash.es also. -- DQ (t) (e) 17:45, 6 June 2011 (UTC)[reply]

I think we're on the same page here 202.27.212.175 on 8080 was originally the access point for a proxy that showed up as edits from 202.49.134.179. And perhaps 202.49.134.179 was also a proxy all by itself. However, neither responds as a proxy on 8080 anymore. 202.49.134.179 is open on 3128, as you indicated but some googling reveals that it belongs to a dialup isp. Dialup ISPs frequently used closed proxy type services to accelerate downloads, so given that fact and the fact it doesn't proxy for me, I think we can close this case. Sailsbystars (talk) 01:30, 7 June 2011 (UTC)[reply]

217.173.49.82

217.173.49.82 · talk · contribs · block · log · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan

User:Alloutlenses (edit | talk | history | links | watch | logs)

User Alloutlenses (talk · contribs) requests that proxy be unblocked. I initially set block to "Anonymous users only" but reverted and decided to bring it here instead. I saw no abuse on the IP address.--v/r - T P 15:25, 18 June 2011 (UTC)[reply]

Thanks - please don't ever lift a proxy block without first confirming that the proxy is either not open or otherwise offline. ProcseeBot generally knows what it's doing. Anyway, port scan on this IP address shows that port 80 is open. It appears to be some sort of administrative login point for a Cisco router, asking for a username and password with the message "level_15_access". Port 23 is also open, running a telnet service, and port 25 (SMTP) is filtered. All other ports are reported as closed. Hersfold ^(t/a/c) 16:13, 18 June 2011 (UTC)[reply]

Forgot to mention: checkuser indicates that this IP address is not the subject of abuse, nor are the /29 and /20 network blocks it's a part of. Hersfold ^(t/a/c) 16:14, 18 June 2011 (UTC)[reply]

Sorry. I wasn't even aware of this WikiProject. I found it after reading policy. I'd like to make two suggestions though. The first is to add a link in the policy and the second is to include a link in the bot's rationale with a "report here first" message.--v/r - T P 16:52, 18 June 2011 (UTC)[reply]

Sounds reasonable. I'll take a look at the policy and see what can be done; as for the bot, that'll have to go through the operator. Hersfold ^(t/a/c) 01:12, 19 June 2011 (UTC)[reply]

So does this mean we can unblock, or not? Daniel Case (talk) 15:46, 19 June 2011 (UTC)[reply]

I dunno. I can't confirm much (in terms of this being a proxy or not) beyond what I already have, but from what I can see there wouldn't be much harm to it. Hersfold ^(t/a/c) 22:11, 19 June 2011 (UTC)[reply]

I would say safe to unblock. Looks like it was a zombie computer and it has either jumped IPs or had the proxy cured or the ISP kicked the use off until they fix the problem. In any of those cases, we probably can let it edit again. Sailsbystars (talk) 22:26, 19 June 2011 (UTC)[reply]

Unblocking to request a few checks after we set this free. Both are Cisco Operations on :23 and :80, telnet and http respectively. It also looks like it's been dead for a few days. -- DQ (t) (e) 11:36, 20 June 2011 (UTC)[reply]

202.156.13.10

202.156.13.10 · talk · contribs · block · log · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan User claims in request that IP shows as open proxy because it's dynamic, and goes into some detail in their request. Daniel Case (talk) 15:57, 7 July 2011 (UTC)[reply]

Is there a way to search for blocks on a particular range or with a particular prefix? This seems almost identical to the above request and I'm wondering if there are more similar blocks out there. Sailsbystars (talk) 02:54, 8 July 2011 (UTC)[reply]

41.66.138.134

41.66.138.134 · talk · contribs · block · log · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan

Reason: Requested unblock via unblock-en-l.

Interesting results but out of my league to figure this one out. -- DQ (t) (e) 16:42, 9 July 2011 (UTC)[reply]

I'm guessing it's a zombie computer on someone's corporate network. The preponderance of evidence indicates it hasn't been fixed yet. Has been used for spamming since at least May on other websites. The proxy likely jumps ports/is only online some times of day, however, which is why we can't confirm or disconfirm it easily. Sailsbystars (talk) 20:44, 9 July 2011 (UTC)[reply]

69.158.68.37

69.158.68.37 · talk · contribs · block · log · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan

Reason: This user has asked to be unblocked on their talk page. Salvio ^{Let's talk about it!} 17:25, 10 July 2011 (UTC)[reply]

Assuming the request is genuine, the account quoted on the IP talk page user:Io_Katai looks OK, so I've suggested he apply for IPBE. Ronhjones ^(Talk) 18:08, 10 July 2011 (UTC)[reply]

And I've just granted it as a temporary solution, since this user seems to be a valuable contributor. Anyone is free, as usual, to revert my action. Salvio ^{Let's talk about it!} 18:39, 10 July 2011 (UTC)[reply]

Very very unlikely to be a proxy. Unblocked and IPBE removed. -- DQ (t) (e) 23:18, 10 July 2011 (UTC)[reply]

80.254.147.84

80.254.147.84 · talk · contribs · block · log · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan There is a request for unblock at User talk:Allanlewis, who is apparently caught in a proxy block. I have checked as well as I can, and it seems that the proxy is not working, but I would like someone with more experience of these matters to check. Because I know that this project tends to have a backlog and can take a long time to respond, I will give the user IP block exemption for now, but this can be removed if it turns out the proxy is still working. JamesBWatson (talk) 13:21, 13 July 2011 (UTC)[reply]

Looks like it's a gateway belonging to a cisco subsidiary that does web filtering etc for various clients. The listed port is no longer open to me. Looks like it was an open proxy briefly before the company figured out that someone misconfigured a setting. We should probably unblock as since this is a gateway it will affect many users editing from corporate environments. Sailsbystars (talk) 15:14, 14 July 2011 (UTC)[reply]

84.147.220.8

84.147.220.8 · talk · contribs · block · log · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Block was made three years ago. Can we see if things have changed since then? Daniel Case (talk) 18:30, 2 August 2011 (UTC)[reply]

Taking a quick look, I'm not quite sure what this means (I'm too tired to hash it right now), but lets leave it for now. The following came up:

113/tcp closed auth
5060/tcp open sip AVM FRITZ!Box WLAN 7170 29.04.80 (Jan 27 2010)

-- DQ (t) (e) 02:34, 3 August 2011 (UTC)[reply]

Seems down right now, not to concerned with port 5060, but recheck down the road would be good. -- DQ (t) (e) 13:50, 5 August 2011 (UTC)[reply]

98.142.208.62

98.142.216.62 · talk · contribs · block · log · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan 98.142.208.0/20 · contribs · block · log · stalk · Robtex · whois · Google

Reason: A range was blocked of which my computer is a part. My IP (98.142.208.62) is my personal server, used only by myself. There has never been an open proxy on this IP. I have never had an association with any other IP in the 98.142.208.0/20 range. --Revaaron (talk) 16:33, 8 August 2011 (UTC)[reply]