Steward requests/Global

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

For global IP or account 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 or accounts; 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: 1 hour ago20 comments12 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.

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:

You know the IP address(es) or accounts 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 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: stewardswikimediaorg

Global block for User:Shāntián Tàiláng

Status: Not done

Shāntián Tàiláng xwiki-contribs • xwiki-date ^{(Tàiláng alt)} • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • Tàiláng bullseye

See Special:CentralAuth/Shāntián_Tàiláng and Commons:Commons:Administrators'_noticeboard/User_problems#User:Shāntián_Tàiláng This user was originally blocked on en.wikt in 2019, and has subsequently been blocked from en.wp, el.wikt, and blocked a few times on Commons for importing the same dispute from one wiki to the next. And now they are importing it here as well, in fact, it seems the all or nearly all of their edits here at meta are either regarding this situation or trying to get others to proxy for them on projects where they are blocked, so a local block may also be in order edit: this has now happened. Additionally, at least one of their known socks User:Man with a boon is already globally locked for cross-wiki disruption. Five years of disruption and harassment over one block on one project is more than enough. --Beeblebrox (talk) 20:37, 28 January 2025 (UTC)Reply

Support a global lock. Disruptive user, and a local block was not sufficient. Yann (talk) 09:44, 29 January 2025 (UTC)Reply
I'm skeptical of this - Commons could have chosen to indef block and applied a 3-month block instead. Regardless of what one thinks of that decision Meta shouldn't overrule it. I think it's now possible to do temporary global blocks of accounts, and no objection to a 3-month global block. * Pppery * _{it has begun} 19:12, 29 January 2025 (UTC)Reply
@Pppery: The above support comment is from the admin who blocked them on Commons. I would assume that when their immediate reaction to be being blocked there was to keep going on about the same dispute here, Yann changed their mind. Beeblebrox (talk) 01:59, 30 January 2025 (UTC)Reply

Done a global lock request for this user. 興華街 (Hing Wah Street) - 💬 - 📝 17:05, 30 January 2025 (UTC)Reply

Not done. Please see Global bans#Obtaining consensus for a global ban --Alaa :)..! 11:45, 31 January 2025 (UTC)Reply

@علاء This is a request for a global block, NOT a global ban. 興華街 (Hing Wah Street) - 💬 - 📝 14:56, 31 January 2025 (UTC)Reply

Please note that they are same thing, and you not a stew and should not reopen this. aqurs ❄️ 15:14, 31 January 2025 (UTC)Reply

Just want to note here that a global ban and a global block are not the same thing. Global bans lock the account and requires an RfC to implement or appeal, while global blocks are implemented or appealed through us and can be exempted by local communities. EPIC (talk) 16:38, 31 January 2025 (UTC)Reply

Global block for 2800:AF0:108C:D05:0:0:0:0/64

Status: Done

2800:AF0:108C:D05:0:0:0:0/64 xwiki-contribs • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye

Cross-wiki abuse. —MdsShakil (talk) 15:18, 31 January 2025 (UTC)Reply

Robot clerk note: Done by EPIC. MajavahBot (talk) 16:45, 31 January 2025 (UTC)Reply

Global block for 46.125.249.35

Status: Done

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

Long-term abuse. Wikihez (talk) 15:29, 31 January 2025 (UTC)Reply

Robot clerk note: Done by EPIC. MajavahBot (talk) 17:25, 31 January 2025 (UTC)Reply

Global block for open proxys

Status: In progress

45.148.242.0/24 xwiki-contribs • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye
154.82.0.0/16 xwiki-contribs • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye
2607:740:5E:0:0:0:0:0/48 xwiki-contribs • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye
83.142.212.0/24 xwiki-contribs • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye

Open proxy abused by LTA. LuchoCR (talk) 16:31, 31 January 2025 (UTC)Reply

Global block for 64.33.133.19

Status: Done

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

Cross-wiki abuse. Leonidlednev (talk) 17:17, 31 January 2025 (UTC)Reply

Robot clerk note: Done by EPIC. MajavahBot (talk) 17:25, 31 January 2025 (UTC)Reply

Global block for 188.132.222.247

Status: Done

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

Long-term abuse. Ban evasion. Wikinger. Leonidlednev (talk) 17:45, 31 January 2025 (UTC)Reply

Robot clerk note: Done by AmandaNP. MajavahBot (talk) 18:05, 31 January 2025 (UTC)Reply

