Steward requests/Global

This is an archived version of this page, as edited by JarBot (talk | contribs) at 21:01, 13 March 2019 (Bot: archiving 6 request to Steward requests/Global/2019-03). It may differ significantly from the current version.

Latest comment: 6 years ago by Ruslik0 in topic Requests for global (un)lock and (un)hiding
Shortcut:
SRG
This page hosts requests for global (un)blocks, (un)locks and hidings.

If you are here because you have been affected by a global block, please see Global blocks/FAQ for more information about global block and routes to appeal.

Note: (un)blocks apply to IP addresses or accounts; and (un)locks apply to global accounts.

Cross-wiki requests
Meta-Wiki requests


Requests for global (un)block

  Please be sure to follow the instructions below:
Your request might be rejected if you don't follow the instructions.
Please also review Global blocking .
Global blocks don't affect Meta-Wiki, so if your IP address or account is blocked, you can still appeal here. IP addresses or accounts that cause disruption on Meta should be reported at Meta:Requests for help from a sysop or bureaucrat instead of here so that they can be blocked locally.
Please describe the kind of cross wiki abusive activity you see from the IP or account. Saying an IP or account is a long term abuser is not helpful, but saying "IP vandalizes at ban.wikipedia, no.wikipedia and vi.wikipedia" is. This is especially important for range blocks. If you do not provide enough details, your request might be declined.
Instructions for making a request

Before requesting, make sure that:

  1. You know the IP address(es) or accounts you wish to have globally blocked or unblocked.
  2. For blocks, the global blocking criteria are met.
  3. For unblocks, your request addresses the original reason for blocking the IP or account, if any.

To make a request for the address(es) or account(s) to be blocked or unblocked

Copy the template below to the bottom of this section and explain why the address(es) or account(s) should be blocked/unblocked.
=== Global block/unblock for [[Special:Contributions/Some IP address or account|Some IP address or account]] ===
{{Status}} <!-- Do not remove this template -->
* {{Luxotool|IP address/username}}
Description, evidence, diffs, etc. --~~~~
When requesting that your IP be unblocked, note that stewards need to know your IP address to even consider a request.
To find your IP, please visit https://www.whatismyip.com/
You are not required to disclose your IP in public - you may make requests privately to any steward on IRC or by email at: stewards wikimedia org

Global unblock for 46.183.103.0/27

Status:    In progress

This range covers the two Proxies for the Deutsche Bahn, 46.183.103.8 xwiki-contribsxwiki-date (alt)STIP infoWHOISrobtexgblockglistabuselogbullseye and 46.183.103.17 xwiki-contribsxwiki-date (alt)STIP infoWHOISrobtexgblockglistabuselogbullseye, no other IPs are currently in use. There is astonishingly little vandalism from these two IPs, so I whitelisted them on de.wp, which is by far the most affected wiki here, we can live with 6 account creations a day. I would recommend unblocking the IPs globally. --Harald Krichel (talk) 06:27, 24 January 2019 (UTC)Reply

@Ruslik0: any objections to removing this? I see there has been some abuse from the range, but there is also a good amount of legitimate activity. – Ajraddatz (talk) 17:43, 7 February 2019 (UTC)Reply
Does Avoided have some relation to Deutsche Bahn? Ruslik (talk) 18:30, 7 February 2019 (UTC)Reply
One of around 4.4 billion passengers each year... maybe --DaizY (talk) 19:59, 18 February 2019 (UTC)Reply

Global block for Open Proxies

Status:    In progress
List

