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.
Reason: IP recently used for vandalism, was blocked by the bot back in October as an open proxy. Block duration should be extended (if it doesn't expire by the time this report is actioned). 60.138.0.247 ( talk) 19:30, 16 May 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Shingling334 on Melbicom hosting/colocation. IamNotU ( talk) 16:35, 17 May 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Webhost back to disruptive editing after their last block recently expired in April 2019. 126.106.254.136 ( talk) 03:44, 23 May 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: OVH Hosting, used by Shingling334 sock IamNotU ( talk) 19:40, 24 May 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Pakistani IP seems to be carrying on edit warring of other IPs in e.g. Africa. Listed as "high risk" and "blacklisted" by IPQualityScore. IamNotU ( talk) 22:23, 27 May 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Used by obvious sock of Shingling334, listed as proxy by IPQualityCheck. IamNotU ( talk) 13:11, 9 June 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Sockpupptry please see Wikipedia:Sockpuppet investigations/Strongwik2324. GSS ( talk| c| em) 16:05, 1 July 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Some (though not all) edits are blatant vandalism. Reported as proxy/vpn by whatismyipaddress.com and ipqualityscore.com IamNotU ( talk) 11:39, 8 July 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits ☆ Bri ( talk) 16:49, 11 July 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Yet another Shingling334 sock proxy on GlobalTeleHost. Reported as blacklisted and proxy/vpn by IPQualityscore. IamNotU ( talk) 19:23, 18 July 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: geforce now ip, using the steam browser to type this, can be used for disruptive editing so iam requesting a block. 8.37.154.122 ( talk) 14:13, 4 May 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits located during Japanelemu sockfarm cleanup. Edits from 45.121.208.0/22, WHOIS lists an Australian server farm provider ☆ Bri ( talk) 19:54, 18 May 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
We've had an ongoing massive campaign to insert the same reference spamming type edit into a range of machine learning articles. I'd estimate at least 30 attempts over the year that I've been closely watching. The pattern is a batch / rash of edits by brand new ip's in a single geographic area. I see that the source of a previous batch is now blocked. They just started another burst, the same edit edits as before, this from three new (single edit) IP's in the same area in Russia, triple entering the same edit on one article in 2 days. Sincerely, North8000 ( talk) 01:39, 21 May 2019 (UTC)
SEVEN-SKY Dynamic broadband customers
, other two as ISKRATELECOM
.) Unlikely IP is an open proxy. Closing. --
MrClog (
talk) 17:53, 8 September 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Not sure if it's an open proxy or not, but the host name "client.fttb.2day.kz" seems a bit suspicious. 123.218.188.28 ( talk) 17:13, 21 May 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Amazon AWS webhosting. 123.218.188.28 ( talk) 18:59, 21 May 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Hurricane Electric. 60.133.229.157 ( talk) 05:02, 18 June 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open proxy/web hosting. Most recently abused from 2a01:4f9:2a:6d5::2 ( talk · contribs · WHOIS). 92.17.91.122 ( talk) 22:41, 23 July 2019 (UTC)
{{colocationwebhost}}: <!-- Hetzner -->
MrClog (
talk) 18:19, 7 September 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits; recently blocked 31 hrs. Stalk toy also indicates two blocks on other wikis. Zaxxon0 ( talk) 06:50, 6 August 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Linode cloud server, used by obvious sock of Shingling334, listed as high-risk blacklisted proxy by IPQualityScore. IamNotU ( talk) 14:20, 11 August 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Another socking proxy. GlobalTeleHost, IPQualityScore lists as blacklisted/proxy. Same thing as now-blocked Special:Contributions/198.57.27.196. IamNotU ( talk) 12:18, 14 August 2019 (UTC)
{{colocationwebhost}} <!-- gthost.com -->
.
MrClog (
talk) 14:05, 7 September 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Reported as blacklisted, high-risk proxy; long edit history of little but vandalism. -- IamNotU ( talk) 21:01, 26 August 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Another obvious Shingling334 sock on another linode host... IamNotU ( talk) 22:23, 31 August 2019 (UTC)
{{Colocationwebhost}} <!-- Linode -->
.
MrClog (
talk) 13:30, 7 September 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: IP is by "FranTech Solutions" Zaxxon0 ( talk) 09:36, 10 September 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock. 81.162.224.114 ( talk) 14:45, 14 September 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Another Shingling334 proxy. IamNotU ( talk) 22:03, 26 September 2019 (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.
Reason: IP recently used for vandalism, was blocked by the bot back in October as an open proxy. Block duration should be extended (if it doesn't expire by the time this report is actioned). 60.138.0.247 ( talk) 19:30, 16 May 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Shingling334 on Melbicom hosting/colocation. IamNotU ( talk) 16:35, 17 May 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Webhost back to disruptive editing after their last block recently expired in April 2019. 126.106.254.136 ( talk) 03:44, 23 May 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: OVH Hosting, used by Shingling334 sock IamNotU ( talk) 19:40, 24 May 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Pakistani IP seems to be carrying on edit warring of other IPs in e.g. Africa. Listed as "high risk" and "blacklisted" by IPQualityScore. IamNotU ( talk) 22:23, 27 May 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Used by obvious sock of Shingling334, listed as proxy by IPQualityCheck. IamNotU ( talk) 13:11, 9 June 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Sockpupptry please see Wikipedia:Sockpuppet investigations/Strongwik2324. GSS ( talk| c| em) 16:05, 1 July 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Some (though not all) edits are blatant vandalism. Reported as proxy/vpn by whatismyipaddress.com and ipqualityscore.com IamNotU ( talk) 11:39, 8 July 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits ☆ Bri ( talk) 16:49, 11 July 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Yet another Shingling334 sock proxy on GlobalTeleHost. Reported as blacklisted and proxy/vpn by IPQualityscore. IamNotU ( talk) 19:23, 18 July 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: geforce now ip, using the steam browser to type this, can be used for disruptive editing so iam requesting a block. 8.37.154.122 ( talk) 14:13, 4 May 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits located during Japanelemu sockfarm cleanup. Edits from 45.121.208.0/22, WHOIS lists an Australian server farm provider ☆ Bri ( talk) 19:54, 18 May 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
We've had an ongoing massive campaign to insert the same reference spamming type edit into a range of machine learning articles. I'd estimate at least 30 attempts over the year that I've been closely watching. The pattern is a batch / rash of edits by brand new ip's in a single geographic area. I see that the source of a previous batch is now blocked. They just started another burst, the same edit edits as before, this from three new (single edit) IP's in the same area in Russia, triple entering the same edit on one article in 2 days. Sincerely, North8000 ( talk) 01:39, 21 May 2019 (UTC)
SEVEN-SKY Dynamic broadband customers
, other two as ISKRATELECOM
.) Unlikely IP is an open proxy. Closing. --
MrClog (
talk) 17:53, 8 September 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Not sure if it's an open proxy or not, but the host name "client.fttb.2day.kz" seems a bit suspicious. 123.218.188.28 ( talk) 17:13, 21 May 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Amazon AWS webhosting. 123.218.188.28 ( talk) 18:59, 21 May 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Hurricane Electric. 60.133.229.157 ( talk) 05:02, 18 June 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Open proxy/web hosting. Most recently abused from 2a01:4f9:2a:6d5::2 ( talk · contribs · WHOIS). 92.17.91.122 ( talk) 22:41, 23 July 2019 (UTC)
{{colocationwebhost}}: <!-- Hetzner -->
MrClog (
talk) 18:19, 7 September 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Suspicious edits; recently blocked 31 hrs. Stalk toy also indicates two blocks on other wikis. Zaxxon0 ( talk) 06:50, 6 August 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Linode cloud server, used by obvious sock of Shingling334, listed as high-risk blacklisted proxy by IPQualityScore. IamNotU ( talk) 14:20, 11 August 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Another socking proxy. GlobalTeleHost, IPQualityScore lists as blacklisted/proxy. Same thing as now-blocked Special:Contributions/198.57.27.196. IamNotU ( talk) 12:18, 14 August 2019 (UTC)
{{colocationwebhost}} <!-- gthost.com -->
.
MrClog (
talk) 14:05, 7 September 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Reported as blacklisted, high-risk proxy; long edit history of little but vandalism. -- IamNotU ( talk) 21:01, 26 August 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Another obvious Shingling334 sock on another linode host... IamNotU ( talk) 22:23, 31 August 2019 (UTC)
{{Colocationwebhost}} <!-- Linode -->
.
MrClog (
talk) 13:30, 7 September 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: IP is by "FranTech Solutions" Zaxxon0 ( talk) 09:36, 10 September 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Requested unblock. 81.162.224.114 ( talk) 14:45, 14 September 2019 (UTC)
– This proxy check request is closed and will soon be archived by a bot.
Reason: Another Shingling334 proxy. IamNotU ( talk) 22:03, 26 September 2019 (UTC)