 | This page has an administrative backlog that requires the attention of willing administrators. Please replace this notice with ((no admin backlog)) when the backlog is cleared. |
 | Looking to make a new report? You're in the wrong place! Please go to Wikipedia:WikiProject on open proxies#Reporting and fill in the relevant box. |
| Index |
|
This page has archives. Sections older than Expression error: Unrecognized punctuation character ",". days may be automatically archived by ClueBot III when more than 5 sections are present. |
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)
- I've checked the three /24s separately here (165.85.64.0/24 · contribs · block · log · stalk · Robtex · whois · Google - 165.85.65.0/24 · contribs · block · log · stalk · Robtex · whois · Google - 165.85.66.0/24 · contribs · block · log · stalk · Robtex · whois · Google). While the ISP is Amazon, all three ranges are currently allocated to Palo Alto Networks. The first range, 165.85.64.0/24, appears to be used for part of their GlobalProtect VPN service per Spur's data. This seems similar to the McAfee WGCS and Zscaler ranges currently reported on this page, and any hardblock on these ranges would have some collateral on legitimate users. A softblock/((Colocationwebhost-soft)) might be appropriate here. The other two ranges in the /22 seem to be in the same data centre, and don't seem to be part of the same service, but the filter log linked above is from an IP on the third /24 so it clearly has some use somewhere. Not sure what to recommend here, and I've not been able to easily search to see if any other IPs in the range have triggered any filters, though none have any recorded contributions. Sideswipe9th (talk) 18:17, 17 July 2023 (UTC)
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)
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)
46.102.156.0/24 and 94.177.9.0/24[edit]
– A proxy checker has requested administrator assistance for action regarding the case below. The requested action is below.
- 46.102.156.0/24 · contribs · block · log · stalk · Robtex · whois · Google
- 94.177.9.0/24 · contribs · block · log · stalk · Robtex · whois · Google
https://www.alwyzon.com/en
Reason: Both ranges belong to Hohl IT e.U. aka (Alwyzon) which is an Austrian provider of dedicated servers. Matthew Tyler-Harrington (aka mth8412) (talk) 03:45, 22 June 2023 (UTC)
- Confirmed as to the ranges with "Customers" in the name (/26), but I didn't check them all. This might also be a job for the ASNbot (AS40994) @AntiCompositeNumber: — Mdaniels5757 (talk • contribs) 00:36, 8 December 2023 (UTC)
- I’ve blocked the two /26. Malcolmxl5 (talk) 13:15, 23 March 2024 (UTC)
157.167.128.0/24[edit]
A user has requested a proxy check. A proxy checker will shortly look into the case.
Reason: Cloud server/VPN. This is an odd one, because the IP range geolocates to Turkey, and is listed as a VPN network; but most of the edits are to Turkish-related articles. Is this some sort of corporate cloud network? 2601:1C0:4401:F60:8C11:4CC3:7E71:B4CE (talk) 20:54, 13 August 2023 (UTC)
- My reading is that this is a user or users in Turkey editing via a connection belonging to an enterprise, perhaps a business or a public body, that subscribes to cybersecurity services offered by Forcepoint. It looks to me like a corporate proxy. The contributions suggest a stable connection with largely unproblematic edits and I would not be inclined to take any action at this time. Malcolmxl5 (talk) 02:05, 20 January 2024 (UTC)
5.42.72.0/21[edit]
– A proxy checker has requested administrator assistance for action regarding the case below. The requested action is below.
Reason: IP range belongs to webhosting/VPN service. 2601:1C0:4401:F60:817:B3DA:A0F9:1195 (talk) 18:34, 20 August 2023 (UTC)
- Confirmed along with most things in [1]. Perhaps User:AntiCompositeNumber could add this (ASN 210644) to User:AntiCompositeBot/ASNBlock? — Mdaniels5757 (talk • contribs) 00:28, 8 December 2023 (UTC)
- All the /24 in the /21 are currently globally blocked. I’ve added a local block for the /21. Malcolmxl5 (talk) 12:57, 23 March 2024 (UTC)
202.134.9.141[edit]
A user has requested a proxy check. A proxy checker will shortly look into the case.
- 202.134.9.141 · talk · contribs · block · log · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan
Reason: Same proxy sock that got blocked earlier for both ban evasion and editing with proxy. [2] He is still socking to restore the same article.[3][4] Ratnahastin (talk) 15:22, 8 March 2024 (UTC)
- There’s a lot of blocks in the history, the most recent is a 3 month /12 block in September for block evasion. Malcolmxl5 (talk) 11:06, 13 March 2024 (UTC)