Wikipedia:WikiProject on open proxies/Requests

165.85.64.0/22

edit

  – A proxy checker has requested a second opinion on this case.

Reason: Amazon AWB. 165.85.64.0 - 165.85.66.255 are all registered to Amazon AWB, hence the /22 range in this report. BLP disruption caught by filter log. 73.67.145.30 (talk) 16:45, 28 April 2023 (UTC)[reply]

209.35.227.0/24

edit

  – A proxy checker has requested a second opinion on this case.

Reason: VPN. Perimeter 81. 73.67.145.30 (talk) 18:43, 15 May 2023 (UTC)[reply]

  •   Confirmed While the range is announced by Perimeter 81, and a large portion of it seems to be empty per Spur and Shodan, there are IP ranges within that are active on Perimeter 81's VPN product. However that product is aimed at businesses, with pricing to match. This seems similar to the Zscaler, McAfee WGCS cases that are also open at present. A softblock on the range might be appropriate however, the one contributor who was active on 15 May 2023 was using an IP that's part of their VPN range. While I've tried to pin down the exact range for just the IPs that are part of their VPN offering, it seems somewhat spread out throughout it with gaps, so it might be more expedient to just block it in its entirety. Flagging this for a 2O though, while we figure out how to handle this particular type of VPN provider. Sideswipe9th (talk) 00:22, 19 July 2023 (UTC)[reply]

103.23.206.0/23

edit

  A user has requested a proxy check. A proxy checker will shortly look into the case.

103.23.206.0/23 · contribs · block · log · stalk · Robtex · whois · Google

Reason: Requested unblock or softening. Non-proxy collateral on this range. - RichT|C|E-Mail 01:23, 15 November 2024 (UTC)[reply]

@Rich Smith. Have you discussed this with the blocking admin ST47? Malcolmxl5 (talk) 22:07, 19 November 2024 (UTC)[reply]
@Malcolmxl5: I have not, my last attempt at asking ST47 about a block, albeit by their bot, was left unanswered - RichT|C|E-Mail 15:43, 21 November 2024 (UTC)[reply]
@Rich Smith. I understand. ST47 hasn’t edited for a while so let’s have a look at this. Malcolmxl5 (talk) 12:34, 29 November 2024 (UTC)[reply]

Iranian rangehopper

edit

  A user has requested a proxy check. A proxy checker will shortly look into the case.

Reason: Dubious edits, dubious geolocation. SPA rangehopping, at the least, but smells proxy-ish to me. ☆ Bri (talk) 04:18, 19 November 2024 (UTC)[reply]

Nigeria IP rangehopper

edit

  A user has requested a proxy check. A proxy checker will shortly look into the case.

Reason: Recent edits has been violating MOS:ROLEBIO and showing WP:IDHT by reverting after informed on ROLEBIO. In which, being curious on why the ever-changing IP from various ranges in which making warning to level 4 impossible in turn making AIV reporting impossible, I did a fuzzy check on the IPs location, it's changing between Kano and Lagos in Nigeria hence I suspect that there's likely VPN or proxy involved. Paper9oll (🔔📝) 14:47, 23 November 2024 (UTC)[reply]

Single-purpose IP & edit warrior

edit

  A user has requested a proxy check. A proxy checker will shortly look into the case.

Reason: single-purpose accounts apparently closely linked to Jüri Lina. In Spanish Wikipedia an IP (actually blocked) seems to be located in Sweden, where the author lives. Here, in Wikipedia in English, it seems to be using open proxies. Edits are disruptive, biased and spamming (in eswiki the IP tries to promote the author's books). It is edit-warring, in eswiki as well as in enwiki. A block will prevent further damage to revision history. I add a second IP apparently connected with this one, single-purpose account, too. Thanks! PedroAcero76 (talk) 17:41, 28 November 2024 (UTC)[reply]

Could you give me eswiki page(s) where an IP tried to promote the author's books (would be fun if true)? If possible I also want to know what you think was biased in my edits (I do not plan to do these any more becuase it seems that IP addresses have no rights; it is your train of thought that is in my interest). 2404:F780:5:DEB:0:0:0:D001 (talk) 01:34, 29 November 2024 (UTC)[reply]

IPVanish ranges

edit

  A user has requested a proxy check. A proxy checker will shortly look into the case.

Reason: VPN range used by IPVanish. Klinetalkcontribs 01:31, 30 November 2024 (UTC)[reply]

103.67.199.99

edit

  – This proxy check request is closed and will soon be archived by a bot.

Reason: User has repeatedly used open proxies to make same edit to IMDb Meters (talk) 03:54, 30 November 2024 (UTC)[reply]