This page is an archive. Do not edit the contents of this page. Please direct any additional comments to the current main page. |
{{ proxycheckstatus}}
Reason: Datacenter run by Zayo Infrastructure France SA wizzito | say hello! 01:01, 20 April 2023 (UTC)
{{ proxycheckstatus}}
Reason: Possible VPN. 73.67.145.30 ( talk) 03:21, 8 May 2023 (UTC)
{{ proxycheckstatus}}
Reason: Cloud proxy server recently used for abuse. 2601:1C0:4401:F60:442:8414:7C65:842 ( talk) 17:39, 1 September 2023 (UTC)
{{ proxycheckstatus}}
{{ proxycheckstatus}}
Reason: Disruption. Possible VPN server. 73.67.145.30 ( talk) 19:22, 7 May 2023 (UTC)
{{ proxycheckstatus}}
Reason: Datacenter IP. Please block this range as it is being abused by User:Anne Barrington's socks. 99.241.217.73 ( talk) 15:27, 3 August 2023 (UTC)
{{ proxycheckstatus}}
Reason: Open proxy/VPN service. 2601:601:51C:6A8:4D49:CA1F:3CB5:D334 ( talk) 17:22, 3 September 2023 (UTC)
{{ proxycheckstatus}}
Reason: Seems to be an open proxy, VPN I think registered to Department of Veteran Affairs. Recent Abuse according to IpCheck on toolforge.
Seawolf35 (
talk) 15:30, 6 September 2023 (UTC)
{{ proxycheckstatus}}
Open proxy. The IP has already been blocked in the French Wikipedia for exactly this reason. It has been the source of extensive vandalism. Fisandelli ( talk) 20:35, 6 September 2023 (UTC)
{{ proxycheckstatus}}
Reason: Blocked before as proxy, tagged as public proxy by whatismyipaddress.com, being used for vandalism by LTA who just 1 day ago used <an IP> (also tagged a public proxy) located very far away from the new IP. 2804:F14:808E:A601:F0B3:ED6F:D12C:B951 ( talk) 10:22, 6 July 2023 (UTC)
{{ proxycheckstatus}}
Reason: Cloud proxy/VPN server. 2601:1C0:4401:F60:CC1B:7FBB:65E7:4373 ( talk) 18:00, 8 August 2023 (UTC)
{{ proxycheckstatus}}
Reason: Belongs to "HostRush" VPN services. Disruption from 207.231.105.153 ( talk · contribs · WHOIS). See WHOIS for /21 range confirmation. 2601:1C0:4401:F60:B09F:5E03:B2DE:5C0F ( talk) 17:55, 12 August 2023 (UTC)
{{ proxycheckstatus}}
Reason: Although not a proxy, this IP is from a web hosting provider. This IP is allocated to the Veselí nad Lužnicí town government. Looking at the IP's global contributions, it appears it this IP has been blocked on the German Wikipedia [1].
Update #1: Added another IP that might from the same web hosting provider. Apparently, this IP was blocked on the Spanish Wikipedia for being a proxy.
SpinnerLaserzthe2nd ( talk) 20:07, 19 August 2023 (UTC)
{{ proxycheckstatus}}
OVH, several proxies and VPNs. MarioGom ( talk) 08:59, 27 August 2023 (UTC)
{{ proxycheckstatus}}
Reason: Webhost. 2601:601:51C:A47:E530:E9E5:B590:2100 ( talk) 15:17, 8 September 2023 (UTC)
{{ proxycheckstatus}}
Reason: Webhost/VPN. 2601:601:51C:2D16:612F:DB7E:1100:4008 ( talk) 04:42, 9 September 2023 (UTC)
{{ proxycheckstatus}}
Reason: Cloud/VPN server. 2601:601:51C:D94:6487:982:C0FF:2E5D ( talk) 19:46, 10 September 2023 (UTC)
{{ proxycheckstatus}}
Reason: Despite the recent block in French Wikipedia due to remove sources on the Angolan Civil War article, the proxy IP had started various sources in Wikipedias of other languages. SpinnerLaserzthe2nd ( talk) 14:29, 6 November 2023 (UTC)
{{ proxycheckstatus}}
Reason: The IP is hosted on Acehost. See also the edit summary on this diff. -- Leonidlednev ( T, C, L) 05:45, 4 August 2023 (UTC)
{{ proxycheckstatus}}
Reason: Webhost IP range recently used for disruption. 2601:1C0:4401:F60:D587:449F:646D:BACC ( talk) 17:59, 18 August 2023 (UTC)
{{ proxycheckstatus}}
Reason: Repeating blocked IP edits via use of VPN; see edit history of Hispanics and Latinos in Los Angeles. Jalen Folf (talk) 01:27, 12 October 2023 (UTC)
{{ proxycheckstatus}}
Reason: This IP has been detected as a proxy IP ( https://www.ipqualityscore.com/free-ip-lookup-proxy-vpn-test/lookup/89.119.251.40). According to CleanTalk, this IP is reported as a spam IP that also committed brute force attacks. SpinnerLaserzthe2nd ( talk) 20:24, 26 October 2023 (UTC)
{{ proxycheckstatus}}
Reason: Webhost. 73.67.145.30 ( talk) 18:12, 25 May 2023 (UTC)
{{ proxycheckstatus}}
Reason: Webhost/VPN range. 2601:1C0:4401:F60:592C:6755:67BE:F9D9 ( talk) 20:27, 26 August 2023 (UTC)
{{ proxycheckstatus}}
Webhost/VPN Seawolf35 ( talk) 16:20, 28 September 2023 (UTC)
{{ proxycheckstatus}}
Reason: This is likely to be block-evasion from Belteshazzar who has been globally banned by the WMF [2]. From a search I did, the IP is listed as an open proxy. Psychologist Guy ( talk) 20:30, 8 October 2023 (UTC)
{{ proxycheckstatus}}
Reason: Open proxy per block on Commons, see their blocking log. -- LemonSlushie 🍋 ( talk) ( edits) 07:01, 25 October 2023 (UTC)
{{ proxycheckstatus}}
Reason: Undoing categorization work which was done after an informal discussion and is now in my talk page demanding an explaination. Omnis Scientia ( talk) 21:44, 7 December 2023 (UTC)
{{ proxycheckstatus}}
Reason: Disruption, possibly a VPN server. 2601:1C0:4401:F60:817:B3DA:A0F9:1195 ( talk) 20:01, 19 August 2023 (UTC)
{{ proxycheckstatus}}
Reason: VPN server. Previously blocked. 2601:1C0:4401:F60:7C72:5877:80EB:F896 ( talk) 19:31, 14 August 2023 (UTC)
{{ proxycheckstatus}}
Reason: VPN server/datacenter IP. Vandalism, see edit filter log. 2601:1C0:4401:F60:B09F:5E03:B2DE:5C0F ( talk) 17:49, 12 August 2023 (UTC)
{{ proxycheckstatus}}
Pro forma. — Mdaniels5757 ( talk • contribs) 21:37, 17 December 2023 (UTC)
{{ proxycheckstatus}}
Reason: disruptive edits, multiple blocks over the years, including proxy block. Nobody ( talk) 14:12, 3 January 2024 (UTC)
{{ proxycheckstatus}}
Reason: This IP came up on UTRS. Blocked both globally and locally, but from my checks it seems like it isn't a proxy any longer. DatGuy Talk Contribs 19:31, 1 January 2024 (UTC)
{{ proxycheckstatus}}
Reason: Listed as proxy at IPQualityScore. The whole range 103.127.216.1-103.127.219.254 belongs to the same provider. Siawase ( talk) 10:32, 3 January 2024 (UTC)
{{ proxycheckstatus}}
Reason: Listed as a VPN server. 2601:5CC:8300:A7F0:7186:1FB7:1CA:90A5 ( talk) 23:39, 16 January 2024 (UTC)
{{ proxycheckstatus}}
Reason: Spur reports "belongs to a call-back proxy network". See Talk:Catalent#Undisclosed paid edits and recurring attempts by IPs to add unreferenced financial info to the article, and now this IP is doing same.
See WP:WikiProject on open proxies/Requests/Archives/46#175.158.155.92/Requests/Archives/46#175.158.155.92 for MarioGom's findings on proxy IP(s) at the same article in 2022. ☆ Bri ( talk) 18:29, 19 January 2024 (UTC)
{{ proxycheckstatus}}
Reason: Webhost/VPN. 73.67.145.30 ( talk) 16:23, 17 May 2023 (UTC)
{{ proxycheckstatus}}
Individual IP's in these two ranges, 14.231.169.16 and 113.177.23.65, have already been blocked as proxies on the Swedish and Russian Wikipedias respectively. Both blocked IP's were used on those projects by User:Phạm Văn Rạng to evade their global lock. They look to be using a larger portion of these IP ranges for evasion on this project as well. I've already applied some range blocks to deal with the evasion, but some insight into what's going on technically would be appreciated. Courtesy pinging @ Riggwelter: and @ Q-bit array: who applied to blocks on the other projects, in case you want to weigh in here. Sir Sputnik ( talk) 17:19, 30 July 2023 (UTC)
{{ proxycheckstatus}}
Reason: Identified as VPN server by WHOIS. Spur reports "belongs to a call-back proxy network". IP hopping/proxy use at beauty pageant pages strongly suggests nefarious editing, there are many sockfarms active at the same pages these are editing. IPs are listed roughly from most recent to least. ☆ Bri ( talk) 04:16, 18 January 2024 (UTC)
{{ proxycheckstatus}}
Reason: IncogNet LLC. Listed as VPN by WP:IP Info feature. Someone who's wrong on the internet ( talk) 06:02, 18 January 2024 (UTC)
{{ proxycheckstatus}}
Reason: Proxy IP check by Proxy API Checker SpinnerLaserzthe2nd ( talk) 00:10, 21 January 2024 (UTC)
{{ proxycheckstatus}}
Reason: IP made some unconstructive edits today and in the past. Nobody ( talk) 14:41, 15 February 2024 (UTC)
{{ proxycheckstatus}}
Used by known proxy-hopping LTA. See Wikipedia:Sockpuppet investigations/Blue Barette Bam. Someone who's wrong on the internet ( talk) 23:45, 24 January 2024 (UTC)
{{ proxycheckstatus}}
Reason: The range seems to be announced by IPXO (per Hurricane Electric), an "IP marketplace" according to their website. All IPs in the range who have made contributions since 1 January 2023 are active on ExpressVPN, as well as a handful of varying residential proxies according to Spur. I've not done a fully exhaustive check on the range yet, but the only IPs I've seen not flagged as ExpressVPN on the Spur data are .251-.255, though they are still listed as data centre IPs.
It may also be worth the other /24s listed on HE as being announced by IPXO as well for any that haven't yet been blocked (some have) but probably should be. Sideswipe9th ( talk) 20:56, 4 February 2023 (UTC)
{{ proxycheckstatus}}
Reason: VPN server. 73.67.145.30 ( talk) 18:38, 17 April 2023 (UTC)
{{ proxycheckstatus}}
Reason: VPN network/Webhosting service. 73.67.145.30 ( talk) 08:05, 1 May 2023 (UTC)
{{ proxycheckstatus}}
Reason: Requested unblock. I'm unable to edit wikipedia pages from this IP (our office) even when logged in. The IP is statically allocated to us (since Feb 2022), we're not running any proxy and I'm not seeing any unusual open ports or suspicious network activity. xmath ( talk) 19:30, 30 June 2023 (UTC)
Update: never mind, the block isn't for our IP specifically, apparently the entire IP range has been mistakenly classified as webhosting instead of FTTH/FTTB. xmath ( talk) 20:59, 30 June 2023 (UTC)
{{ proxycheckstatus}}
Reason: Made an unsourced BLP edit. SPUR shows possible call-back proxy. Nobody ( talk) 12:38, 1 March 2024 (UTC)
{{ proxycheckstatus}}
Reason: Colocation webhost. Looking at the WHOIS info, it appears to belong to Hetzner, a provider of cloud servers, dedicated servers, colocation and web hosting, according to their website. Looking at the block log of this IP, it was blocked in February 2022 for two years as a colocation webhost before. Reason why I'm reporting is because soon after the expiration of that 2 year block, some user at least seems to be using it to vandalise various music-related articles; see Wikipedia:Administrators' noticeboard/Incidents#Need a rangeblock for Oregon IPs for more insight on this. This is an example of their vandalism, where they're introducing incorrect information into the article, with no explanation, sources, etc. There are so many recent edits like these from this range. — AP 499D25 (talk) 13:32, 4 March 2024 (UTC)
This page is an archive. Do not edit the contents of this page. Please direct any additional comments to the current main page. |
{{ proxycheckstatus}}
Reason: Datacenter run by Zayo Infrastructure France SA wizzito | say hello! 01:01, 20 April 2023 (UTC)
{{ proxycheckstatus}}
Reason: Possible VPN. 73.67.145.30 ( talk) 03:21, 8 May 2023 (UTC)
{{ proxycheckstatus}}
Reason: Cloud proxy server recently used for abuse. 2601:1C0:4401:F60:442:8414:7C65:842 ( talk) 17:39, 1 September 2023 (UTC)
{{ proxycheckstatus}}
{{ proxycheckstatus}}
Reason: Disruption. Possible VPN server. 73.67.145.30 ( talk) 19:22, 7 May 2023 (UTC)
{{ proxycheckstatus}}
Reason: Datacenter IP. Please block this range as it is being abused by User:Anne Barrington's socks. 99.241.217.73 ( talk) 15:27, 3 August 2023 (UTC)
{{ proxycheckstatus}}
Reason: Open proxy/VPN service. 2601:601:51C:6A8:4D49:CA1F:3CB5:D334 ( talk) 17:22, 3 September 2023 (UTC)
{{ proxycheckstatus}}
Reason: Seems to be an open proxy, VPN I think registered to Department of Veteran Affairs. Recent Abuse according to IpCheck on toolforge.
Seawolf35 (
talk) 15:30, 6 September 2023 (UTC)
{{ proxycheckstatus}}
Open proxy. The IP has already been blocked in the French Wikipedia for exactly this reason. It has been the source of extensive vandalism. Fisandelli ( talk) 20:35, 6 September 2023 (UTC)
{{ proxycheckstatus}}
Reason: Blocked before as proxy, tagged as public proxy by whatismyipaddress.com, being used for vandalism by LTA who just 1 day ago used <an IP> (also tagged a public proxy) located very far away from the new IP. 2804:F14:808E:A601:F0B3:ED6F:D12C:B951 ( talk) 10:22, 6 July 2023 (UTC)
{{ proxycheckstatus}}
Reason: Cloud proxy/VPN server. 2601:1C0:4401:F60:CC1B:7FBB:65E7:4373 ( talk) 18:00, 8 August 2023 (UTC)
{{ proxycheckstatus}}
Reason: Belongs to "HostRush" VPN services. Disruption from 207.231.105.153 ( talk · contribs · WHOIS). See WHOIS for /21 range confirmation. 2601:1C0:4401:F60:B09F:5E03:B2DE:5C0F ( talk) 17:55, 12 August 2023 (UTC)
{{ proxycheckstatus}}
Reason: Although not a proxy, this IP is from a web hosting provider. This IP is allocated to the Veselí nad Lužnicí town government. Looking at the IP's global contributions, it appears it this IP has been blocked on the German Wikipedia [1].
Update #1: Added another IP that might from the same web hosting provider. Apparently, this IP was blocked on the Spanish Wikipedia for being a proxy.
SpinnerLaserzthe2nd ( talk) 20:07, 19 August 2023 (UTC)
{{ proxycheckstatus}}
OVH, several proxies and VPNs. MarioGom ( talk) 08:59, 27 August 2023 (UTC)
{{ proxycheckstatus}}
Reason: Webhost. 2601:601:51C:A47:E530:E9E5:B590:2100 ( talk) 15:17, 8 September 2023 (UTC)
{{ proxycheckstatus}}
Reason: Webhost/VPN. 2601:601:51C:2D16:612F:DB7E:1100:4008 ( talk) 04:42, 9 September 2023 (UTC)
{{ proxycheckstatus}}
Reason: Cloud/VPN server. 2601:601:51C:D94:6487:982:C0FF:2E5D ( talk) 19:46, 10 September 2023 (UTC)
{{ proxycheckstatus}}
Reason: Despite the recent block in French Wikipedia due to remove sources on the Angolan Civil War article, the proxy IP had started various sources in Wikipedias of other languages. SpinnerLaserzthe2nd ( talk) 14:29, 6 November 2023 (UTC)
{{ proxycheckstatus}}
Reason: The IP is hosted on Acehost. See also the edit summary on this diff. -- Leonidlednev ( T, C, L) 05:45, 4 August 2023 (UTC)
{{ proxycheckstatus}}
Reason: Webhost IP range recently used for disruption. 2601:1C0:4401:F60:D587:449F:646D:BACC ( talk) 17:59, 18 August 2023 (UTC)
{{ proxycheckstatus}}
Reason: Repeating blocked IP edits via use of VPN; see edit history of Hispanics and Latinos in Los Angeles. Jalen Folf (talk) 01:27, 12 October 2023 (UTC)
{{ proxycheckstatus}}
Reason: This IP has been detected as a proxy IP ( https://www.ipqualityscore.com/free-ip-lookup-proxy-vpn-test/lookup/89.119.251.40). According to CleanTalk, this IP is reported as a spam IP that also committed brute force attacks. SpinnerLaserzthe2nd ( talk) 20:24, 26 October 2023 (UTC)
{{ proxycheckstatus}}
Reason: Webhost. 73.67.145.30 ( talk) 18:12, 25 May 2023 (UTC)
{{ proxycheckstatus}}
Reason: Webhost/VPN range. 2601:1C0:4401:F60:592C:6755:67BE:F9D9 ( talk) 20:27, 26 August 2023 (UTC)
{{ proxycheckstatus}}
Webhost/VPN Seawolf35 ( talk) 16:20, 28 September 2023 (UTC)
{{ proxycheckstatus}}
Reason: This is likely to be block-evasion from Belteshazzar who has been globally banned by the WMF [2]. From a search I did, the IP is listed as an open proxy. Psychologist Guy ( talk) 20:30, 8 October 2023 (UTC)
{{ proxycheckstatus}}
Reason: Open proxy per block on Commons, see their blocking log. -- LemonSlushie 🍋 ( talk) ( edits) 07:01, 25 October 2023 (UTC)
{{ proxycheckstatus}}
Reason: Undoing categorization work which was done after an informal discussion and is now in my talk page demanding an explaination. Omnis Scientia ( talk) 21:44, 7 December 2023 (UTC)
{{ proxycheckstatus}}
Reason: Disruption, possibly a VPN server. 2601:1C0:4401:F60:817:B3DA:A0F9:1195 ( talk) 20:01, 19 August 2023 (UTC)
{{ proxycheckstatus}}
Reason: VPN server. Previously blocked. 2601:1C0:4401:F60:7C72:5877:80EB:F896 ( talk) 19:31, 14 August 2023 (UTC)
{{ proxycheckstatus}}
Reason: VPN server/datacenter IP. Vandalism, see edit filter log. 2601:1C0:4401:F60:B09F:5E03:B2DE:5C0F ( talk) 17:49, 12 August 2023 (UTC)
{{ proxycheckstatus}}
Pro forma. — Mdaniels5757 ( talk • contribs) 21:37, 17 December 2023 (UTC)
{{ proxycheckstatus}}
Reason: disruptive edits, multiple blocks over the years, including proxy block. Nobody ( talk) 14:12, 3 January 2024 (UTC)
{{ proxycheckstatus}}
Reason: This IP came up on UTRS. Blocked both globally and locally, but from my checks it seems like it isn't a proxy any longer. DatGuy Talk Contribs 19:31, 1 January 2024 (UTC)
{{ proxycheckstatus}}
Reason: Listed as proxy at IPQualityScore. The whole range 103.127.216.1-103.127.219.254 belongs to the same provider. Siawase ( talk) 10:32, 3 January 2024 (UTC)
{{ proxycheckstatus}}
Reason: Listed as a VPN server. 2601:5CC:8300:A7F0:7186:1FB7:1CA:90A5 ( talk) 23:39, 16 January 2024 (UTC)
{{ proxycheckstatus}}
Reason: Spur reports "belongs to a call-back proxy network". See Talk:Catalent#Undisclosed paid edits and recurring attempts by IPs to add unreferenced financial info to the article, and now this IP is doing same.
See WP:WikiProject on open proxies/Requests/Archives/46#175.158.155.92/Requests/Archives/46#175.158.155.92 for MarioGom's findings on proxy IP(s) at the same article in 2022. ☆ Bri ( talk) 18:29, 19 January 2024 (UTC)
{{ proxycheckstatus}}
Reason: Webhost/VPN. 73.67.145.30 ( talk) 16:23, 17 May 2023 (UTC)
{{ proxycheckstatus}}
Individual IP's in these two ranges, 14.231.169.16 and 113.177.23.65, have already been blocked as proxies on the Swedish and Russian Wikipedias respectively. Both blocked IP's were used on those projects by User:Phạm Văn Rạng to evade their global lock. They look to be using a larger portion of these IP ranges for evasion on this project as well. I've already applied some range blocks to deal with the evasion, but some insight into what's going on technically would be appreciated. Courtesy pinging @ Riggwelter: and @ Q-bit array: who applied to blocks on the other projects, in case you want to weigh in here. Sir Sputnik ( talk) 17:19, 30 July 2023 (UTC)
{{ proxycheckstatus}}
Reason: Identified as VPN server by WHOIS. Spur reports "belongs to a call-back proxy network". IP hopping/proxy use at beauty pageant pages strongly suggests nefarious editing, there are many sockfarms active at the same pages these are editing. IPs are listed roughly from most recent to least. ☆ Bri ( talk) 04:16, 18 January 2024 (UTC)
{{ proxycheckstatus}}
Reason: IncogNet LLC. Listed as VPN by WP:IP Info feature. Someone who's wrong on the internet ( talk) 06:02, 18 January 2024 (UTC)
{{ proxycheckstatus}}
Reason: Proxy IP check by Proxy API Checker SpinnerLaserzthe2nd ( talk) 00:10, 21 January 2024 (UTC)
{{ proxycheckstatus}}
Reason: IP made some unconstructive edits today and in the past. Nobody ( talk) 14:41, 15 February 2024 (UTC)
{{ proxycheckstatus}}
Used by known proxy-hopping LTA. See Wikipedia:Sockpuppet investigations/Blue Barette Bam. Someone who's wrong on the internet ( talk) 23:45, 24 January 2024 (UTC)
{{ proxycheckstatus}}
Reason: The range seems to be announced by IPXO (per Hurricane Electric), an "IP marketplace" according to their website. All IPs in the range who have made contributions since 1 January 2023 are active on ExpressVPN, as well as a handful of varying residential proxies according to Spur. I've not done a fully exhaustive check on the range yet, but the only IPs I've seen not flagged as ExpressVPN on the Spur data are .251-.255, though they are still listed as data centre IPs.
It may also be worth the other /24s listed on HE as being announced by IPXO as well for any that haven't yet been blocked (some have) but probably should be. Sideswipe9th ( talk) 20:56, 4 February 2023 (UTC)
{{ proxycheckstatus}}
Reason: VPN server. 73.67.145.30 ( talk) 18:38, 17 April 2023 (UTC)
{{ proxycheckstatus}}
Reason: VPN network/Webhosting service. 73.67.145.30 ( talk) 08:05, 1 May 2023 (UTC)
{{ proxycheckstatus}}
Reason: Requested unblock. I'm unable to edit wikipedia pages from this IP (our office) even when logged in. The IP is statically allocated to us (since Feb 2022), we're not running any proxy and I'm not seeing any unusual open ports or suspicious network activity. xmath ( talk) 19:30, 30 June 2023 (UTC)
Update: never mind, the block isn't for our IP specifically, apparently the entire IP range has been mistakenly classified as webhosting instead of FTTH/FTTB. xmath ( talk) 20:59, 30 June 2023 (UTC)
{{ proxycheckstatus}}
Reason: Made an unsourced BLP edit. SPUR shows possible call-back proxy. Nobody ( talk) 12:38, 1 March 2024 (UTC)
{{ proxycheckstatus}}
Reason: Colocation webhost. Looking at the WHOIS info, it appears to belong to Hetzner, a provider of cloud servers, dedicated servers, colocation and web hosting, according to their website. Looking at the block log of this IP, it was blocked in February 2022 for two years as a colocation webhost before. Reason why I'm reporting is because soon after the expiration of that 2 year block, some user at least seems to be using it to vandalise various music-related articles; see Wikipedia:Administrators' noticeboard/Incidents#Need a rangeblock for Oregon IPs for more insight on this. This is an example of their vandalism, where they're introducing incorrect information into the article, with no explanation, sources, etc. There are so many recent edits like these from this range. — AP 499D25 (talk) 13:32, 4 March 2024 (UTC)