Global block for 2600:1009:B043:511A:F9B5:F29F:CC57:2936

Status: Done

2600:1009:B043:511A:F9B5:F29F:CC57:2936 xwiki-contribs • xwiki-date ^(alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye

Cross-wiki abuse XReport --aqurs ❄️ 18:26, 31 January 2025 (UTC)Reply

Robot clerk note: Done by EPIC. MajavahBot (talk) 18:45, 31 January 2025 (UTC)Reply

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

Latest comment: 23 minutes ago88 comments29 people in discussion

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.

Temporary accounts (those with username format ~20##-#####) can not be globally locked. See #Requests_for_global_(un)block instead for them.

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, --~~~~

Global lock for Tunar.ee

Status: In progress

Tunar.ee (talk • contribs • block • xwiki-contribs • xwiki-date ^(alt) • CA • gblock • ST • lwcheckuser)

Cross-wiki abuse. cross-wiki spammer. Kadı Message 09:28, 24 January 2025 (UTC)Reply

Are there any recent edits from this account? The last edits I found are from 2024. EPIC (talk) 09:36, 24 January 2025 (UTC)Reply

@EPIC, this user is sock account of Çınarcan. He is using Çınarcan account now. I emailed the steward about gagwiki adminship. He is a cross-wiki spammer. Kadı Message 10:17, 24 January 2025 (UTC)Reply

Global lock for QuantumFoam66

Status: In progress

QuantumFoam66 (talk • contribs • block • xwiki-contribs • xwiki-date ^(alt) • CA • gblock • ST • lwcheckuser)

User is currently indefinitely blocked on dewiki and simplewiki and was recently temporarily blocked on sewiki all for the same disruptive editing to video game-related categories. The user has been warned not to edit in languages they do not know According to the user themselves, English is the only language they speak: "Closing note: someone else in this discussion appears to think that my native language is Ukrainian? It is not. It is indeed English. I'm not good at speaking any other languages, there's no way I could write all this German. --QuantumFoam66 (Diskussion) 06:57, 25. Jan. 2025 (CET)", but this does not stop them from editing in languages they clearly do not know. In addition, it has been pointed out on at least sewiki and dewiki that the English category hierarchy cannot and should not be forced on other language editions and especially not when they do not know the language, not even via machine translation, yet they continue to edit and make changes to the category hierarchy and articles in other languages they clearly do not know. In addition, they have been reported to the incident board on enwiki for this disruptive behaviour. So block on grounds of LTA, cross-wiki abuse (and wasting way too many people's time because of it). --Yupik (talk) 13:27, 27 January 2025 (UTC)Reply

With no home wiki block I am inclined to decline at this time, it seems to be something that perhaps could be handled by local communities for now. Leaving open for another steward to give a potential opinion though. EPIC (talk) 13:32, 27 January 2025 (UTC)Reply

With that being said, if we do decide to decline this then I suggest to do it with a note to QuantumFoam66 to please be careful when performing potentially controversial edits in languages they do not know. I see Yupik's point here, and several of the edits are on small wikis as well, where changes are not as closely monitored. EPIC (talk) 13:59, 27 January 2025 (UTC)Reply

I concur that I think it has to be a decline. A global lock isn't appropriate when they are contributing to some projects constructively.MarcGarver (talk) 17:03, 27 January 2025 (UTC)Reply

If they are contributing to even a single project constructively, we should not be sacrificing the rest of them for that one project's sake imo. Many of their destructive edits are on smaller Wikipedia editions (which also bleed over into Wikidata) that do not have the resources to constantly fix the mess left behind. This editor has been warned on multiple Wikis to stop their destructive editing already, yet continues it anyways; how much more damage do they have to do? :/ - Yupik (talk) 18:34, 27 January 2025 (UTC)Reply

If their behaviour is so harmful, I would expect more local blocks to follow, at least in larger wikis like en, es, fr... have you tried contacting local admins in a few larger wikis? A global (b)lock would have much better chances if there were more local blocks, given that stewards usually act on consensus and currently most project apparently don't really care about their edits. Johannnes89 (talk) 18:43, 27 January 2025 (UTC)Reply

There is currently a proposal to close the Greenlandic Wikipedia, which I hope that you all will read and reflect upon in relation to this request. This is also the situation in many of the Wikipedia versions this user is "editing". The Greenlandic Wikipedia admin also wrote a really good article in the Kurier about AI and how it affects Greenlandic and the Greenlandic Wikipedia, which echoes what Trosterud said back in 2021 at Arctic Knot about the Wikipedia editions in the circumpolar region and Scannell said this fall at Celtic Knot about the Irish Wikipedia and quality. I hope that you (pl.) will reassess your belief that what this user is doing is not bad enough for a global lock just because en/es/frwiki has failed to block them. - Yupik (talk) 09:17, 28 January 2025 (UTC)Reply

Global lock for Appledisk

Status: In progress

Appledisk (talk • contribs • block • xwiki-contribs • xwiki-date ^(alt) • CA • gblock • ST • lwcheckuser)

Cross-wiki abuse. Spam / spambot. 𝐖𝐢𝐤𝐢𝐁𝐚𝐲𝐞𝐫 👤💬 (WikiBayerCatHelper) 23:06, 27 January 2025 (UTC)Reply

Global lock for Shāntián Tàiláng

Status: Not done

Shāntián Tàiláng (talk • contribs • block • xwiki-contribs • xwiki-date ^(alt) • CA • gblock • ST • lwcheckuser)

Importing disputes to cross-wiki sites. Being blocked for three months on Commons but might continue to do so for the rest of wiki. 興華街 (Hing Wah Street) - 💬 - 📝 13:54, 30 January 2025 (UTC)Reply

By my read a global block was more suited for this specific situation, according to when it would and would not be granted, but either one would be fine, this same disruption has now gotten them blocked on five separate wikis, including this one. Beeblebrox (talk) 05:43, 31 January 2025 (UTC)Reply

Not done. Please see Global bans#Obtaining consensus for a global ban --Alaa :)..! 11:45, 31 January 2025 (UTC)Reply

@علاء This is a request for a global lock, NOT a global ban. 興華街 (Hing Wah Street) - 💬 - 📝 14:57, 31 January 2025 (UTC)Reply

HingWahStreet Have you read the Global locks page? Especially that "the user demonstrates an ongoing pattern of cross-wiki abuse that is not merely vandalism or spam". Do you know the difference between Global locks and Global ban? The above mentioned user have around 191K edits globally, and blocked indefinitely in four projects only, and in another project for temporary period (end on 28 April 2025). Plus that has edits in other projects. --Alaa :)..! 15:29, 31 January 2025 (UTC)Reply

Sorry. I'll respect that. 興華街 (Hing Wah Street) - 💬 - 📝 15:35, 31 January 2025 (UTC)Reply

Global lock for TopWikiEditors

Status: In progress

TopWikiEditors (talk • contribs • block • xwiki-contribs • xwiki-date ^(alt) • CA • gblock • ST • lwcheckuser)

Long-term abuse. Cross-wiki abuse. Spam / spambot. User:Prozone77. Bovlb (talk) 17:32, 30 January 2025 (UTC)Reply

Global lock for a Serbian LTA

Status: In progress

Lock all:

name hidden (talk • contribs • block • xwiki-contribs • xwiki-date ^(alt) • CA • gblock • ST • lwcheckuser)
name hidden (talk • contribs • block • xwiki-contribs • xwiki-date ^(alt) • CA • gblock • ST • lwcheckuser)
name hidden (talk • contribs • block • xwiki-contribs • xwiki-date ^(alt) • CA • gblock • ST • lwcheckuser)
name hidden (talk • contribs • block • xwiki-contribs • xwiki-date ^(alt) • CA • gblock • ST • lwcheckuser)
name hidden (talk • contribs • block • xwiki-contribs • xwiki-date ^(alt) • CA • gblock • ST • lwcheckuser)
name hidden (talk • contribs • block • xwiki-contribs • xwiki-date ^(alt) • CA • gblock • ST • lwcheckuser)
name hidden (talk • contribs • block • xwiki-contribs • xwiki-date ^(alt) • CA • gblock • ST • lwcheckuser)
name hidden (talk • contribs • block • xwiki-contribs • xwiki-date ^(alt) • CA • gblock • ST • lwcheckuser)

Long-term abuse. Cross-wiki abuse. Abusive username. Spam / spambot. A LTA with a cross-wiki sockpuppet/spambot farm, originating from sr.wiki. نوفاك اتشمان (talk) 22:07, 30 January 2025 (UTC)Reply