FilterBypass.me:
206.190.152.176 xwiki-contribsxwiki-date (alt)STIP infoWHOISrobtexgblockglistabuselogbullseye
Proxysite.me:
167.114.11.52 xwiki-contribsxwiki-date (alt)STIP infoWHOISrobtexgblockglistabuselogbullseye
68.235.60.203 xwiki-contribsxwiki-date (alt)STIP infoWHOISrobtexgblockglistabuselogbullseye
217.182.175.75 xwiki-contribsxwiki-date (alt)STIP infoWHOISrobtexgblockglistabuselogbullseye
217.182.175.63 xwiki-contribsxwiki-date (alt)STIP infoWHOISrobtexgblockglistabuselogbullseye
217.182.175.74 xwiki-contribsxwiki-date (alt)STIP infoWHOISrobtexgblockglistabuselogbullseye
217.182.175.122 xwiki-contribsxwiki-date (alt)STIP infoWHOISrobtexgblockglistabuselogbullseye
NewIPnow .com:
51.255.78.5 xwiki-contribsxwiki-date (alt)STIP infoWHOISrobtexgblockglistabuselogbullseye
199.193.248.248 xwiki-contribsxwiki-date (alt)STIP infoWHOISrobtexgblockglistabuselogbullseye
163.172.106.89 xwiki-contribsxwiki-date (alt)STIP infoWHOISrobtexgblockglistabuselogbullseye
Genmirror.com:
163.172.111.240 xwiki-contribsxwiki-date (alt)STIP infoWHOISrobtexgblockglistabuselogbullseye
panproxy.com
163.172.255.95 xwiki-contribsxwiki-date (alt)STIP infoWHOISrobtexgblockglistabuselogbullseye
spanproxy.com:
163.172.255.95 xwiki-contribsxwiki-date (alt)STIP infoWHOISrobtexgblockglistabuselogbullseye
atozproxy.com:
163.172.255.91 xwiki-contribsxwiki-date (alt)STIP infoWHOISrobtexgblockglistabuselogbullseye
unblockweb.co:
5.39.216.243 xwiki-contribsxwiki-date (alt)STIP infoWHOISrobtexgblockglistabuselogbullseye
proxysite.club:
173.212.247.109 xwiki-contribsxwiki-date (alt)STIP infoWHOISrobtexgblockglistabuselogbullseye--WikiBayer (talk) 22:47, 26 January 2019 (UTC)Reply

Thunder VPN
107.167.106.130 xwiki-contribsxwiki-date (alt)STIP infoWHOISrobtexgblockglistabuselogbullseye
107.167.108.234 xwiki-contribsxwiki-date (alt)STIP infoWHOISrobtexgblockglistabuselogbullseye
Hola VPN
46.99.36.3 xwiki-contribsxwiki-date (alt)STIP infoWHOISrobtexgblockglistabuselogbullseye
197.207.150.43 xwiki-contribsxwiki-date (alt)STIP infoWHOISrobtexgblockglistabuselogbullseye
172.84.200.21 xwiki-contribsxwiki-date (alt)STIP infoWHOISrobtexgblockglistabuselogbullseye
103.110.53.244 xwiki-contribsxwiki-date (alt)STIP infoWHOISrobtexgblockglistabuselogbullseye
154.127.244.130 xwiki-contribsxwiki-date (alt)STIP infoWHOISrobtexgblockglistabuselogbullseye
158.181.43.118 xwiki-contribsxwiki-date (alt)STIP infoWHOISrobtexgblockglistabuselogbullseye
41.189.245.225 xwiki-contribsxwiki-date (alt)STIP infoWHOISrobtexgblockglistabuselogbullseye
154.127.142.83 xwiki-contribsxwiki-date (alt)STIP infoWHOISrobtexgblockglistabuselogbullseye
76.76.179.175 xwiki-contribsxwiki-date (alt)STIP infoWHOISrobtexgblockglistabuselogbullseye
202.65.49.134 xwiki-contribsxwiki-date (alt)STIP infoWHOISrobtexgblockglistabuselogbullseye
193.182.144.63 xwiki-contribsxwiki-date (alt)STIP infoWHOISrobtexgblockglistabuselogbullseye
220.158.236.141 xwiki-contribsxwiki-date (alt)STIP infoWHOISrobtexgblockglistabuselogbullseye

