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: 1 month ago10 comments6 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 for 223.123.23.88

Status: Done

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

Cross-wiki abuse. Spam / spambot. KonstantinaG07 (talk) 00:16, 25 March 2024 (UTC)Reply

Hmm, they made an edit on Wikinews but nothing other than that, so probably stale. EPIC (talk) 05:42, 25 March 2024 (UTC)Reply

+ enwikiquote [1] Johannnes89 (talk) 09:24, 25 March 2024 (UTC)Reply

I remember at least one more, will try to find it in my browser history KonstantinaG07 (talk) 13:30, 25 March 2024 (UTC)Reply

enwikibooks too --KonstantinaG07 (talk) 13:43, 25 March 2024 (UTC)Reply

Done Johannnes89 (talk) 18:43, 25 March 2024 (UTC)Reply

Global block for 67.180.17.203

Status: Done

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

Cross-wiki abuse. Vandalism on enwiki and simplewiki. JustarandomamericanALT (talk) 20:28, 25 March 2024 (UTC)Reply

Done ----Alaa :)..! 21:51, 25 March 2024 (UTC)Reply

Global block for 36.78.194.218

Status: In progress

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

Cross-wiki abuse. Codename Noreste 🤔 talk 22:53, 25 March 2024 (UTC)Reply

Global block for 45.238.21.106

Status: In progress

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

Cross-wiki abuse. Also lock evasion of Special:CentralAuth/Dante_Antonio_Muñoz_Carriman. KonstantinaG07 (talk) 23:01, 25 March 2024 (UTC)Reply

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

Latest comment: 1 month ago29 comments14 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, --~~~~

Global lock for Kadaj821

Status: Not done

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

Long-term abuse. Eclair802, Eclair802, Eclair802, Kadaj820 and a few other accts. KonstantinaG07 (talk) 00:52, 25 March 2024 (UTC)Reply

none of the sockpuppets mentioned is globally locked, is there a reason why this can't be dealt with locally at itwiki? Johannnes89 (talk) 05:38, 25 March 2024 (UTC)Reply

Was locally blocked after all, and they don't seem to affect other wikis for now. Whether they can be prevented in the future is another topic. Will try to discuss with the local admins. Maybe recommend an abuse filter since their pattern is predictable. Figuring out if there's some underlying open proxy would be good but that's a question from other venue KonstantinaG07 (talk) 13:38, 25 March 2024 (UTC)Reply

I do agree with Johannes here that this seems to be a local vandal, in other words not much for stewards to do here - but yes, maybe taking this with the local administrators instead if this is a long-term vandal or such is a good idea. EPIC (talk) 14:43, 25 March 2024 (UTC)Reply

Agreed with above, local problem for now, no need for global locks. – Ajraddatz (talk) 18:36, 25 March 2024 (UTC)Reply

Global lock for Pokai

Status: Not done

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

clearly a sock of User:Shaunak Chakraborty. ─ Aafī (talk) 16:49, 25 March 2024 (UTC)Reply

I just deleted a bunch of their spam uploads on Commons. ─ Aafī (talk) 17:06, 25 March 2024 (UTC)Reply

I think a lock would be premature here - the user has no edits on projects where I can CheckUser, and is actively (and seemingly unproblematically) contributing on enwiki. A good first step would be starting a local sockpuppet investigation case there. – Ajraddatz (talk) 18:35, 25 March 2024 (UTC)Reply

Hi @Ajraddatz, I feel you are right. I had a thought that asking for a CU was too much when the behavior was pretty much evident but I take your note. I have requested for a CU on enwiki where there have been plenty of socks belonging to this farm. ─ Aafī (talk) 19:08, 25 March 2024 (UTC)Reply