Steward requests/Global

This page hosts requests for global (un)blocks, (un)locks and hidings.

For global IP block requests, read the guideline and make a request below under Requests for global (un)block. Indicate why a global block is necessary and for how long.
For account lock requests, read the guideline and post under Requests for global (un)lock and (un)hiding.
For local requests here on Meta, see Meta:Requests for help from a sysop or bureaucrat.

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; and (un)locks apply to global accounts.

Cross-wiki requests
CheckUser information Global blocks/locks Permissions (global) Permissions (bot) Permissions (other) Username changes/ usurpation requests Miscellaneous requests URL blacklisting Title/username blacklisting Email blacklisting
Meta-Wiki requests
CheckUser information Deletion Permissions Requests for help

Requests for global (un)block

Latest comment: 40 minutes ago29 comments10 people in discussion

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. Only IP addresses can be globally blocked at this moment. Please see #Requests for global (un)lock and (un)hiding if your request involves an account.

Global blocks don't affect Meta-Wiki, so if your IP address is blocked, you can still appeal here. IP addresses 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. Saying an IP 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:

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

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

Copy the template below to the bottom of this section and explain why the address(es) should be blocked/unblocked.

=== Global block/unblock for [[Special:Contributions/Some IP address|Some IP address]] ===
{{Status}} <!-- Do not remove this template -->
* {{Luxotool|IP address}}
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: stewardswikimediaorg

Global block/unblock for 62.214.191.67

Status: On hold

62.214.191.67 xwiki-contribs • xwiki-date ^(alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye

VPN/Proxy used in Tor, Windscribe and Tunnelbear, 361 users, according to IP-information tool. --Keneris ^☎ 17:38, 20 May 2024 (UTC)Reply

I'm not seeing anything indicating that this is a proxy, at least not in the proxy checkers I'm using. As such I'm guessing this is a P2P, but note that we do not block those for being proxies. I'll wait to see if Amanda or another steward more skilled in the area might prove me wrong, but otherwise I'm closing this in some time. EPIC (talk) 17:46, 20 May 2024 (UTC)Reply

Like I said, the IP-information tool on my home wiki (uk:Спеціальна:Внесок/62.214.191.67) gave out this bunch of VPN services and a staggering number of editors. As you can see from the history of edits, it is engaged in vandalism. --Keneris ^☎ 17:56, 20 May 2024 (UTC)Reply

Thanks for the clarification. Well, that was the reason I intended to leave this open, to see if another steward more skilled in this area could find something that I didn't find. EPIC (talk) 17:58, 20 May 2024 (UTC)Reply

The IP belongs to some public wifi provided by de:IT-Dienstleistungszentrum Berlin, that's why the number of users is high. If there is vandalism, the IP should be locally blocked for a couple of days, but I don't think a global block is in order. Johannnes89 (talk) 05:13, 21 May 2024 (UTC)Reply

Global block for 170.55.10.178

Status: In progress

170.55.10.178 xwiki-contribs • xwiki-date ^(alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye

Open proxy or zombie. Lemonaka (talk) 14:50, 21 May 2024 (UTC)Reply

Hmm, none of the proxy checkers I'm using are giving positive here [1] and I'm not finding anything else indicating proxy here, so in other words, this is probably not or no longer an open proxy. EPIC (talk) 14:54, 21 May 2024 (UTC)Reply

Global block for 180.242.68.0/22

Status: Withdrawn

180.242.68.0/22 xwiki-contribs • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye

Long-term abuse. Cross-wiki abuse. He start to vandalise again XReport --Fazily • 📩 10:26, 22 May 2024 (UTC)Reply

Note: This range is already blocked at enwiki. Fazily • 📩 10:27, 22 May 2024 (UTC)Reply

Hmm, I'm still only seeing vandalism from one IP, and that is 180.242.69.12 from some hours ago. Is there something else I am not seeing here? EPIC (talk) 10:28, 22 May 2024 (UTC)Reply

116.206.28.41, please see. Fazily • 📩 10:31, 22 May 2024 (UTC)Reply

But that IP is on a different range though? Since this vandal just seems to be jumping between different ranges I went ahead and protected the page in question. EPIC (talk) 10:35, 22 May 2024 (UTC)Reply

Well, okay. Mark this report as not done then. ;) Fazily • 📩 10:36, 22 May 2024 (UTC)Reply

OK then, no problem, marking as withdrawn. EPIC (talk) 10:37, 22 May 2024 (UTC)Reply

Global block for 185.100.159.209

Status: Done

185.100.159.209 xwiki-contribs • xwiki-date ^(alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye

Spam / spambot. Open proxy. XXBlackburnXx (talk) 12:02, 22 May 2024 (UTC)Reply

Done EPIC (talk) 12:04, 22 May 2024 (UTC)Reply

Global block for 89.212.87.157

Status: Not done

89.212.87.157 xwiki-contribs • xwiki-date ^(alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye

Vandalizing pages. Ternera (talk) 13:27, 22 May 2024 (UTC)Reply

This looks like regular one wiki vandalism, can slwiki admins take care of this perhaps? @A09: FYI, if you feel a block is of use. EPIC (talk) 13:29, 22 May 2024 (UTC)Reply

Sorry, I thought Twinkle would report this to the slwiki admins, not globally. Ternera (talk) 13:32, 22 May 2024 (UTC)Reply

No problem. TwinkleGlobal doesn't have the ability to report to local administrators' noticeboards, but only to SRG (and GSR if it is a GS wiki, which slwiki is not), unless there is a local version of Twinkle that has that ability. EPIC (talk) 13:35, 22 May 2024 (UTC)Reply

Thanks for clarifying! I'll keep in mind to only use Twinkle Global's report function for cross-wiki vandalizers. Have a good day! Ternera (talk) 13:47, 22 May 2024 (UTC)Reply

@EPIC: I suggest closing as not done since editing has stopped. IMO a block is not usable atm. A09 (talk) 14:27, 22 May 2024 (UTC)Reply

OK, going ahead and doing so. EPIC (talk) 14:28, 22 May 2024 (UTC)Reply

Global block for 116.206.8.45

Status: Done

116.206.8.45 xwiki-contribs • xwiki-date ^(alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye

Cross-wiki abuse. Fazily • 📩 14:09, 22 May 2024 (UTC)Reply

Done EPIC (talk) 14:10, 22 May 2024 (UTC)Reply

Global block for 204.184.47.243

Status: Done

204.184.47.243 xwiki-contribs • xwiki-date ^(alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye

Crosswiki disruption XReport --RoBri (talk) 15:17, 22 May 2024 (UTC)Reply

Done EPIC (talk) 15:20, 22 May 2024 (UTC)Reply

Global block for 146.158.58.70

Status: Done

146.158.58.70 xwiki-contribs • xwiki-date ^(alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye

Cross-wiki abuse. Leonidlednev (talk) 17:22, 22 May 2024 (UTC)Reply

Done EPIC (talk) 17:23, 22 May 2024 (UTC)Reply

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

Latest comment: 24 minutes ago32 comments13 people in discussion

Note that global blocking currently only applies to IPs, due to a technical limitation. If you wish to request a named account for global [un]locking, please request a global [un]lock here instead. 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-stewards^connect or email your request to the stewards VRT queue at stewards-oversightwikimediaorg (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-appealswikimediaorg.

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:

You have evidence of cross-wiki disruption from the account(s).
You can show that it is not feasible to use local-only blocks or other measures like page protection to combat the disruption.
You have considered making the request in #wikimedia-stewards^connect, 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, --~~~~