--WikiBayer (talk) 19:08, 3 February 2019 (UTC)Reply

Global block for possible open proxies

Status:    In progress
List

This guy is a real stubborn fellow.

Not sure at this point if subranges containing these IPs need to be blocked, or just the individual IPs themselves.

Pinging tawiki admins @Info-farmer, Balajijagadesh, Shanmugamp7, Mdmahir, and Ravidreams: who can help get rid of this Kannadiga's pages. Mahir256 (talk) 00:30, 11 February 2019 (UTC)Reply

Global Block for 2001:b400:e2af:7599:5883:533c:58f5:52eb/50 (Nipponese Dog Calvero (KAGE) used)

Status:    In progress

--MCC214#ex umbra in solem 10:06, 12 February 2019 (UTC)Reply

Global block for 208.114.128.0/18 (Xplornet Communications Inc.) for LTA

Status:    In progress

First discovered on SimpleWiki, these IP addresses vandalize for years on many wikis (simple, en, es, fr for example). They are rife especially in pages difficult to control, color pages for example (w:simple:List of colors, w:fr:Liste de noms de couleur or w:es:Anexo:Colores and as well as all internal links contained therein). For this difficulty, it is necessary to block this IP range indefinitely. (Woodstock, New-Brunswick, Canada, Stalk toy: locally blocked 6 times). Thank you in advance. Wikipedially. --Eihel (talk) 01:57, 16 February 2019 (UTC)Reply

Since my first request, IPs have still vandalized here. That will make you, maybe, to do this lock. --Eihel (talk) 11:47, 22 February 2019 (UTC)Reply

Global block for open proxies

Status:    In progress

Used for spamming, all tripped spam filters at simplewikt. --Hiàn (talk) 23:13, 16 February 2019 (UTC)Reply

Global block for 94.236.128.0/20 for LTA

Status:    In progress

Cross-wiki vandalism with false informations. Number of awesome local blockings (see Stalk Toy). Vandalisms since January 26, 2019: here. Thank you in advance. --Eihel (talk) 15:32, 17 February 2019 (UTC)Reply

Global block for 151.20.7.153

Status:    In progress

Block evasion by user Alec Smithson xwiki-contribsxwiki-date (Smithson alt)CAgblockglistabuselog.

The IP is blocked on WP:EN and I've blocked it on WP:FR but the user is still active on several WMF projects, including Commons. Can you block for a 6 months (or more). Thanks. -- Habertix (talk) 22:57, 25 February 2019 (UTC)Reply

What is disruptive about the actions taken on other projects; i.e. azwiki? Looks like they just added some images to a gallery. Are those the wrong images? – Ajraddatz (talk) 01:22, 26 February 2019 (UTC)Reply

Global block for 113.249.0.0/16

Status:    In progress

guc) on at least enwiki for block evasion of 219.153.0.0/16 (talkcontribsinfoWHOISguc) and it seems to focus around en:Robert David Hall among other targets. Earlier this week 113.249.63.135 (talkcontribsinfoWHOISguc) started disruptively editing on simple by disruptively creating and further blanking simple:Robert David Hall and including BLP violations. They continued vandalism on 18 different projects by blanking articles and creating nonsense talk pages. I looked at the range in xwiki contribs and I can't find a single false positive for 2018 or 2019 where they weren't disruptively editing under 113.249.0.0/16 - I also find it strange that there are few edits in this range from 2013-18 then it suddenly becomes heavily used for vandalism, so I'm requesting a global range block to prevent further disruption. --Praxidicae (talk) 15:43, 27 February 2019 (UTC)Reply

Also appears to be some significant abuse from 123.147.0.0/16 (talkcontribsinfoWHOIS

guc) Praxidicae (talk) 15:48, 27 February 2019 (UTC)Reply

