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.
Obvious troll editing from a confirmed proxy server. GabeMc ( talk| contribs) 20:07, 1 July 2013 (UTC) Reason: Suspicious edits from a confirmed proxy server.
– This proxy check request is closed and will soon be archived by a bot.
Reason: VPN. Triggered a filter. Possible spambot. [ oakweb.com] — Ginsuloft ( talk) 14:48, 2 July 2013 (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. This user displays an uncanny knowledge of our policies for such a short editing career. The IP geolocates to a non-English speaking county (Peru) and is in the same block as a known honeypot-trapped spam mail server. - Mr X 20:02, 10 July 2013 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits –— Preceding unsigned comment added by Bigpoliticsfan ( talk • contribs) 00:55, 19 July 2013 Not currently an open proxy This is at least the third time this ISP has been reported here. To me, this seems like a satellite internet provider that uses either caching proxies or just a highly dynamic range. It does not appear to be an open proxy, nor have any of the other similar ones I've seen. Sailsbystars ( talk) 19:36, 20 July 2013 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Port 8080 open Ginsuloft ( talk) 19:04, 22 July 2013 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
The range was blocked on 6 April 2013 by Elockid, the reason given being {{ webhostblock}}. There is now an unblock request at User talk:Pankkake, saying "2001:41D0:0:0:0:0:0:0/40 is not an "open proxy", it's a whole hoster and ISP, OVH". I would be grateful if someone with more knowledge of these things than me would look at it. JamesBWatson ( talk) 09:49, 23 July 2013 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Port 80 open + edits are spambot-like. (Several edits were speedy deleted, incase a non-admin is wondering "what edits") Ginsuloft ( talk) 22:47, 23 July 2013 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: As above, port 80 open + spambot-style editing. Ginsuloft ( talk) 07:41, 24 July 2013 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock via UTRS. Note that from the unblock request this is the "Rhine-Waal University's NAT IP for all HTTP/HTTPS traffic of LAN users, transparently routed through a Web Security Gateway to secure LAN users on these kinds of traffic".-- Jezebel'sPonyo bons mots 15:58, 24 July 2013 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Suspicious edits. It just occurred to me that these might be spambots and I whois'd them and they were registered to Chinanet (lots of spambots from that ISP). TCP port 80 seems to be intermittently open. Ginsuloft ( talk) 21:11, 1 August 2013 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: User talk:Arielco is caught in a proxy block of the noted IP address.-- Jezebel'sPonyo bons mots 17:54, 2 August 2013 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock on talk page Ronhjones (Talk) 19:45, 4 August 2013 (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: Requested unblock via UTRS.-- Jezebel'sPonyo bons mots 16:36, 14 August 2013 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: This one has a weird editing history. Sometimes it looks like an Intel engineer, sometimes like an experienced Wikipedian, sometimes like a child, sometimes like someone in Washington State, sometimes like someone in India. Could it be an open proxy? Wifi Hotspot? Or maybe someone is using a VPN and his kids are sharing his connection? Weird edits include: Very useful edit, [1] Spam, [2] Intel-related technical information, [3] Removal of a template, [4] and Vandalism. [5] -- Guy Macon ( talk) 17:46, 18 August 2013 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: At UTRS #8566, the user claims to be using a private proxy to edit. If there are indeed innocent users and/or legitimate closed proxies in the range, could it be reduced to a softblock? -- King of ♥ ♦ ♣ ♠ 03:37, 20 August 2013 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock via UTRS.-- Jezebel'sPonyo bons mots 22:33, 4 September 2013 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: At UTRS #8648, user claims it is his normal Free (ISP) IP address. If it is found that not all of the range can be used as an open proxy, could it be unblocked or at least reduced to softblock? -- King of ♥ ♦ ♣ ♠ 08:32, 5 September 2013 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
User claims OPs have been disabled. Daniel Case ( talk) 22:13, 9 September 2013 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock. See User talk:Duke Khan. IP blocked three days ago by Elockid ( talk). JohnCD ( talk) 22:11, 17 September 2013 (UTC)
Part of the determination of what to do at Wikipedia:Archive.is RFC depends on whether my suspicions of proxy abuse are well founded. Any attention that anyone cares to pay to the long list of IPs detailed at the RFC will be greatly appreciated.— Kww( talk) 01:18, 22 September 2013 (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: Requested unblock at User talk:3fire76.-- Jezebel'sPonyo bons mots 18:33, 24 September 2013 (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.
Obvious troll editing from a confirmed proxy server. GabeMc ( talk| contribs) 20:07, 1 July 2013 (UTC) Reason: Suspicious edits from a confirmed proxy server.
– This proxy check request is closed and will soon be archived by a bot.
Reason: VPN. Triggered a filter. Possible spambot. [ oakweb.com] — Ginsuloft ( talk) 14:48, 2 July 2013 (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. This user displays an uncanny knowledge of our policies for such a short editing career. The IP geolocates to a non-English speaking county (Peru) and is in the same block as a known honeypot-trapped spam mail server. - Mr X 20:02, 10 July 2013 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits –— Preceding unsigned comment added by Bigpoliticsfan ( talk • contribs) 00:55, 19 July 2013 Not currently an open proxy This is at least the third time this ISP has been reported here. To me, this seems like a satellite internet provider that uses either caching proxies or just a highly dynamic range. It does not appear to be an open proxy, nor have any of the other similar ones I've seen. Sailsbystars ( talk) 19:36, 20 July 2013 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Port 8080 open Ginsuloft ( talk) 19:04, 22 July 2013 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
The range was blocked on 6 April 2013 by Elockid, the reason given being {{ webhostblock}}. There is now an unblock request at User talk:Pankkake, saying "2001:41D0:0:0:0:0:0:0/40 is not an "open proxy", it's a whole hoster and ISP, OVH". I would be grateful if someone with more knowledge of these things than me would look at it. JamesBWatson ( talk) 09:49, 23 July 2013 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Port 80 open + edits are spambot-like. (Several edits were speedy deleted, incase a non-admin is wondering "what edits") Ginsuloft ( talk) 22:47, 23 July 2013 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: As above, port 80 open + spambot-style editing. Ginsuloft ( talk) 07:41, 24 July 2013 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock via UTRS. Note that from the unblock request this is the "Rhine-Waal University's NAT IP for all HTTP/HTTPS traffic of LAN users, transparently routed through a Web Security Gateway to secure LAN users on these kinds of traffic".-- Jezebel'sPonyo bons mots 15:58, 24 July 2013 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Suspicious edits. It just occurred to me that these might be spambots and I whois'd them and they were registered to Chinanet (lots of spambots from that ISP). TCP port 80 seems to be intermittently open. Ginsuloft ( talk) 21:11, 1 August 2013 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: User talk:Arielco is caught in a proxy block of the noted IP address.-- Jezebel'sPonyo bons mots 17:54, 2 August 2013 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock on talk page Ronhjones (Talk) 19:45, 4 August 2013 (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: Requested unblock via UTRS.-- Jezebel'sPonyo bons mots 16:36, 14 August 2013 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: This one has a weird editing history. Sometimes it looks like an Intel engineer, sometimes like an experienced Wikipedian, sometimes like a child, sometimes like someone in Washington State, sometimes like someone in India. Could it be an open proxy? Wifi Hotspot? Or maybe someone is using a VPN and his kids are sharing his connection? Weird edits include: Very useful edit, [1] Spam, [2] Intel-related technical information, [3] Removal of a template, [4] and Vandalism. [5] -- Guy Macon ( talk) 17:46, 18 August 2013 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: At UTRS #8566, the user claims to be using a private proxy to edit. If there are indeed innocent users and/or legitimate closed proxies in the range, could it be reduced to a softblock? -- King of ♥ ♦ ♣ ♠ 03:37, 20 August 2013 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock via UTRS.-- Jezebel'sPonyo bons mots 22:33, 4 September 2013 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: At UTRS #8648, user claims it is his normal Free (ISP) IP address. If it is found that not all of the range can be used as an open proxy, could it be unblocked or at least reduced to softblock? -- King of ♥ ♦ ♣ ♠ 08:32, 5 September 2013 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
User claims OPs have been disabled. Daniel Case ( talk) 22:13, 9 September 2013 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock. See User talk:Duke Khan. IP blocked three days ago by Elockid ( talk). JohnCD ( talk) 22:11, 17 September 2013 (UTC)
Part of the determination of what to do at Wikipedia:Archive.is RFC depends on whether my suspicions of proxy abuse are well founded. Any attention that anyone cares to pay to the long list of IPs detailed at the RFC will be greatly appreciated.— Kww( talk) 01:18, 22 September 2013 (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: Requested unblock at User talk:3fire76.-- Jezebel'sPonyo bons mots 18:33, 24 September 2013 (UTC)