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: 6 minutes ago14 comments7 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 2600:1003:B03F:CADB:0:5:B62C:401

Status: Done

2600:1003:B03F:CADB:0:5:B62C:401 xwiki-contribs • xwiki-date ^(alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye

Cross-wiki abuse. Related to Special:Contributions/2600:1003:B033:260C:0:0:0:0/64 (globally blocked IP range). MathXplore (talk) 03:41, 18 June 2024 (UTC)Reply

Robot clerk note: Done by EPIC. MajavahBot (talk) 05:45, 18 June 2024 (UTC)Reply

Global block for 128.0.82.174

Status: Done

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

Cross-wiki abuse. MathXplore (talk) 07:16, 18 June 2024 (UTC)Reply

Done EPIC (talk) 07:17, 18 June 2024 (UTC)Reply

Global block for 167.103.28.0/23

Status: Done

167.103.28.0/23 xwiki-contribs • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye

Open proxy. AS53813: ZSCALER_PROXY. Syunsyunminmin 🗨️talk 08:13, 18 June 2024 (UTC)Reply

Done EPIC (talk) 08:33, 18 June 2024 (UTC)Reply

Global block for 2605:6400:0:0:0:0:0:0/32

Status: Done

2605:6400:0:0:0:0:0:0/32 xwiki-contribs • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye

Open proxy. Syunsyunminmin 🗨️talk 08:17, 18 June 2024 (UTC)Reply

Done EPIC (talk) 08:34, 18 June 2024 (UTC)Reply

Global block for 195.12.232.229

Status: Done

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

High traffic proxy, xwiki abuse (POV pushing), cf. d:Wikidata:Mezi_bajty#Nejstarší_české_dějiny. --Matěj Suchánek (talk) 09:22, 18 June 2024 (UTC)Reply

Robot clerk note: Done by EPIC. MajavahBot (talk) 09:45, 18 June 2024 (UTC)Reply

Global block for 91.63.248.135

Status: Done

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

Cross-wiki abuse. Wüstenspringmaus _talk 12:42, 18 June 2024 (UTC)Reply

Done, for two weeks given the IP returned to its previous behaviour immediately after the last short block expired. MarcGarver (talk) 12:43, 18 June 2024 (UTC)Reply

Global block for 49.104.49.91

Status: Done

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

Cross-wiki abuse. Blocked at en/simple. MathXplore (talk) 12:50, 18 June 2024 (UTC)Reply

Done EPIC (talk) 12:56, 18 June 2024 (UTC)Reply

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

Latest comment: 37 minutes ago35 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 CommanderInDubio

Status: In progress

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

Cross-wiki abuse. A little background: CommanderInDubio is a disruptive editor, blocked indefinitely on three big projects now for a combination of things including competency issues, copyright violations, making legal threats and lacking in the ability to collaborate. Here are the block details:

enwiki - indeffed: He got indeffed first in May 2020, the block was lifted in January 2021, before he got indeffed again in May 2021. He was inactive for two and a half years before requesting an unblock, which was declined in January 2024.
dewiki - indeffed: He started switching to dewiki in January 2024, where he got blocked twice for personal attacks before being indeffed in March 2024 for continuing his problematic behaviour which he showed in enwiki before as well. He appealed the block at the German Arbcom, got another block for personal attacks during the process, the appeal was declined in May 2024.
eswiki - indeffed: After he got blocked in dewiki in March 2024, he switched to eswiki, where he got blocked for one month because of his competency issues in June 2024. After making legal threats because of that, he got indeffed there as well today.

As you can see, he just continues his behaviour in other wikis after being blocked. tl;dr he a disruptive editor and needs a global lock before disrupting the next wiki. --Icodense (talk) 21:55, 17 June 2024 (UTC)Reply

Hmm, I'm leaning towards the opinion that opening a GRFC for a global ban might be a better alternative here, especially since they are not particularly active on the wikis where they already have local blocks. The case is not entirely uncontroversial here (almost 100k global edits and has granted user rights on one wiki), so I'm going to be checking with some colleagues as well. EPIC (talk) 22:08, 17 June 2024 (UTC)Reply

I don't really see why some user rights which weren't removed on a wiki because he is indeffed anyway (and so there was/is no need to remove them) should be a problem. Anyway, I'm certainly not going to open a GRFC, as I don't desire more threats of legal action against me by this user via mail which I already got because of this blocks at dewiki and eswiki. But thanks for looking at it anyway. --Icodense (talk) 22:18, 17 June 2024 (UTC)Reply