This page is an archive. Do not edit the contents of this page. Please direct any additional comments to the current main page. |
– This proxy check request is closed and will soon be archived by a bot.
open port 8080 2016-05-27
Reason: suspicious edits
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Has been blocked once before on port 30364. 71.237.141.40 ( talk) 19:32, 28 May 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. 71.237.141.40 ( talk) 03:03, 29 May 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Open on port 8080, blocked in March by ProcseeBot
Reason: Suspicious edits. Sro23 ( talk) 07:35, 4 June 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
port 8080 2016-06-08
Reason: Suspicious edits
– This proxy check request is closed and will soon be archived by a bot.
blocked once before 2016-06-11
Reason: Suspicious edits
– This proxy check request is closed and will soon be archived by a bot.
many open ports in the 8000 range 2016-06-12
Reason: Suspicious edits
– This proxy check request is closed and will soon be archived by a bot.
mikrotik router open port 80 2016-06-12
Reason: Suspicious edits
– This proxy check request is closed and will soon be archived by a bot.
2016-06-17
pot 8080 blocked before
Reason: Suspicious edits
– This proxy check request is closed and will soon be archived by a bot.
2016-06-17
Reason: Suspicious edits
– This proxy check request is closed and will soon be archived by a bot.
port 8080 and 3128 open, among others 2016-06-17
Reason: Suspicious edits
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits/signs of sockpupetry. Most of these ips above were mentioned on here and the last one was confirmed here. The proxies seem stale. However, it doesn't mean that they are not being abused by the long-term abuser, since his status is still active. 46.221.217.82 ( talk) 16:54, 17 June 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Also, the same ip was reported on Wikipedia:Sockpuppet investigations/Tirgil34. 46.221.217.82 ( talk) 17:10, 17 June 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Proxy socking.- Mr X 15:36, 19 June 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Socking via Amazon AWS.- Mr X 15:39, 19 June 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits, likely proxy. Also, similar edits and fields of interest with a banned sockmaster. See: WP:Tirgil34. 46.221.224.69 ( talk) 15:55, 19 June 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: suspicious edits & blocked by ProcseeBot in November Sro23 ( talk) 14:42, 24 June 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. IP is registered to "Tophost hosting servers", geo-locating to Italy, and is based from this proxy hosting service/website. 172.56.42.70 ( talk) 22:25, 25 June 2016 (UTC)
{{
webhostblock}}
and block
2001:4B78:1001:0:0:0:0:401 (
talk ·
contribs ·
WHOIS) as {{
blocked proxy}}
, since the traffic to
this web-proxy exits via that IP. Regards—
UY Scuti
Talk 16:04, 8 July 2016 (UTC)– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open proxy at anonymoX.net. 172.56.42.70 ( talk) 22:44, 25 June 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open proxy at anonymoX.net. 172.56.42.70 ( talk) 22:44, 25 June 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. IPv4 proxy IP from proxfree.com. 172.56.42.5 ( talk) 22:33, 30 June 2016 (UTC)
{{
webhostblock}}
. Regards—
UY Scuti
Talk 16:48, 8 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 3128. 172.56.42.5 ( talk) 22:50, 30 June 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open proxy here. 172.56.42.5 ( talk) 22:56, 30 June 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 8080. 172.56.42.5 ( talk) 23:48, 30 June 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits
– This proxy check request is closed and will soon be archived by a bot.
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 1080. More details can be found here. 172.56.42.233 ( talk) 20:21, 9 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 1080. More details can be found here. 172.56.42.233 ( talk) 20:30, 9 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 8080. 172.56.42.221 ( talk) 21:45, 9 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open proxy. The following IP seems to be in a wide variety of open proxies with the IP range of 188.165.0.0/16 ( talk · contribs · WHOIS) per WHOIS. Also, this IPv6 address which is currently blocked, 2001:41d0:2:905e::1 ( talk · contribs · WHOIS) exits through the IPv4 address above. 172.56.42.221 ( talk) 22:11, 9 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Blocked by DoRD. The editor who uses the pseudonym " JamesBWatson" ( talk) 12:52, 26 July 2016 (UTC)
Reason: Suspicious edits. Current open proxy. Has been recently used to evade a block. 172.58.35.162 ( talk) 22:33, 9 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 3128. 172.58.41.207 ( talk) 03:39, 11 July 2016 (UTC)
UPDATE: Apparently, it is registered to a school in Indiana, per the school template on the IP's talkpage. The IP registration may have recently changed... 172.58.41.207 ( talk) 03:43, 11 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 8080. 172.58.41.207 ( talk) 03:41, 11 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 3128. 172.58.41.207 ( talk) 03:44, 11 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 8080. 172.58.41.207 ( talk) 03:45, 11 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 80. 172.58.41.207 ( talk) 03:47, 11 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 8080. 172.58.41.207 ( talk) 03:48, 11 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 10200. 172.58.41.207 ( talk) 03:49, 11 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 10200. 172.58.41.207 ( talk) 03:50, 11 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 10200. 172.58.41.207 ( talk) 03:52, 11 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 60088. 172.58.41.207 ( talk) 03:53, 11 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 1080. 172.58.41.207 ( talk) 03:55, 11 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 9050. 172.58.41.207 ( talk) 03:57, 11 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 60088. 172.58.41.207 ( talk) 04:04, 11 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 60088. 172.58.41.207 ( talk) 04:05, 11 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 10200. 172.58.41.207 ( talk) 04:07, 11 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 8080. 2607:FB90:8089:750F:0:18:D040:9101 ( talk) 02:25, 16 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Unicyclon requested unblock. Reason given for IP address: {{ webhostblock}}. עוד מישהו Od Mishehu 11:43, 17 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: suspicious edits Sro23 ( talk) 18:22, 23 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. 2607:FB90:80AE:5088:0:31:E487:1301 ( talk) 22:02, 24 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits on ja.wikipedia.org.-- HotKorokke ( talk) 22:42, 24 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Belongs to Rackspace Cloud Servers in San Antonio, Texas. Also offered by proxy hosting site known as browserling.com. 2607:FB90:80AE:5088:0:31:E487:1301 ( talk) 00:50, 25 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Recent disruptive edits and this IP has been blocked as a proxy twice before - see log. Geraldo Perez ( talk) 13:42, 25 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. 2607:FB90:4A3B:11E7:0:4B:E2D7:1501 ( talk) 07:18, 28 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 1080. More details can be found here. 172.58.24.218 ( talk) 00:44, 31 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 1080. More details can be found here. 172.58.24.218 ( talk) 00:47, 31 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 1080. More details can be found here. 172.58.24.218 ( talk) 00:50, 31 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: ru-02.tunnello.com Tunnello open proxy. See http://31.192.104.216:3129/, https://31.192.104.216/. -- Antigng ( talk) 01:36, 31 July 2016 (UTC)
The official website says there are Belgian proxies, but I can't find any of them. -- Antigng ( talk) 07:50, 31 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open proxy via web hosting system Tunnello.com. Open on port 3129. 172.58.40.81 ( talk) 03:43, 31 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open at port 1080. More details can be found here. 172.56.42.174 ( talk) 04:42, 31 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open at port 1080. More details can be found here. 172.56.42.174 ( talk) 04:43, 31 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open at port 10200. More details can be found here. 172.56.42.174 ( talk) 04:44, 31 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open at port 1080. More details can be found here. 172.56.42.174 ( talk) 04:46, 31 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open at port 1080. More details can be found here. 172.56.42.174 ( talk) 04:47, 31 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open at port 1080. More details can be found here. 172.56.42.174 ( talk) 04:48, 31 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open on port 1080. More details can be found here. 172.58.41.237 ( talk) 20:05, 31 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Mobile phone app web-hosting site. This seems to be a very wide IP range, but all may be of the same hosting network per WHOIS. Some of the proxies that I have found to be open are all on port 1080. Some of them include:
There is probably a better hidden CIDR sub-mask that I'm just not seeing...
172.56.42.18 ( talk) 05:13, 2 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: IP range is almost at the end of it's current web-host-block. The IP range is still open. 172.58.41.186 ( talk) 00:04, 4 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: IP range is currently open. Has been blocked in the past. 172.58.41.186 ( talk) 00:04, 4 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open on port 1080. More details can be found here. 172.58.40.246 ( talk) 03:51, 4 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open on port 1080. More details can be found here. 172.58.40.246 ( talk) 03:51, 4 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open on port 1080. More details can be found here. 172.58.40.246 ( talk) 03:51, 4 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open on port 1080. More details can be found here. 172.58.40.246 ( talk) 03:51, 4 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open on port 1080. Runs through the same traffic as currently blocked proxy: 93.183.85.208 ( talk · contribs · WHOIS). 172.58.40.246 ( talk) 03:51, 4 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open on port 10200. More details can be found here. 172.58.40.246 ( talk) 03:51, 4 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open on port 1080. Runs through the same traffic as currently blocked proxy: 78.135.114.76 ( talk · contribs · WHOIS). See also the very first block entry for 78.135.114.76 ( talk · contribs · WHOIS) blocked by ProcseeBot. 172.58.40.246 ( talk) 04:13, 4 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Block for this IP range is about to end, and it is still currently open through VPN serive "SaferVPN". 208.54.5.206 ( talk) 20:56, 5 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Many edits that are obvious vandalism, even more edits that add information to articles without citation. Going to user's IP address redirects to Google. Running WHOIS on user's IP shows a virtual private server provider which is likely being used as a proxy.
Wave1453 ( talk) 18:31, 7 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits from 192.95.39.118 ( talk · contribs · WHOIS) & 192.95.39.46 ( talk · contribs · WHOIS). WHOIS shows that this is the range containing the open proxy(ies). Also is used by proxy web-hosting website known as "KProxy.com". 172.56.7.10 ( talk) 13:44, 10 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open proxy with running traffic through already currently blocked proxy 109.202.15.100 ( talk · contribs · WHOIS). 172.56.7.10 ( talk) 13:53, 10 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: This IP range is still currently open through dedicated OVH servers; current block is about to expire. 172.58.40.103 ( talk) 03:02, 12 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: This IP range is still currently open through dedicated OVH servers. Has been blocked twice in the past. 172.58.40.103 ( talk) 03:05, 12 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open IP range through web-host cloud service through "KProxy.com". 172.56.42.156 ( talk) 03:31, 12 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: OVH dedicated range through web-hosting proxy service "KProxy.com". 172.58.41.1 ( talk) 18:40, 12 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: OVH dedicated range through web-hosting proxy service "KProxy.com". 208.54.5.147 ( talk) 21:54, 12 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Apparently involved in
Vodkapoise LTA socking, reported by tools as confirmed proxy
[1].
Brianhe (
talk) 15:57, 14 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Canadian server for Boleh VPN ( https://www.bolehvpn.net/) Ronhjones (Talk) 19:52, 14 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Belongs to Rackspace Cloud Servers in San Antonio, Texas. Also offered by proxy hosting site known as browserling.com. Please see this link. 172.56.38.211 ( talk) 04:58, 15 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: IP was recently blocked as an open proxy. Current blocking period has almost expired. Registered to [Cohula.ru] and open on port 80. 172.56.38.211 ( talk) 04:58, 15 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Dedicated OVH open IP proxy range. Has been blocked in the past. 172.56.38.211 ( talk) 04:58, 15 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Dedicated OVH open IP proxy range. Has been blocked in the past. 172.56.38.211 ( talk) 04:58, 15 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Dedicated OVH open IP proxy range. Has been blocked in the past. 172.56.38.211 ( talk) 04:58, 15 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Dedicated OVH open IP proxy range. 172.56.38.211 ( talk) 04:58, 15 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits at 45.56.87.119 ( talk · contribs · WHOIS). The following IP with the given IP range locates it's ISP to Linode Cloud Hosting Services, which is a virtual private network. Please see this link. 172.56.38.228 ( talk) 01:39, 16 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
– This proxy check request is closed and will soon be archived by a bot.
Reason: IP traffic through Zenmate VPN service. The IP is within the same network with the following IP range: 193.182.144.0/24 ( talk · contribs · WHOIS). Please see this link. 193.182.144.73 ( talk) 21:31, 17 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: IP traffic through Zenmate VPN service. The IP is within the same network with the following IP range: 178.255.42.0/24 ( talk · contribs · WHOIS). Please see this link. 178.255.42.234 ( talk) 21:41, 17 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: IP traffic through Zenmate VPN service. These IP's are within the same network with the following IP range: 31.192.111.0/24 ( talk · contribs · WHOIS). Please see this link. 31.192.111.201 ( talk) 21:45, 17 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: IP traffic through Zenmate VPN service. The IP is within the same network with the following IP range: 103.43.72.0/22 ( talk · contribs · WHOIS). Please see this link. 103.43.75.100 ( talk) 22:08, 17 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Both IP's contain traffic through Zenmate VPN service, though these two IP's seem to be the only ones that are programmed within the server itself (no IP range detected here)... 185.9.19.66 ( talk) 22:18, 17 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open proxy. Suspicious edits. Has been blocked in the past. 73.96.115.45 ( talk) 05:06, 23 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open proxy on port 9987. Suspicious edits. 73.96.115.45 ( talk) 05:06, 23 August 2016 (UTC)
reporting IPs with no suspicious editing patterns makes things slow and is overwhelming to proxy checkers. It is quite hard to clear the current high backlog. There are a LOT of open proxies that haven't edited Wikipedia. It is also counter productive, should we choose to check and block them all individually. To ease things a bit, I'd suggest you to henceforth report IPs that only have suspicious editing patterns. Please also consider not reporting IP ranges unless you see a pattern of editing.Regards— UY Scuti Talk 13:19, 24 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Don't know much about open proxy's saw this when I noticed that a user was evading a block. This says it is a confirmed proxy server. -- GB fan 20:13, 23 August 2016 (UTC)
{{
webhostblock}}
. Regards—
UY Scuti
Talk 13:15, 24 August 2016 (UTC)– This proxy check request is closed and will soon be archived by a bot.
Reason: Open proxy; VERY active and being used to evade block(s). Web proxy is from this service. A VERY long block duration is needed here. Regards. 208.54.5.133 ( talk) 18:49, 26 August 2016 (UTC)
A user has requested a proxy check. A proxy checker will shortly look into the case.
Reason: http://whatismyipaddress.com/ip/2604:1380:1000:6e00::1 shows "Confirmed Proxy Server" Ronhjones (Talk) 22:40, 30 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Open proxy at port 8080. -- Antigng ( talk) 10:11, 1 September 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits, is blacklisted by a number of open proxy detection/spammer detection services such as Barracuda Networks. Brianhe ( talk) 04:59, 2 September 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open on port 80, currently editing from the proxy just for reporting here, please see this link. 37.48.86.212 ( talk) 01:50, 9 September 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Registered to CloudFlare, Inc. Web-hosting services. Open proxy. 37.48.86.212 ( talk) 01:50, 9 September 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: ProcseeBot ( talk · contribs) has previously blocked this IP twice; still open on port 8080. 37.48.86.212 ( talk) 02:12, 9 September 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: ProcseeBot ( talk · contribs) has previously blocked this IP; still open on port 1080. 37.48.86.212 ( talk) 04:06, 9 September 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open proxy, currently using to report the proxy, this link confirms the IPV6 /32 range. 2001:1608:10:135:0:0:E3D8:F0A8 ( talk) 23:14, 12 September 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: IPV4 traffic of the IPV6 report made above. this link confirms the IPV4 /19 range. 2001:1608:10:135:0:0:E3D8:F0A8 ( talk) 23:14, 12 September 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open proxy through 0xproxy. 108.161.136.29 ( talk) 23:58, 12 September 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open proxy through europroxy.pw and 8proxy.space. 172.58.40.148 ( talk) 00:40, 13 September 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open proxy server at this web proxy hosting site. Mobile web-browser hosting. 2607:FB90:A62C:37CC:0:20:D6D8:B101 ( talk) 02:37, 15 September 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 1024. 172.56.38.131 ( talk) 04:12, 16 September 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 1024. 172.56.38.53 ( talk) 04:18, 16 September 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. 172.56.38.53 ( talk) 04:18, 16 September 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Lord Sjones23 ( talk - contributions) 05:14, 16 September 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. 73.96.115.3 ( talk) 00:02, 17 September 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
UNBLOCK: IP is no longer an open proxy, in fact, I don't even think it ever was an open proxy based on it's WHOIS credentials... 73.96.114.205 ( talk) 23:01, 24 September 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Range appears to be used by HexaTech VPN. Please investigate this claim! Thank you. 199.212.86.23 ( talk) 22:26, 3 October 2016 (UTC) Reason: Suspicious edits
Individual IPs can be blocked as necessary. The range also has a lot of legitimate edits and I'm not seeing the need to implement a block at this range despite the range being allocated to a webhost provider. Regards— UY Scuti Talk 17:47, 29 October 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Confirmed open proxy. Please see this link. 2601:1C0:4401:F360:E136:8F9E:9ACF:27BB ( talk) 02:20, 19 October 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Confirmed open proxy. Please see this link. 2601:1C0:4401:F360:E136:8F9E:9ACF:27BB ( talk) 02:20, 19 October 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Confirmed open proxy. Please see this link. 2601:1C0:4401:F360:E136:8F9E:9ACF:27BB ( talk) 02:20, 19 October 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Registered to SurfEasy Inc. I put the range here just in case if the patrolling admin decides to implement the rangeblock, per the WHOIS credentials. 2601:1C0:4401:F360:E136:8F9E:9ACF:27BB ( talk) 18:31, 22 October 2016 (UTC)
{{
blockedproxy}}
. Regards—
UY Scuti
Talk 14:43, 23 October 2016 (UTC)– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Registered to SurfEasy Inc. I put the range here just in case if the patrolling admin decides to implement the rangeblock, per the WHOIS credentials. 2601:1C0:4401:F360:E136:8F9E:9ACF:27BB ( talk) 18:31, 22 October 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. The IP range listed above has already been blocked once for two years, by administrator Elockid. I put the range here just in case if the patrolling admin decides to implement the rangeblock, per the WHOIS credentials. 2601:1C0:4401:F360:E136:8F9E:9ACF:27BB ( talk) 18:31, 22 October 2016 (UTC)
{{
webhostblock}}
. Regards—
UY Scuti
Talk 18:05, 29 October 2016 (UTC)– This proxy check request is closed and will soon be archived by a bot.
Reason: Open proxy IP range, highly used, previous 2 year block by Elockid has now expired. 2601:1C0:4401:F360:E136:8F9E:9ACF:27BB ( talk) 23:23, 22 October 2016 (UTC)
{{
webhostblock}}
—
UY Scuti
Talk 18:22, 29 October 2016 (UTC)– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Registered to Donhost webhosting services. I put the range here just in case if the patrolling admin decides to implement the rangeblock, per the WHOIS credentials. 2601:1C0:4401:F360:4057:B87:4A96:758B ( talk) 23:00, 23 October 2016 (UTC)
{{
webhostblock}}
. Regards —
UY Scuti
Talk 20:02, 29 October 2016 (UTC)– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Registered to OneAsiaHost webhosting services. I put the range here just in case if the patrolling admin decides to implement the rangeblock, per the WHOIS credentials. 2601:1C0:4401:F360:4057:B87:4A96:758B ( talk) 00:56, 27 October 2016 (UTC)
{{
webhostblock}}
. Regards —
UY Scuti
Talk 20:34, 29 October 2016 (UTC)– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Registered to BelCloud Hosting Cooperation webhosting services. I put the range here just in case if the patrolling admin decides to implement the rangeblock, per the WHOIS credentials. 2601:1C0:4401:F360:4057:B87:4A96:758B ( talk) 03:49, 28 October 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Likely a sock of a recently blocked or topic banned user.- Mr X 04:24, 7 November 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Registered to Power Up Hosting, Inc. Yinf ( talk) 22:55, 12 November 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits (spamming Binary options) & WHOIS shows this is a Korean cloud hosting service known as SoftLayer. - Brianhe ( talk) 00:41, 15 November 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Registered to SurfEasy VPN, which is a webhost service. I put the range here just in case if the patrolling admin decides to implement the rangeblock, per the WHOIS credentials. 2601:1C0:2:3207:F9C4:CC2A:EB:3760 ( talk) 00:26, 16 November 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: sockpuppetry. Please see Wikipedia:Sockpuppet investigations/Internetwikier. Ivanvector ( Talk/ Edits) 21:28, 19 November 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Appears to be registered to this dedicated server. The IP range appears to be 212.7.221.0/24 ( block range · block log ( global) · WHOIS (partial)). 2601:1C0:109:2557:11F8:BEF8:160B:24CC ( talk) 06:12, 25 November 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: whatismyipaddress.com notes that it is a confirmed proxy server, while I know their word isn't gospel, and this doesn't mean that it's an open proxy, I'm curious if it is. An IP-hopping user from India appears to be using it to perpetuate an edit war, as can be seen here throughout November 2016. Thanks, Cyphoidbomb ( talk) 00:56, 27 November 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Registered to Power Up Hosting. Included the range, too. 2607:FB90:A51A:3F75:0:48:261E:FB01 ( talk) 17:18, 29 November 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: clear sockpuppetry by a user who nearly always geolocates to Toronto, Canada. This IP belongs to Lowe's and geolocates to North Carolina. Ivanvector ( Talk/ Edits) 17:58, 30 November 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Many disruptive edits from "CHINANET" IP addresses, ProceeBot often blocks IP's from this ISP. Well for example, 115.203.95.239 ( talk · contribs · WHOIS) which was just blocked minutes ago... Open on ports 22 and 443. 2601:1C0:102:B7:1511:5911:F6C6:FF50 ( talk) 06:48, 3 December 2016 (UTC)
A user has requested a proxy check. A proxy checker will shortly look into the case.
Reason:unblock request. this ip is range is blocked from long time and now must unblock. — Preceding unsigned comment added by John CS ( talk • contribs)
– This proxy check request is closed and will soon be archived by a bot.
Geolocate data says this ip is in Ho Chi Min City and is a suspected network sharing device. Beeblebrox ( talk) 23:32, 6 December 2016 (UTC) Reason: Suspicious edits
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Registered to "Blue Coat Systems, Inc". Webhost service. 2601:1C0:10D:8D92:6177:2722:C0EF:15C3 ( talk) 01:06, 7 December 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Check the edit filter log entries for this IP for their most recent edits. Webhosting cloud service "Avast". 73.96.115.2 ( talk) 01:54, 7 December 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Registered to MegaProxy.com. Highly visible proxy server. The /21 range specified above has been previously blocked before. 2601:1C0:10D:5E68:107A:41A1:58F4:7F73 ( talk) 05:40, 8 December 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits - Mr X 16:41, 8 December 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious rDNS: service.brought.to.you.by.uk7.org – 🐈? ( talk) 20:28, 8 December 2016 (UTC)
{{proxycheckstatus}close}}
Reason: Suspicious edits. Another "CHINANET" open proxy, see report for 116.228.82.194 above, which was blocked by Ponyo. 2601:1C0:104:51C4:915F:9EAD:1324:BC92 ( talk) 23:41, 8 December 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious, disruptive edits. Possibly related to this banned sockpuppet. Cathexis1349 ( talk) 09:30, 9 December 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious, disruptive edits. Possibly related to this banned sockpuppet. Cathexis1349 ( talk) 09:30, 9 December 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Highly visible proxy server. Open on port 8080. 87.244.181.185 ( talk) 01:03, 12 December 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Highly visible proxy server. Open on port 3128. 202.106.16.36 ( talk) 01:09, 12 December 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
– This proxy check request is closed and will soon be archived by a bot.
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Registered to GoDaddy. Often used by the LTA sandbox vandal. 2601:1C0:104:9A47:2C4F:1095:CDC4:24CD ( talk) 23:52, 15 December 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: I want you to take note of that whois. "Avast Software Servers". Now, we can note that some of these IPs seem to all have odd, vandal behavior. However, Avast, an antivirus company, seems like an odd AS for that behavior. After doing some research, I quickly found out Avast hosts a VPN! And guess what: one of the locations they list is Istanbul, which is of course, in Turkey. I didn't go looking for the other ranges they might have because I didn't know if things like this would get blocked, but I thought I might as well try. – 🐈? ( talk) (ping me!) 02:33, 18 December 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock.
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Registered here. 2601:1C0:10C:CF1C:9CB2:BA23:5AA4:2F1F ( talk) 04:20, 20 December 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Although whatismyipaddress.com isn't as accurate, but it is claimed to be a confirmed proxy server, if not that it is a shared IP of some sort... 2601:1C0:10D:7EEA:C01A:87C:FE3B:8846 ( talk) 06:32, 20 December 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Registered to HostGator. 2601:1C0:105:DE17:6973:298F:C092:ED0B ( talk) 16:19, 20 December 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. 176.54.93.202 ( talk) 19:32, 27 December 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. "CHINANET" proxy. 2601:1C0:106:17FE:D5AF:4387:5D5F:D086 ( talk) 03:54, 29 December 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. The entire range listed above is also webhosting service as well. 2601:1C0:10D:BF57:953B:1A26:5126:7B57 ( talk) 04:39, 1 January 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. The entire range is registered to Transvision Reseau webhosting services. 172.56.42.77 ( talk) 18:30, 2 January 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits on jawp.-- HotKorokke ( talk) 23:21, 2 January 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. The proxy is from "Romania" and its contributions reminds a sockmaster banned last year. Please check. 46.221.187.97 ( talk) 23:55, 7 January 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Webhost/cloud server. Lots of long-term issues with this IP address, many warnings on their talkpage. 2601:1C0:102:B2A0:6B:B5FF:C620:7D13 ( talk) 23:23, 10 January 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits, Geolocate says "Confirmed proxy server". Beyond My Ken ( talk) 15:18, 18 January 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: A variety of near death threats and abusive behavior at Talk:Chelsea Manning, e.g., [ [2]], started at 130.211.161.255, hopped after block to 159.180.16.2 (which geolocate says is a confirmed proxy), after block complained with dubious innocence on my talk page from 123.30.130.215, which is also marked as a confirmed proxy by geolocate. Request open proxy checks on the latter two addresses. Note the diff I gave has been revdel'd and may end up oversighted. -- joe decker talk 06:05, 19 January 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Harassment related to previous request. Geolocate calls it a confirmed proxy. (I've done a short term block there, but if this is an open proxy you'll want to lengthen it.) -- joe decker talk 15:18, 19 January 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits
– This proxy check request is closed and will soon be archived by a bot.
Reason: I'm on SurfEasy VPN right now and I'm unblocked. -- 162.211.122.69 ( talk) 21:44, 24 January 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: I'm on a SurfEasy VPN right now and unblocked. 146.0.229.30 ( talk) 15:27, 26 January 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Someone from that IP address argues that while it might have been an open proxy back in December, it no longer is. My own rather primitive attempts at verification have yielded mixed results. Someone more experienced than me, possibly Ponyo, may want to take another look. Huon ( talk) 14:43, 27 January 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits Sro23 ( talk) 02:53, 3 September 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Adding promotion for Ismael Ogando (see Wikipedia:Sockpuppet investigations/Cocainaenvenenada) on Ezili Dantor ( [3], [4], [5]; it's a fake source, added only to get Ogando's name into the article), like many socks before them (see page history of article), a sockpuppeteer whose known geolocation is Berlin, Germany, and who is also known to have used proxies before (a proxy they had used was blocked earlier today...). While these IPs geolocate to other continents, in spite of making one of the sockmaster's signature edits. - Tom | Thomas.W talk 23:44, 13 September 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: More Cocainaenvenenada/Ismael Ogando (see above), making Cocainaenvenenada's/Ogando's signature edits on their favourite targets but geolocating to somewhere other than where the sockmaster lives. Another IP used by him today ( Special:Contributions/193.182.144.88) has already been blocked as a proxy by Zzuuzz. - Tom | Thomas.W talk 10:29, 14 September 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Two more Cocainaenvenenada. They both posted on my talk page yesterday, in a thread started by Cocainaenvenenada/Ogando, and might be meat, but are most probably Ogando himself using proxies. - Tom | Thomas.W talk 19:25, 14 September 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: abusive edits coming from European IPs by a user likely located in California. Ivanvector ( Talk/ Edits) 14:06, 16 September 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: IP geolocating to the US but used by obvious sock of Wikipedia:Sockpuppet investigations/Bosnipedian (who geolocates to Sarajevo, Bosnia). - Tom | Thomas.W talk 13:11, 17 September 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: related to the request above for 185.212.170.103, clearly the same user still on a closely related subnet. Ivanvector ( Talk/ Edits) 12:30, 23 September 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Another sock of Wikipedia:Sockpuppet investigations/Cocainaenvenenada. An IP geolocating to California making the sockmasters signature edit on Vusamazulu Credo Mutwa (see page history). Cocainaenvenenada geolocates to Berlin, Germany, but almost a dozen open proxies in other countries were blocked as socks of his not long ago (see a number of previous reports here), so using open proxies is nothing new. - Tom | Thomas.W talk 12:52, 23 September 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: As of 24 Sep 2017, is being used for editwarring and other disruption on several articles. These edits are evidently part of a pattern involving a blocked user using more than one open proxy. IP address itself appears on several lists titled "Free Bangladesh proxy". Guliolopez ( talk) 22:24, 24 September 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: The IP has been used by Wikipedia:Sockpuppet investigations/PavelStaykov (the edits about Bulgarians), but has also been used for childish vandalism, which I've never seen from Staykov, the geolocation (Nairobi, Kenya) also matches neither Staykov nor the other edits, making me believe it's an open proxy, one of many in that country it seems. It's currently blocked for three months, but if it is an open proxy it ought to get a longer block. - Tom | Thomas.W talk 18:57, 27 September 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits.
Reported for edit warring at
Sinn Féin at
WP:AN3. Previously blocked two months by
User:ProcseeBot as an open proxy, port 53281.
EdJohnston (
talk) 03:15, 5 October 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. IP's host is a clear indicator of a VPN. 172.56.39.241 ( talk) 03:20, 1 February 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. IP's host is a clear indicator of a VPN. 172.56.39.241 ( talk) 05:33, 1 February 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Spotted vandalism here, looked them up here and saw the hostname indicates a proxy of some kind. Thanks. Cyphoidbomb ( talk) 19:11, 2 February 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Clearly the LTA flag vandal. They will almost definitely return after the short block... 172.58.41.13 ( talk) 03:33, 3 February 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Blocked proxy; host offline unable to verify if this is IP is still a proxy or concern. Looking for guidance on this IP.— Preceding unsigned comment added by Dane ( talk • contribs)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Possible webhosting service. 172.58.41.122 ( talk) 01:16, 9 February 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Digital Ocean webhosting services. 172.58.40.66 ( talk) 01:43, 10 February 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Long block log of proxy blocks. Most recent edits can be found in the edit filter log. 172.58.41.58 ( talk) 18:40, 10 February 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Webhosting service. The /22 range is the network used. 172.58.40.51 ( talk) 00:50, 14 February 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Registered VPN service. 172.58.40.139 ( talk) 17:54, 14 February 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. 172.58.41.131 ( talk) 18:48, 16 February 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Registered VPN service. 172.58.41.30 ( talk) 03:45, 21 February 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. The /19 range includes the entire webhost service. 172.58.40.170 ( talk) 04:36, 24 February 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 8080. (Note: I was testing the connection of this proxy yesterday and made some edits with it...) 172.58.40.173 ( talk) 23:25, 27 February 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock at User talk:8.37.225.78. עוד מישהו Od Mishehu 06:46, 5 March 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock at User talk:146.247.83.91. עוד מישהו Od Mishehu 06:51, 5 March 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock at User talk:W33dscoper. עוד מישהו Od Mishehu 06:55, 5 March 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Appeal at User talk:Saturnalia0. Block log. Please check whether indeed open proxy.
– This proxy check request is closed and will soon be archived by a bot.
Reason: Part of Opera's SurfEasy VPN. -- 185.80.220.42 ( talk) 03:43, 11 March 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: I sometimes use a VPN (for gaming). This is a new one on NordVPN, and not blocked. Ronhjones (Talk) 20:43, 12 March 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Probably a proxy sock-the same article was targeted a notorious sockmaster before. 46.154.45.179 ( talk) 12:52, 17 March 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Likely a proxy sock-the same article was targeted by a notorious sockmaster before. 46.154.45.179 ( talk) 13:03, 17 March 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Some random troll or other used it to vandalize my talk page, geolocate says it's a confirmed proxy server. Beeblebrox ( talk) 19:54, 22 March 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: IP already blocked for vandalism; WHOIS confirms as proxy server. Thank you, <<< SOME GADGET GEEK >>> ( talk) 01:50, 23 March 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Vandalism and admittance by user it's a proxy server Ronhjones (Talk) 17:14, 25 March 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
User claims in this appeal on UTRS that the IP address is a proxy that requires authorization, not an open proxy. ~ Anachronist ( talk) 00:56, 5 April 2017 (UTC) Reason: Requested unblock.
– This proxy check request is closed and will soon be archived by a bot.
Reason: Vandalism as editing on List of programs broadcast by UNTV. LG-Gunther : Talk 04:28, 5 April 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Noticed a bit of vandalism coming from this IP. I've blocked them for 72 hours, but I noticed that What's My IP Address thinks they might be a proxy and a forum spam source. Granted, I know that this doesn't always mean anything, but my other option was to do nothing, which I didn't think would be helpful. Thanks for looking into this. Cyphoidbomb ( talk) 16:03, 7 April 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious and disruptive edits. The ip is blacklisted at dnsbl.sorbs.net, dul.dnsbl.sorbs.net, 12.apews.org. The ip is static like many proxies and is apparently used by the same person since december. Plus, its edit conduct is resembling a notorious sockmaster involved in ip-socking before. I know this project cannot detect all the proxies any time but it would be nice if someone check this highly dubious ip. 46.221.192.32 ( talk) 12:40, 18 April 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Some recent disruptive editing coming from this IP. Per the IP's block log, ProcseeBot issued a block in 2010 on the basis that the IP was a proxy of some kind. Thought it could use another look. Thanks, Cyphoidbomb ( talk) 15:46, 20 April 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock at User talk:111.88.115.104. עוד מישהו Od Mishehu 09:47, 23 April 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
– This proxy check request is closed and will soon be archived by a bot.
Used Hide.me, then asked google "what's my ip?". -barrelroll.dev ( talk) 23:33, 1 May 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Vandalism from Amazon EC cloud IP
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock.
– This proxy check request is closed and will soon be archived by a bot.
Webhosting service; continued to cause disruption after recent release from block. 2A00:1838:37:C1:0:0:0:6A9D ( talk) 01:44, 16 June 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Webhosting service; continued to cause disruption after recent release from block. Specifically from 198.15.118.143 ( talk · contribs · WHOIS). 2601:1C0:10E:B297:1056:9979:D4E9:73AE ( talk) 01:45, 19 June 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
See [6]. Web check reveals it to be a network sharing device or proxy. GAB gab 21:02, 23 June 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: This IP has been used by a proxy hopping troll on another wiki I am a checkuser on, and it belongs to Amazon. Amazon has hosting services, and if this is an open proxy being used for wiki vandalism, it's only a matter of time until someone uses it to vandalize Wikipedia. PCHS-NJROTC (Messages)Have a blessed day. 21:30, 5 July 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits; long-term prolific sockfarm Wikipedia:Sockpuppet investigations/OfficialPankajPatidar. The IP geolocates to Beijing but here they claim to be in Pakistan, which is consitent with the sockfarm's profile. _ Bri ( talk) 18:55, 7 July 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Managed to edit user:Ronhjones/Proxy, while connected through Nord vpn Canada Ronhjones (Talk) 19:40, 23 July 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits, web check reveals it to be a confirmed proxy server. Probably User:Accopulocrat. GAB gab 00:46, 31 July 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits, "Network sharing device or proxy server... Likely mail server". GAB gab 00:03, 1 August 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits Beyond My Ken ( talk) 14:25, 31 August 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits Beyond My Ken ( talk) 14:25, 31 August 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Disruptive edits over the past year, this says it's a network sharing device or proxy server. -★- PlyrStar93. → Message me. ← 00:09, 23 October 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Began making same pattern of disruptive edits to fast food mascot articles after a prior IP (200.76.184.163) was given a level 4 warning. IP Quality Score lists as a proxy. RA0808 talk contribs 15:20, 24 October 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: ISP is server4you, indicating a web hosting service. Edit warring on some pages. -★- PlyrStar93. → Message me. ← 14:52, 28 October 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Disruptive edits adding deliberate misinformation, IP Quality Score flags as a proxy. RA0808 talk contribs 21:12, 28 October 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits 222.167.166.187 ( talk)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits, vandalism, School block. 222.167.166.187 ( talk)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits, blocked proxy. 222.167.166.187 ( talk)
– This proxy check request is closed and will soon be archived by a bot.
Reason: vandalism from this IP. ISP is Microsoft Corporation and organization is listed as Microsoft Azure, which is a cloud computing platform to deploy applications as well as web hosts. Geolocation shows up as East Coast of US, which is not where Microsoft's corporate office is at, but rather a Microsoft datacenter (Boydton, VA). -★- PlyrStar93. → Message me. ← 19:33, 29 October 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Vandalism, blocked proxy 222.167.166.187 ( talk) 21:06, 30 October 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: 185.17.132.66:53281 is an open proxy which was used for a vandalbot attack on Commons. — Guan aco 08:12, 31 October 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits, appears to be Zscaler proxy ☆ Bri ( talk) 14:41, 1 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. whatismyipaddress.com says that it is a VPN server. Even though the IP address is already blocked, it should be hard-blocked and possibly for a longer duration. 24.51.86.102 ( talk) 18:07, 1 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Recently started editing again within the last few days. Blocked by the proxy bot, still an open proxy. 159.89.10.188 ( talk) 15:54, 2 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Zscaler open proxy. 116.220.7.10 ( talk) 20:43, 3 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. whatismyipaddress.com reports it as a spam source (within the last 30 days, etc.). 82.0.113.79 ( talk) 18:30, 5 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Hurricane Electric open proxy. 176.103.48.38 ( talk) 16:18, 9 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Zscaler open proxy. 122.197.215.184 ( talk) 17:59, 10 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious (promotional) edits; socking; has been identified as Microsoft Azure host. ☆ Bri ( talk) 18:02, 10 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: sockpuppetry, IPs in France, England, and Japan, being used by a banned user located in the United States who has used open proxies for abuse in the past. (NOTE: I combined a few open reports) Ivanvector ( Talk/ Edits) 15:35, 18 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits — Preceding unsigned comment added by 95.153.132.82 ( talk • contribs) 01:28, 17 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: edit war-ish edit summaries. Host name is vds-holanet.timeweb.ru and ISP is TimeWeb Ltd., a Russian web hosting company. -★- PlyrStar93. → Message me. ← 03:07, 19 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Recently blocked as a webhost on meta.wiki, and was once blocked on en.wiki too. This /32 IPv6 range still appears to be a webhosting service. 219.98.8.174 ( talk) 22:40, 19 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Fanciful hoaxing & BLP violations in the style of Jaredgk2008.— Odysseus 147 9 05:34, 21 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
I work for the ISP which owns this netblock and can confirm that this is a range of DHCP addresses handed out to residential customers and has no connection to our colocation facilities. Refer to this discussion if you want to know why I posted this request here. Reason: Incorrectly blocked as colocationwebhost. Opsftw ( talk) 18:38, 27 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: WP:DUCK test matches Wikipedia:Long-term abuse/109.151.65.218, behavior matches that one almost spot on. However, this IP's WHOIS data indicates a US-based IP address, while all of the others indicate UK-based IP addresses. Asking for a proxy check to see if they are using an open proxy to mask their location. IP is already blocked a short time based on behavioral evidence. -- Jayron 32 20:07, 27 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. I'm not sure how to check which port the IP is open on, but whatismyipaddress.com labels it as a "confirmed proxy server".
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits, listed as problem host by Barracuda. ☆ Bri ( talk) 18:38, 28 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: All edits are vandalism/unconstructive. Also some other edits in other wikis: frwiki/ simplewiki are the same type of vandalism. Proxy checker shows as VPN/proxy. Based on behavior, this is the Pikepass vandal at frwiki, who is known to abuse proxies (e.g. previous blocked IP 96.92.203.45 now globally blocked 1 year as open proxy). -★- PlyrStar93. → Message me. ← 04:11, 29 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Dedicated server proxy IP. May need to be rangeblocked as {{
webhostblock}}
.
116.123.126.79 (
talk) 10:05, 29 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. IP address is back to being a proxy once again per whatismyipaddress.com (refer to block log). 203.128.191.50 ( talk) 18:04, 29 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. User has admitted that this IP address is a Tor exit node. 60.36.225.155 ( talk) 13:10, 30 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Hostname is: "hosted-by.seedvps.com" which is registered to
this VPN hosting service. According to the
WHOIS links,
46.166.176.0/21 (
block range ·
block log (
global) ·
WHOIS (partial)) would be the correct range to block if a {{
webhostblock}}
would be performed.
76.109.126.61 (
talk) 05:59, 4 December 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits, address query reports Webhosting cloud service Avast "Network sharing device or proxy server", poss proxy thing ☆ Bri ( talk) 04:48, 5 December 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock.
– This proxy check request is closed and will soon be archived by a bot.
Reason: Recently used by sockpuppeteer; whatismyaddress.com says it's a proxy server. Trivialist ( talk) 21:10, 17 December 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. confirmed proxy server and webhosting service. 180.47.118.156 ( talk) 18:58, 18 December 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits
See a complaint of disruptive editing at WP:Administrators' noticeboard#Editor being bullied. User:Berean Hunter tried checking the IP at one of the IP lookup sites, and that site reports it to be an open proxy. I am unsure whether to trust this verdict. EdJohnston ( talk) 00:34, 21 December 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: See discussion, the final section at WP:ANI. In short, someone created a couple of attack accounts, and when they were blocked, this IP continued the disruption. According to checkuser NinjaRobotPirate, the accounts are using proxies, so I suppose it's likely that this one also might be. It was previously blocked by Procseebot, but that block expired without being renewed, so I'm not clear if that means that the bot hadn't gotten around to reblocking it yet or if it means that it's not a proxy anymore. I gave it a short block for the disruption, but please lengthen the block if it's a proxy. Nyttend ( talk) 14:05, 23 December 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
A few minutes after I made the block referenced in the previous section, I got this friendly notice from an IP with no previous edits. This is the first logged action I've made in several days, aside from unprotecting a page (can't imagine anyone objecting to that in such a manner), so I strongly suspect that it's related. Seeing that 110.77.181.148 is Thai, and this one's Chinese, I strongly suspect that they're both open proxies. Nyttend ( talk) 14:24, 23 December 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. IP has been blocked twice in the past as an open proxy. 14.190.44.204 ( talk) 17:47, 28 December 2017 (UTC)
This page is an archive. Do not edit the contents of this page. Please direct any additional comments to the current main page. |
– This proxy check request is closed and will soon be archived by a bot.
open port 8080 2016-05-27
Reason: suspicious edits
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Has been blocked once before on port 30364. 71.237.141.40 ( talk) 19:32, 28 May 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. 71.237.141.40 ( talk) 03:03, 29 May 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Open on port 8080, blocked in March by ProcseeBot
Reason: Suspicious edits. Sro23 ( talk) 07:35, 4 June 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
port 8080 2016-06-08
Reason: Suspicious edits
– This proxy check request is closed and will soon be archived by a bot.
blocked once before 2016-06-11
Reason: Suspicious edits
– This proxy check request is closed and will soon be archived by a bot.
many open ports in the 8000 range 2016-06-12
Reason: Suspicious edits
– This proxy check request is closed and will soon be archived by a bot.
mikrotik router open port 80 2016-06-12
Reason: Suspicious edits
– This proxy check request is closed and will soon be archived by a bot.
2016-06-17
pot 8080 blocked before
Reason: Suspicious edits
– This proxy check request is closed and will soon be archived by a bot.
2016-06-17
Reason: Suspicious edits
– This proxy check request is closed and will soon be archived by a bot.
port 8080 and 3128 open, among others 2016-06-17
Reason: Suspicious edits
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits/signs of sockpupetry. Most of these ips above were mentioned on here and the last one was confirmed here. The proxies seem stale. However, it doesn't mean that they are not being abused by the long-term abuser, since his status is still active. 46.221.217.82 ( talk) 16:54, 17 June 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Also, the same ip was reported on Wikipedia:Sockpuppet investigations/Tirgil34. 46.221.217.82 ( talk) 17:10, 17 June 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Proxy socking.- Mr X 15:36, 19 June 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Socking via Amazon AWS.- Mr X 15:39, 19 June 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits, likely proxy. Also, similar edits and fields of interest with a banned sockmaster. See: WP:Tirgil34. 46.221.224.69 ( talk) 15:55, 19 June 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: suspicious edits & blocked by ProcseeBot in November Sro23 ( talk) 14:42, 24 June 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. IP is registered to "Tophost hosting servers", geo-locating to Italy, and is based from this proxy hosting service/website. 172.56.42.70 ( talk) 22:25, 25 June 2016 (UTC)
{{
webhostblock}}
and block
2001:4B78:1001:0:0:0:0:401 (
talk ·
contribs ·
WHOIS) as {{
blocked proxy}}
, since the traffic to
this web-proxy exits via that IP. Regards—
UY Scuti
Talk 16:04, 8 July 2016 (UTC)– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open proxy at anonymoX.net. 172.56.42.70 ( talk) 22:44, 25 June 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open proxy at anonymoX.net. 172.56.42.70 ( talk) 22:44, 25 June 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. IPv4 proxy IP from proxfree.com. 172.56.42.5 ( talk) 22:33, 30 June 2016 (UTC)
{{
webhostblock}}
. Regards—
UY Scuti
Talk 16:48, 8 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 3128. 172.56.42.5 ( talk) 22:50, 30 June 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open proxy here. 172.56.42.5 ( talk) 22:56, 30 June 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 8080. 172.56.42.5 ( talk) 23:48, 30 June 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits
– This proxy check request is closed and will soon be archived by a bot.
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 1080. More details can be found here. 172.56.42.233 ( talk) 20:21, 9 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 1080. More details can be found here. 172.56.42.233 ( talk) 20:30, 9 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 8080. 172.56.42.221 ( talk) 21:45, 9 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open proxy. The following IP seems to be in a wide variety of open proxies with the IP range of 188.165.0.0/16 ( talk · contribs · WHOIS) per WHOIS. Also, this IPv6 address which is currently blocked, 2001:41d0:2:905e::1 ( talk · contribs · WHOIS) exits through the IPv4 address above. 172.56.42.221 ( talk) 22:11, 9 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Blocked by DoRD. The editor who uses the pseudonym " JamesBWatson" ( talk) 12:52, 26 July 2016 (UTC)
Reason: Suspicious edits. Current open proxy. Has been recently used to evade a block. 172.58.35.162 ( talk) 22:33, 9 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 3128. 172.58.41.207 ( talk) 03:39, 11 July 2016 (UTC)
UPDATE: Apparently, it is registered to a school in Indiana, per the school template on the IP's talkpage. The IP registration may have recently changed... 172.58.41.207 ( talk) 03:43, 11 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 8080. 172.58.41.207 ( talk) 03:41, 11 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 3128. 172.58.41.207 ( talk) 03:44, 11 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 8080. 172.58.41.207 ( talk) 03:45, 11 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 80. 172.58.41.207 ( talk) 03:47, 11 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 8080. 172.58.41.207 ( talk) 03:48, 11 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 10200. 172.58.41.207 ( talk) 03:49, 11 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 10200. 172.58.41.207 ( talk) 03:50, 11 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 10200. 172.58.41.207 ( talk) 03:52, 11 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 60088. 172.58.41.207 ( talk) 03:53, 11 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 1080. 172.58.41.207 ( talk) 03:55, 11 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 9050. 172.58.41.207 ( talk) 03:57, 11 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 60088. 172.58.41.207 ( talk) 04:04, 11 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 60088. 172.58.41.207 ( talk) 04:05, 11 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 10200. 172.58.41.207 ( talk) 04:07, 11 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 8080. 2607:FB90:8089:750F:0:18:D040:9101 ( talk) 02:25, 16 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Unicyclon requested unblock. Reason given for IP address: {{ webhostblock}}. עוד מישהו Od Mishehu 11:43, 17 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: suspicious edits Sro23 ( talk) 18:22, 23 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. 2607:FB90:80AE:5088:0:31:E487:1301 ( talk) 22:02, 24 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits on ja.wikipedia.org.-- HotKorokke ( talk) 22:42, 24 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Belongs to Rackspace Cloud Servers in San Antonio, Texas. Also offered by proxy hosting site known as browserling.com. 2607:FB90:80AE:5088:0:31:E487:1301 ( talk) 00:50, 25 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Recent disruptive edits and this IP has been blocked as a proxy twice before - see log. Geraldo Perez ( talk) 13:42, 25 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. 2607:FB90:4A3B:11E7:0:4B:E2D7:1501 ( talk) 07:18, 28 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 1080. More details can be found here. 172.58.24.218 ( talk) 00:44, 31 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 1080. More details can be found here. 172.58.24.218 ( talk) 00:47, 31 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 1080. More details can be found here. 172.58.24.218 ( talk) 00:50, 31 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: ru-02.tunnello.com Tunnello open proxy. See http://31.192.104.216:3129/, https://31.192.104.216/. -- Antigng ( talk) 01:36, 31 July 2016 (UTC)
The official website says there are Belgian proxies, but I can't find any of them. -- Antigng ( talk) 07:50, 31 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open proxy via web hosting system Tunnello.com. Open on port 3129. 172.58.40.81 ( talk) 03:43, 31 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open at port 1080. More details can be found here. 172.56.42.174 ( talk) 04:42, 31 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open at port 1080. More details can be found here. 172.56.42.174 ( talk) 04:43, 31 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open at port 10200. More details can be found here. 172.56.42.174 ( talk) 04:44, 31 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open at port 1080. More details can be found here. 172.56.42.174 ( talk) 04:46, 31 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open at port 1080. More details can be found here. 172.56.42.174 ( talk) 04:47, 31 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open at port 1080. More details can be found here. 172.56.42.174 ( talk) 04:48, 31 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open on port 1080. More details can be found here. 172.58.41.237 ( talk) 20:05, 31 July 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Mobile phone app web-hosting site. This seems to be a very wide IP range, but all may be of the same hosting network per WHOIS. Some of the proxies that I have found to be open are all on port 1080. Some of them include:
There is probably a better hidden CIDR sub-mask that I'm just not seeing...
172.56.42.18 ( talk) 05:13, 2 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: IP range is almost at the end of it's current web-host-block. The IP range is still open. 172.58.41.186 ( talk) 00:04, 4 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: IP range is currently open. Has been blocked in the past. 172.58.41.186 ( talk) 00:04, 4 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open on port 1080. More details can be found here. 172.58.40.246 ( talk) 03:51, 4 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open on port 1080. More details can be found here. 172.58.40.246 ( talk) 03:51, 4 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open on port 1080. More details can be found here. 172.58.40.246 ( talk) 03:51, 4 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open on port 1080. More details can be found here. 172.58.40.246 ( talk) 03:51, 4 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open on port 1080. Runs through the same traffic as currently blocked proxy: 93.183.85.208 ( talk · contribs · WHOIS). 172.58.40.246 ( talk) 03:51, 4 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open on port 10200. More details can be found here. 172.58.40.246 ( talk) 03:51, 4 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open on port 1080. Runs through the same traffic as currently blocked proxy: 78.135.114.76 ( talk · contribs · WHOIS). See also the very first block entry for 78.135.114.76 ( talk · contribs · WHOIS) blocked by ProcseeBot. 172.58.40.246 ( talk) 04:13, 4 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Block for this IP range is about to end, and it is still currently open through VPN serive "SaferVPN". 208.54.5.206 ( talk) 20:56, 5 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Many edits that are obvious vandalism, even more edits that add information to articles without citation. Going to user's IP address redirects to Google. Running WHOIS on user's IP shows a virtual private server provider which is likely being used as a proxy.
Wave1453 ( talk) 18:31, 7 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits from 192.95.39.118 ( talk · contribs · WHOIS) & 192.95.39.46 ( talk · contribs · WHOIS). WHOIS shows that this is the range containing the open proxy(ies). Also is used by proxy web-hosting website known as "KProxy.com". 172.56.7.10 ( talk) 13:44, 10 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open proxy with running traffic through already currently blocked proxy 109.202.15.100 ( talk · contribs · WHOIS). 172.56.7.10 ( talk) 13:53, 10 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: This IP range is still currently open through dedicated OVH servers; current block is about to expire. 172.58.40.103 ( talk) 03:02, 12 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: This IP range is still currently open through dedicated OVH servers. Has been blocked twice in the past. 172.58.40.103 ( talk) 03:05, 12 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open IP range through web-host cloud service through "KProxy.com". 172.56.42.156 ( talk) 03:31, 12 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: OVH dedicated range through web-hosting proxy service "KProxy.com". 172.58.41.1 ( talk) 18:40, 12 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: OVH dedicated range through web-hosting proxy service "KProxy.com". 208.54.5.147 ( talk) 21:54, 12 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Apparently involved in
Vodkapoise LTA socking, reported by tools as confirmed proxy
[1].
Brianhe (
talk) 15:57, 14 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Canadian server for Boleh VPN ( https://www.bolehvpn.net/) Ronhjones (Talk) 19:52, 14 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Belongs to Rackspace Cloud Servers in San Antonio, Texas. Also offered by proxy hosting site known as browserling.com. Please see this link. 172.56.38.211 ( talk) 04:58, 15 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: IP was recently blocked as an open proxy. Current blocking period has almost expired. Registered to [Cohula.ru] and open on port 80. 172.56.38.211 ( talk) 04:58, 15 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Dedicated OVH open IP proxy range. Has been blocked in the past. 172.56.38.211 ( talk) 04:58, 15 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Dedicated OVH open IP proxy range. Has been blocked in the past. 172.56.38.211 ( talk) 04:58, 15 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Dedicated OVH open IP proxy range. Has been blocked in the past. 172.56.38.211 ( talk) 04:58, 15 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Dedicated OVH open IP proxy range. 172.56.38.211 ( talk) 04:58, 15 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits at 45.56.87.119 ( talk · contribs · WHOIS). The following IP with the given IP range locates it's ISP to Linode Cloud Hosting Services, which is a virtual private network. Please see this link. 172.56.38.228 ( talk) 01:39, 16 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
– This proxy check request is closed and will soon be archived by a bot.
Reason: IP traffic through Zenmate VPN service. The IP is within the same network with the following IP range: 193.182.144.0/24 ( talk · contribs · WHOIS). Please see this link. 193.182.144.73 ( talk) 21:31, 17 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: IP traffic through Zenmate VPN service. The IP is within the same network with the following IP range: 178.255.42.0/24 ( talk · contribs · WHOIS). Please see this link. 178.255.42.234 ( talk) 21:41, 17 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: IP traffic through Zenmate VPN service. These IP's are within the same network with the following IP range: 31.192.111.0/24 ( talk · contribs · WHOIS). Please see this link. 31.192.111.201 ( talk) 21:45, 17 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: IP traffic through Zenmate VPN service. The IP is within the same network with the following IP range: 103.43.72.0/22 ( talk · contribs · WHOIS). Please see this link. 103.43.75.100 ( talk) 22:08, 17 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Both IP's contain traffic through Zenmate VPN service, though these two IP's seem to be the only ones that are programmed within the server itself (no IP range detected here)... 185.9.19.66 ( talk) 22:18, 17 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open proxy. Suspicious edits. Has been blocked in the past. 73.96.115.45 ( talk) 05:06, 23 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open proxy on port 9987. Suspicious edits. 73.96.115.45 ( talk) 05:06, 23 August 2016 (UTC)
reporting IPs with no suspicious editing patterns makes things slow and is overwhelming to proxy checkers. It is quite hard to clear the current high backlog. There are a LOT of open proxies that haven't edited Wikipedia. It is also counter productive, should we choose to check and block them all individually. To ease things a bit, I'd suggest you to henceforth report IPs that only have suspicious editing patterns. Please also consider not reporting IP ranges unless you see a pattern of editing.Regards— UY Scuti Talk 13:19, 24 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Don't know much about open proxy's saw this when I noticed that a user was evading a block. This says it is a confirmed proxy server. -- GB fan 20:13, 23 August 2016 (UTC)
{{
webhostblock}}
. Regards—
UY Scuti
Talk 13:15, 24 August 2016 (UTC)– This proxy check request is closed and will soon be archived by a bot.
Reason: Open proxy; VERY active and being used to evade block(s). Web proxy is from this service. A VERY long block duration is needed here. Regards. 208.54.5.133 ( talk) 18:49, 26 August 2016 (UTC)
A user has requested a proxy check. A proxy checker will shortly look into the case.
Reason: http://whatismyipaddress.com/ip/2604:1380:1000:6e00::1 shows "Confirmed Proxy Server" Ronhjones (Talk) 22:40, 30 August 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Open proxy at port 8080. -- Antigng ( talk) 10:11, 1 September 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits, is blacklisted by a number of open proxy detection/spammer detection services such as Barracuda Networks. Brianhe ( talk) 04:59, 2 September 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open on port 80, currently editing from the proxy just for reporting here, please see this link. 37.48.86.212 ( talk) 01:50, 9 September 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Registered to CloudFlare, Inc. Web-hosting services. Open proxy. 37.48.86.212 ( talk) 01:50, 9 September 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: ProcseeBot ( talk · contribs) has previously blocked this IP twice; still open on port 8080. 37.48.86.212 ( talk) 02:12, 9 September 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: ProcseeBot ( talk · contribs) has previously blocked this IP; still open on port 1080. 37.48.86.212 ( talk) 04:06, 9 September 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open proxy, currently using to report the proxy, this link confirms the IPV6 /32 range. 2001:1608:10:135:0:0:E3D8:F0A8 ( talk) 23:14, 12 September 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: IPV4 traffic of the IPV6 report made above. this link confirms the IPV4 /19 range. 2001:1608:10:135:0:0:E3D8:F0A8 ( talk) 23:14, 12 September 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open proxy through 0xproxy. 108.161.136.29 ( talk) 23:58, 12 September 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open proxy through europroxy.pw and 8proxy.space. 172.58.40.148 ( talk) 00:40, 13 September 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open proxy server at this web proxy hosting site. Mobile web-browser hosting. 2607:FB90:A62C:37CC:0:20:D6D8:B101 ( talk) 02:37, 15 September 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 1024. 172.56.38.131 ( talk) 04:12, 16 September 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 1024. 172.56.38.53 ( talk) 04:18, 16 September 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. 172.56.38.53 ( talk) 04:18, 16 September 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Lord Sjones23 ( talk - contributions) 05:14, 16 September 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. 73.96.115.3 ( talk) 00:02, 17 September 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
UNBLOCK: IP is no longer an open proxy, in fact, I don't even think it ever was an open proxy based on it's WHOIS credentials... 73.96.114.205 ( talk) 23:01, 24 September 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Range appears to be used by HexaTech VPN. Please investigate this claim! Thank you. 199.212.86.23 ( talk) 22:26, 3 October 2016 (UTC) Reason: Suspicious edits
Individual IPs can be blocked as necessary. The range also has a lot of legitimate edits and I'm not seeing the need to implement a block at this range despite the range being allocated to a webhost provider. Regards— UY Scuti Talk 17:47, 29 October 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Confirmed open proxy. Please see this link. 2601:1C0:4401:F360:E136:8F9E:9ACF:27BB ( talk) 02:20, 19 October 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Confirmed open proxy. Please see this link. 2601:1C0:4401:F360:E136:8F9E:9ACF:27BB ( talk) 02:20, 19 October 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Confirmed open proxy. Please see this link. 2601:1C0:4401:F360:E136:8F9E:9ACF:27BB ( talk) 02:20, 19 October 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Registered to SurfEasy Inc. I put the range here just in case if the patrolling admin decides to implement the rangeblock, per the WHOIS credentials. 2601:1C0:4401:F360:E136:8F9E:9ACF:27BB ( talk) 18:31, 22 October 2016 (UTC)
{{
blockedproxy}}
. Regards—
UY Scuti
Talk 14:43, 23 October 2016 (UTC)– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Registered to SurfEasy Inc. I put the range here just in case if the patrolling admin decides to implement the rangeblock, per the WHOIS credentials. 2601:1C0:4401:F360:E136:8F9E:9ACF:27BB ( talk) 18:31, 22 October 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. The IP range listed above has already been blocked once for two years, by administrator Elockid. I put the range here just in case if the patrolling admin decides to implement the rangeblock, per the WHOIS credentials. 2601:1C0:4401:F360:E136:8F9E:9ACF:27BB ( talk) 18:31, 22 October 2016 (UTC)
{{
webhostblock}}
. Regards—
UY Scuti
Talk 18:05, 29 October 2016 (UTC)– This proxy check request is closed and will soon be archived by a bot.
Reason: Open proxy IP range, highly used, previous 2 year block by Elockid has now expired. 2601:1C0:4401:F360:E136:8F9E:9ACF:27BB ( talk) 23:23, 22 October 2016 (UTC)
{{
webhostblock}}
—
UY Scuti
Talk 18:22, 29 October 2016 (UTC)– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Registered to Donhost webhosting services. I put the range here just in case if the patrolling admin decides to implement the rangeblock, per the WHOIS credentials. 2601:1C0:4401:F360:4057:B87:4A96:758B ( talk) 23:00, 23 October 2016 (UTC)
{{
webhostblock}}
. Regards —
UY Scuti
Talk 20:02, 29 October 2016 (UTC)– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Registered to OneAsiaHost webhosting services. I put the range here just in case if the patrolling admin decides to implement the rangeblock, per the WHOIS credentials. 2601:1C0:4401:F360:4057:B87:4A96:758B ( talk) 00:56, 27 October 2016 (UTC)
{{
webhostblock}}
. Regards —
UY Scuti
Talk 20:34, 29 October 2016 (UTC)– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Registered to BelCloud Hosting Cooperation webhosting services. I put the range here just in case if the patrolling admin decides to implement the rangeblock, per the WHOIS credentials. 2601:1C0:4401:F360:4057:B87:4A96:758B ( talk) 03:49, 28 October 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Likely a sock of a recently blocked or topic banned user.- Mr X 04:24, 7 November 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Registered to Power Up Hosting, Inc. Yinf ( talk) 22:55, 12 November 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits (spamming Binary options) & WHOIS shows this is a Korean cloud hosting service known as SoftLayer. - Brianhe ( talk) 00:41, 15 November 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Registered to SurfEasy VPN, which is a webhost service. I put the range here just in case if the patrolling admin decides to implement the rangeblock, per the WHOIS credentials. 2601:1C0:2:3207:F9C4:CC2A:EB:3760 ( talk) 00:26, 16 November 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: sockpuppetry. Please see Wikipedia:Sockpuppet investigations/Internetwikier. Ivanvector ( Talk/ Edits) 21:28, 19 November 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Appears to be registered to this dedicated server. The IP range appears to be 212.7.221.0/24 ( block range · block log ( global) · WHOIS (partial)). 2601:1C0:109:2557:11F8:BEF8:160B:24CC ( talk) 06:12, 25 November 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: whatismyipaddress.com notes that it is a confirmed proxy server, while I know their word isn't gospel, and this doesn't mean that it's an open proxy, I'm curious if it is. An IP-hopping user from India appears to be using it to perpetuate an edit war, as can be seen here throughout November 2016. Thanks, Cyphoidbomb ( talk) 00:56, 27 November 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Registered to Power Up Hosting. Included the range, too. 2607:FB90:A51A:3F75:0:48:261E:FB01 ( talk) 17:18, 29 November 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: clear sockpuppetry by a user who nearly always geolocates to Toronto, Canada. This IP belongs to Lowe's and geolocates to North Carolina. Ivanvector ( Talk/ Edits) 17:58, 30 November 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Many disruptive edits from "CHINANET" IP addresses, ProceeBot often blocks IP's from this ISP. Well for example, 115.203.95.239 ( talk · contribs · WHOIS) which was just blocked minutes ago... Open on ports 22 and 443. 2601:1C0:102:B7:1511:5911:F6C6:FF50 ( talk) 06:48, 3 December 2016 (UTC)
A user has requested a proxy check. A proxy checker will shortly look into the case.
Reason:unblock request. this ip is range is blocked from long time and now must unblock. — Preceding unsigned comment added by John CS ( talk • contribs)
– This proxy check request is closed and will soon be archived by a bot.
Geolocate data says this ip is in Ho Chi Min City and is a suspected network sharing device. Beeblebrox ( talk) 23:32, 6 December 2016 (UTC) Reason: Suspicious edits
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Registered to "Blue Coat Systems, Inc". Webhost service. 2601:1C0:10D:8D92:6177:2722:C0EF:15C3 ( talk) 01:06, 7 December 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Check the edit filter log entries for this IP for their most recent edits. Webhosting cloud service "Avast". 73.96.115.2 ( talk) 01:54, 7 December 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Registered to MegaProxy.com. Highly visible proxy server. The /21 range specified above has been previously blocked before. 2601:1C0:10D:5E68:107A:41A1:58F4:7F73 ( talk) 05:40, 8 December 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits - Mr X 16:41, 8 December 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious rDNS: service.brought.to.you.by.uk7.org – 🐈? ( talk) 20:28, 8 December 2016 (UTC)
{{proxycheckstatus}close}}
Reason: Suspicious edits. Another "CHINANET" open proxy, see report for 116.228.82.194 above, which was blocked by Ponyo. 2601:1C0:104:51C4:915F:9EAD:1324:BC92 ( talk) 23:41, 8 December 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious, disruptive edits. Possibly related to this banned sockpuppet. Cathexis1349 ( talk) 09:30, 9 December 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious, disruptive edits. Possibly related to this banned sockpuppet. Cathexis1349 ( talk) 09:30, 9 December 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Highly visible proxy server. Open on port 8080. 87.244.181.185 ( talk) 01:03, 12 December 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Highly visible proxy server. Open on port 3128. 202.106.16.36 ( talk) 01:09, 12 December 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
– This proxy check request is closed and will soon be archived by a bot.
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Registered to GoDaddy. Often used by the LTA sandbox vandal. 2601:1C0:104:9A47:2C4F:1095:CDC4:24CD ( talk) 23:52, 15 December 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: I want you to take note of that whois. "Avast Software Servers". Now, we can note that some of these IPs seem to all have odd, vandal behavior. However, Avast, an antivirus company, seems like an odd AS for that behavior. After doing some research, I quickly found out Avast hosts a VPN! And guess what: one of the locations they list is Istanbul, which is of course, in Turkey. I didn't go looking for the other ranges they might have because I didn't know if things like this would get blocked, but I thought I might as well try. – 🐈? ( talk) (ping me!) 02:33, 18 December 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock.
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Registered here. 2601:1C0:10C:CF1C:9CB2:BA23:5AA4:2F1F ( talk) 04:20, 20 December 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Although whatismyipaddress.com isn't as accurate, but it is claimed to be a confirmed proxy server, if not that it is a shared IP of some sort... 2601:1C0:10D:7EEA:C01A:87C:FE3B:8846 ( talk) 06:32, 20 December 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Registered to HostGator. 2601:1C0:105:DE17:6973:298F:C092:ED0B ( talk) 16:19, 20 December 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. 176.54.93.202 ( talk) 19:32, 27 December 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. "CHINANET" proxy. 2601:1C0:106:17FE:D5AF:4387:5D5F:D086 ( talk) 03:54, 29 December 2016 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. The entire range listed above is also webhosting service as well. 2601:1C0:10D:BF57:953B:1A26:5126:7B57 ( talk) 04:39, 1 January 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. The entire range is registered to Transvision Reseau webhosting services. 172.56.42.77 ( talk) 18:30, 2 January 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits on jawp.-- HotKorokke ( talk) 23:21, 2 January 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. The proxy is from "Romania" and its contributions reminds a sockmaster banned last year. Please check. 46.221.187.97 ( talk) 23:55, 7 January 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Webhost/cloud server. Lots of long-term issues with this IP address, many warnings on their talkpage. 2601:1C0:102:B2A0:6B:B5FF:C620:7D13 ( talk) 23:23, 10 January 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits, Geolocate says "Confirmed proxy server". Beyond My Ken ( talk) 15:18, 18 January 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: A variety of near death threats and abusive behavior at Talk:Chelsea Manning, e.g., [ [2]], started at 130.211.161.255, hopped after block to 159.180.16.2 (which geolocate says is a confirmed proxy), after block complained with dubious innocence on my talk page from 123.30.130.215, which is also marked as a confirmed proxy by geolocate. Request open proxy checks on the latter two addresses. Note the diff I gave has been revdel'd and may end up oversighted. -- joe decker talk 06:05, 19 January 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Harassment related to previous request. Geolocate calls it a confirmed proxy. (I've done a short term block there, but if this is an open proxy you'll want to lengthen it.) -- joe decker talk 15:18, 19 January 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits
– This proxy check request is closed and will soon be archived by a bot.
Reason: I'm on SurfEasy VPN right now and I'm unblocked. -- 162.211.122.69 ( talk) 21:44, 24 January 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: I'm on a SurfEasy VPN right now and unblocked. 146.0.229.30 ( talk) 15:27, 26 January 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Someone from that IP address argues that while it might have been an open proxy back in December, it no longer is. My own rather primitive attempts at verification have yielded mixed results. Someone more experienced than me, possibly Ponyo, may want to take another look. Huon ( talk) 14:43, 27 January 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits Sro23 ( talk) 02:53, 3 September 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Adding promotion for Ismael Ogando (see Wikipedia:Sockpuppet investigations/Cocainaenvenenada) on Ezili Dantor ( [3], [4], [5]; it's a fake source, added only to get Ogando's name into the article), like many socks before them (see page history of article), a sockpuppeteer whose known geolocation is Berlin, Germany, and who is also known to have used proxies before (a proxy they had used was blocked earlier today...). While these IPs geolocate to other continents, in spite of making one of the sockmaster's signature edits. - Tom | Thomas.W talk 23:44, 13 September 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: More Cocainaenvenenada/Ismael Ogando (see above), making Cocainaenvenenada's/Ogando's signature edits on their favourite targets but geolocating to somewhere other than where the sockmaster lives. Another IP used by him today ( Special:Contributions/193.182.144.88) has already been blocked as a proxy by Zzuuzz. - Tom | Thomas.W talk 10:29, 14 September 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Two more Cocainaenvenenada. They both posted on my talk page yesterday, in a thread started by Cocainaenvenenada/Ogando, and might be meat, but are most probably Ogando himself using proxies. - Tom | Thomas.W talk 19:25, 14 September 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: abusive edits coming from European IPs by a user likely located in California. Ivanvector ( Talk/ Edits) 14:06, 16 September 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: IP geolocating to the US but used by obvious sock of Wikipedia:Sockpuppet investigations/Bosnipedian (who geolocates to Sarajevo, Bosnia). - Tom | Thomas.W talk 13:11, 17 September 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: related to the request above for 185.212.170.103, clearly the same user still on a closely related subnet. Ivanvector ( Talk/ Edits) 12:30, 23 September 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Another sock of Wikipedia:Sockpuppet investigations/Cocainaenvenenada. An IP geolocating to California making the sockmasters signature edit on Vusamazulu Credo Mutwa (see page history). Cocainaenvenenada geolocates to Berlin, Germany, but almost a dozen open proxies in other countries were blocked as socks of his not long ago (see a number of previous reports here), so using open proxies is nothing new. - Tom | Thomas.W talk 12:52, 23 September 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: As of 24 Sep 2017, is being used for editwarring and other disruption on several articles. These edits are evidently part of a pattern involving a blocked user using more than one open proxy. IP address itself appears on several lists titled "Free Bangladesh proxy". Guliolopez ( talk) 22:24, 24 September 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: The IP has been used by Wikipedia:Sockpuppet investigations/PavelStaykov (the edits about Bulgarians), but has also been used for childish vandalism, which I've never seen from Staykov, the geolocation (Nairobi, Kenya) also matches neither Staykov nor the other edits, making me believe it's an open proxy, one of many in that country it seems. It's currently blocked for three months, but if it is an open proxy it ought to get a longer block. - Tom | Thomas.W talk 18:57, 27 September 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits.
Reported for edit warring at
Sinn Féin at
WP:AN3. Previously blocked two months by
User:ProcseeBot as an open proxy, port 53281.
EdJohnston (
talk) 03:15, 5 October 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. IP's host is a clear indicator of a VPN. 172.56.39.241 ( talk) 03:20, 1 February 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. IP's host is a clear indicator of a VPN. 172.56.39.241 ( talk) 05:33, 1 February 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Spotted vandalism here, looked them up here and saw the hostname indicates a proxy of some kind. Thanks. Cyphoidbomb ( talk) 19:11, 2 February 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Clearly the LTA flag vandal. They will almost definitely return after the short block... 172.58.41.13 ( talk) 03:33, 3 February 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Blocked proxy; host offline unable to verify if this is IP is still a proxy or concern. Looking for guidance on this IP.— Preceding unsigned comment added by Dane ( talk • contribs)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Possible webhosting service. 172.58.41.122 ( talk) 01:16, 9 February 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Digital Ocean webhosting services. 172.58.40.66 ( talk) 01:43, 10 February 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Long block log of proxy blocks. Most recent edits can be found in the edit filter log. 172.58.41.58 ( talk) 18:40, 10 February 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Webhosting service. The /22 range is the network used. 172.58.40.51 ( talk) 00:50, 14 February 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Registered VPN service. 172.58.40.139 ( talk) 17:54, 14 February 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. 172.58.41.131 ( talk) 18:48, 16 February 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Registered VPN service. 172.58.41.30 ( talk) 03:45, 21 February 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. The /19 range includes the entire webhost service. 172.58.40.170 ( talk) 04:36, 24 February 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Open on port 8080. (Note: I was testing the connection of this proxy yesterday and made some edits with it...) 172.58.40.173 ( talk) 23:25, 27 February 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock at User talk:8.37.225.78. עוד מישהו Od Mishehu 06:46, 5 March 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock at User talk:146.247.83.91. עוד מישהו Od Mishehu 06:51, 5 March 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock at User talk:W33dscoper. עוד מישהו Od Mishehu 06:55, 5 March 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Appeal at User talk:Saturnalia0. Block log. Please check whether indeed open proxy.
– This proxy check request is closed and will soon be archived by a bot.
Reason: Part of Opera's SurfEasy VPN. -- 185.80.220.42 ( talk) 03:43, 11 March 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: I sometimes use a VPN (for gaming). This is a new one on NordVPN, and not blocked. Ronhjones (Talk) 20:43, 12 March 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Probably a proxy sock-the same article was targeted a notorious sockmaster before. 46.154.45.179 ( talk) 12:52, 17 March 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Likely a proxy sock-the same article was targeted by a notorious sockmaster before. 46.154.45.179 ( talk) 13:03, 17 March 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Some random troll or other used it to vandalize my talk page, geolocate says it's a confirmed proxy server. Beeblebrox ( talk) 19:54, 22 March 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: IP already blocked for vandalism; WHOIS confirms as proxy server. Thank you, <<< SOME GADGET GEEK >>> ( talk) 01:50, 23 March 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Vandalism and admittance by user it's a proxy server Ronhjones (Talk) 17:14, 25 March 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
User claims in this appeal on UTRS that the IP address is a proxy that requires authorization, not an open proxy. ~ Anachronist ( talk) 00:56, 5 April 2017 (UTC) Reason: Requested unblock.
– This proxy check request is closed and will soon be archived by a bot.
Reason: Vandalism as editing on List of programs broadcast by UNTV. LG-Gunther : Talk 04:28, 5 April 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Noticed a bit of vandalism coming from this IP. I've blocked them for 72 hours, but I noticed that What's My IP Address thinks they might be a proxy and a forum spam source. Granted, I know that this doesn't always mean anything, but my other option was to do nothing, which I didn't think would be helpful. Thanks for looking into this. Cyphoidbomb ( talk) 16:03, 7 April 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious and disruptive edits. The ip is blacklisted at dnsbl.sorbs.net, dul.dnsbl.sorbs.net, 12.apews.org. The ip is static like many proxies and is apparently used by the same person since december. Plus, its edit conduct is resembling a notorious sockmaster involved in ip-socking before. I know this project cannot detect all the proxies any time but it would be nice if someone check this highly dubious ip. 46.221.192.32 ( talk) 12:40, 18 April 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Some recent disruptive editing coming from this IP. Per the IP's block log, ProcseeBot issued a block in 2010 on the basis that the IP was a proxy of some kind. Thought it could use another look. Thanks, Cyphoidbomb ( talk) 15:46, 20 April 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock at User talk:111.88.115.104. עוד מישהו Od Mishehu 09:47, 23 April 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
– This proxy check request is closed and will soon be archived by a bot.
Used Hide.me, then asked google "what's my ip?". -barrelroll.dev ( talk) 23:33, 1 May 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Vandalism from Amazon EC cloud IP
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock.
– This proxy check request is closed and will soon be archived by a bot.
Webhosting service; continued to cause disruption after recent release from block. 2A00:1838:37:C1:0:0:0:6A9D ( talk) 01:44, 16 June 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Webhosting service; continued to cause disruption after recent release from block. Specifically from 198.15.118.143 ( talk · contribs · WHOIS). 2601:1C0:10E:B297:1056:9979:D4E9:73AE ( talk) 01:45, 19 June 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
See [6]. Web check reveals it to be a network sharing device or proxy. GAB gab 21:02, 23 June 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: This IP has been used by a proxy hopping troll on another wiki I am a checkuser on, and it belongs to Amazon. Amazon has hosting services, and if this is an open proxy being used for wiki vandalism, it's only a matter of time until someone uses it to vandalize Wikipedia. PCHS-NJROTC (Messages)Have a blessed day. 21:30, 5 July 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits; long-term prolific sockfarm Wikipedia:Sockpuppet investigations/OfficialPankajPatidar. The IP geolocates to Beijing but here they claim to be in Pakistan, which is consitent with the sockfarm's profile. _ Bri ( talk) 18:55, 7 July 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Managed to edit user:Ronhjones/Proxy, while connected through Nord vpn Canada Ronhjones (Talk) 19:40, 23 July 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits, web check reveals it to be a confirmed proxy server. Probably User:Accopulocrat. GAB gab 00:46, 31 July 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits, "Network sharing device or proxy server... Likely mail server". GAB gab 00:03, 1 August 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits Beyond My Ken ( talk) 14:25, 31 August 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits Beyond My Ken ( talk) 14:25, 31 August 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Disruptive edits over the past year, this says it's a network sharing device or proxy server. -★- PlyrStar93. → Message me. ← 00:09, 23 October 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Began making same pattern of disruptive edits to fast food mascot articles after a prior IP (200.76.184.163) was given a level 4 warning. IP Quality Score lists as a proxy. RA0808 talk contribs 15:20, 24 October 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: ISP is server4you, indicating a web hosting service. Edit warring on some pages. -★- PlyrStar93. → Message me. ← 14:52, 28 October 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Disruptive edits adding deliberate misinformation, IP Quality Score flags as a proxy. RA0808 talk contribs 21:12, 28 October 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits 222.167.166.187 ( talk)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits, vandalism, School block. 222.167.166.187 ( talk)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits, blocked proxy. 222.167.166.187 ( talk)
– This proxy check request is closed and will soon be archived by a bot.
Reason: vandalism from this IP. ISP is Microsoft Corporation and organization is listed as Microsoft Azure, which is a cloud computing platform to deploy applications as well as web hosts. Geolocation shows up as East Coast of US, which is not where Microsoft's corporate office is at, but rather a Microsoft datacenter (Boydton, VA). -★- PlyrStar93. → Message me. ← 19:33, 29 October 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Vandalism, blocked proxy 222.167.166.187 ( talk) 21:06, 30 October 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: 185.17.132.66:53281 is an open proxy which was used for a vandalbot attack on Commons. — Guan aco 08:12, 31 October 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits, appears to be Zscaler proxy ☆ Bri ( talk) 14:41, 1 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. whatismyipaddress.com says that it is a VPN server. Even though the IP address is already blocked, it should be hard-blocked and possibly for a longer duration. 24.51.86.102 ( talk) 18:07, 1 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Recently started editing again within the last few days. Blocked by the proxy bot, still an open proxy. 159.89.10.188 ( talk) 15:54, 2 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Zscaler open proxy. 116.220.7.10 ( talk) 20:43, 3 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. whatismyipaddress.com reports it as a spam source (within the last 30 days, etc.). 82.0.113.79 ( talk) 18:30, 5 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Hurricane Electric open proxy. 176.103.48.38 ( talk) 16:18, 9 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Zscaler open proxy. 122.197.215.184 ( talk) 17:59, 10 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious (promotional) edits; socking; has been identified as Microsoft Azure host. ☆ Bri ( talk) 18:02, 10 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: sockpuppetry, IPs in France, England, and Japan, being used by a banned user located in the United States who has used open proxies for abuse in the past. (NOTE: I combined a few open reports) Ivanvector ( Talk/ Edits) 15:35, 18 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits — Preceding unsigned comment added by 95.153.132.82 ( talk • contribs) 01:28, 17 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: edit war-ish edit summaries. Host name is vds-holanet.timeweb.ru and ISP is TimeWeb Ltd., a Russian web hosting company. -★- PlyrStar93. → Message me. ← 03:07, 19 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Recently blocked as a webhost on meta.wiki, and was once blocked on en.wiki too. This /32 IPv6 range still appears to be a webhosting service. 219.98.8.174 ( talk) 22:40, 19 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Fanciful hoaxing & BLP violations in the style of Jaredgk2008.— Odysseus 147 9 05:34, 21 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
I work for the ISP which owns this netblock and can confirm that this is a range of DHCP addresses handed out to residential customers and has no connection to our colocation facilities. Refer to this discussion if you want to know why I posted this request here. Reason: Incorrectly blocked as colocationwebhost. Opsftw ( talk) 18:38, 27 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: WP:DUCK test matches Wikipedia:Long-term abuse/109.151.65.218, behavior matches that one almost spot on. However, this IP's WHOIS data indicates a US-based IP address, while all of the others indicate UK-based IP addresses. Asking for a proxy check to see if they are using an open proxy to mask their location. IP is already blocked a short time based on behavioral evidence. -- Jayron 32 20:07, 27 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. I'm not sure how to check which port the IP is open on, but whatismyipaddress.com labels it as a "confirmed proxy server".
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits, listed as problem host by Barracuda. ☆ Bri ( talk) 18:38, 28 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: All edits are vandalism/unconstructive. Also some other edits in other wikis: frwiki/ simplewiki are the same type of vandalism. Proxy checker shows as VPN/proxy. Based on behavior, this is the Pikepass vandal at frwiki, who is known to abuse proxies (e.g. previous blocked IP 96.92.203.45 now globally blocked 1 year as open proxy). -★- PlyrStar93. → Message me. ← 04:11, 29 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Dedicated server proxy IP. May need to be rangeblocked as {{
webhostblock}}
.
116.123.126.79 (
talk) 10:05, 29 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. IP address is back to being a proxy once again per whatismyipaddress.com (refer to block log). 203.128.191.50 ( talk) 18:04, 29 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. User has admitted that this IP address is a Tor exit node. 60.36.225.155 ( talk) 13:10, 30 November 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. Hostname is: "hosted-by.seedvps.com" which is registered to
this VPN hosting service. According to the
WHOIS links,
46.166.176.0/21 (
block range ·
block log (
global) ·
WHOIS (partial)) would be the correct range to block if a {{
webhostblock}}
would be performed.
76.109.126.61 (
talk) 05:59, 4 December 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits, address query reports Webhosting cloud service Avast "Network sharing device or proxy server", poss proxy thing ☆ Bri ( talk) 04:48, 5 December 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock.
– This proxy check request is closed and will soon be archived by a bot.
Reason: Recently used by sockpuppeteer; whatismyaddress.com says it's a proxy server. Trivialist ( talk) 21:10, 17 December 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. confirmed proxy server and webhosting service. 180.47.118.156 ( talk) 18:58, 18 December 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits
See a complaint of disruptive editing at WP:Administrators' noticeboard#Editor being bullied. User:Berean Hunter tried checking the IP at one of the IP lookup sites, and that site reports it to be an open proxy. I am unsure whether to trust this verdict. EdJohnston ( talk) 00:34, 21 December 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: See discussion, the final section at WP:ANI. In short, someone created a couple of attack accounts, and when they were blocked, this IP continued the disruption. According to checkuser NinjaRobotPirate, the accounts are using proxies, so I suppose it's likely that this one also might be. It was previously blocked by Procseebot, but that block expired without being renewed, so I'm not clear if that means that the bot hadn't gotten around to reblocking it yet or if it means that it's not a proxy anymore. I gave it a short block for the disruption, but please lengthen the block if it's a proxy. Nyttend ( talk) 14:05, 23 December 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
A few minutes after I made the block referenced in the previous section, I got this friendly notice from an IP with no previous edits. This is the first logged action I've made in several days, aside from unprotecting a page (can't imagine anyone objecting to that in such a manner), so I strongly suspect that it's related. Seeing that 110.77.181.148 is Thai, and this one's Chinese, I strongly suspect that they're both open proxies. Nyttend ( talk) 14:24, 23 December 2017 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits. IP has been blocked twice in the past as an open proxy. 14.190.44.204 ( talk) 17:47, 28 December 2017 (UTC)