Did a prefix search and recent vandalism are from the range 113.249.56.0 to 113.249.63.255, i.e.:
I came across this range as well as the previous 219.153.x.x several times during the past few days. They basically make a vandalism edit, then undo the edit. -★- PlyrStar93 Message me. 15:55, 27 February 2019 (UTC)Reply
They are back at it again today. Praxidicae (talk) 12:26, 1 March 2019 (UTC)Reply

Global block for Proxy vandal 2606:2E00:8003:12:216:3EFF:FED6:D880

Status:    In progress

Here andhere --WikiBayer 👤💬 19:08, 7 March 2019 (UTC)Reply

Status:    In progress

Global block for 34.73.124.65

Status:    In progress

Functional proxy, port 3128. OJJ (talk) 09:57, 10 March 2019 (UTC)Reply

Global block for 99.203.2.2

Status:    In progress

w:en:WP:LTA/DENVER perp. Check geolocate and cross-wiki edits. --IanDBeacon (talk) 16:38, 13 March 2019 (UTC)Reply

Requests for global (un)lock and (un)hiding

  Be sure to follow the instructions below:
  • Your request might be rejected if it doesn't include the necessary information.
  • Warning! This page is publicly viewable. If the account name is grossly insulting or contains personal information please contact a steward privately in #wikimedia-stewardsconnect or email your request to the stewards VRT queue at stewards-oversight wikimedia org (direct wiki interface) but do not post it here. Thanks.
  • Warning! This is not the place to ask for locks based on your opinion that someone is disruptive. Global locks are used exclusively against vandalism and spam, not because of content disputes, not because you think that someone deserves to be globally blocked. In such cases, you should ask for local blocks at appropriate places.
  • If you are globally locked, you should appeal your lock to stewards-appeals wikimedia org.
Please describe abusive activity of an account before reporting them here. Since stewards are often not active at projects the reported accounts are, things that seem obvious to you may not be equally obvious to the reviewing steward.
Instructions for making a request

Before requesting that a global account be (un)locked, please be sure that:

  1. You have evidence of cross-wiki disruption from the account(s).
  2. You can show that it is not feasible to use local-only blocks or other measures like page protection to combat the disruption.
  3. You have considered making the request in #wikimedia-stewardsconnect, especially for account names which will be hidden, or for urgent requests.
To make a request for an account to be locked or unlocked
Copy one of the codes below to the bottom of this section and explain why the account(s) should be locked/unlocked.
=== Global lock/unlock for Foo ===
{{status}} <!-- do not remove this template -->
* {{LockHide|username}}
* {{LockHide|username|hidename=1}} <!-- if you do not want the name to be visible on this page -->
*...
Reasons, etc. --~~~~

For many accounts:

=== Global lock for spambots/vandals ===
{{status}} <!-- do not remove this template -->
{{MultiLock|username|username2|username3}}
{{MultiLock|username|username2|username3|hidename=1}} <!-- if you do not want the names to be visible on this page -->
*...
Reasons, etc, --~~~~

Global lock for Grazeymir

Status:    Done

--Tomybrz Bip Bip 21:45, 12 March 2019 (UTC)Reply

  Done Ruslik (talk) 20:29, 13 March 2019 (UTC)Reply

Global lock for Spambots

Status:    Done

Lock allGlobal block all:

Obvious spambots. Several of these accounts are also spamming cross-wiki. Some of them are advertising drugs. LightandDark2000 🌀 (talk) 13:53, 13 March 2019 (UTC)Reply

  Done Ruslik (talk) 20:39, 13 March 2019 (UTC)Reply

Global lock for 影武者(Nipponese Dog Calvero)

Status:    Done

--Lanwi1(talk) 15:48, 13 March 2019 (UTC)Reply

Done. Stryn (talk) 16:41, 13 March 2019 (UTC)Reply

Global lock username hidden

Status:    Done

Inapropriate username --Tomybrz Bip Bip 20:12, 13 March 2019 (UTC)Reply

  DoneDefender (talk) 20:35, 13 March 2019 (UTC)Reply

See also