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: 4 months ago4 comments3 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}}
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 unblock for 103.60.175.0/24

Status: On hold

103.60.175.0/24 xwiki-contribs • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye

Does not appear to be a webhost or open proxy, to both me and Dane. —‍Mdaniels5757 (talk • contribs) 17:40, 3 April 2024 (UTC)Reply

I've come to the same conclusion. Erledigt and @Elton: FYI. -- Amanda (she/her) 04:08, 4 April 2024 (UTC)Antwort

@AmandaNP: I've removed the local Meta-Wiki block accordingly. I'm now curious to what caused this false positive which lead to blocks still active on five other projects, specially enwiki. I personally don't think 103.60.175.0/24 is OP or webhost (after further review), but was led to error by stalktoy results. I would like an explanation from one of you, if you don't mind, to ensure mistakes like this don't happen again in the future. PS: I've set the request 'on hold' only to give you time to reply before this is archived. Thank you in advance. — Elton (talk) 04:39, 4 April 2024 (UTC)Antwort

Honestly, I don't know where the evidence first came from to make the block which renders me unable to comment. I mean I could be wrong, but if we are going to get any clarity on this, @ST47 and Dane: would be the two to ping, as they are on a higher skill level than I am with this. I have a feeling though that some website/script that detects proxies may be the cause. -- Amanda (she/her) 04:46, 4 April 2024 (UTC)Reply

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

Latest comment: 3 months ago34 comments15 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.

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 Flooerdai

Status: Not done

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

Long-term abuse. Fuerdai. Leonidlednev (talk) 19:54, 9 April 2024 (UTC)Reply

I don't know about this one, this is a 3,5 year old account with no edits since then. EPIC (talk) 19:55, 9 April 2024 (UTC)Reply

Not done per above --Alaa :)..! 06:12, 11 April 2024 (UTC)Antwort

Global lock for Usuarioeditor9

Status: Not done

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

Long-term abuse. Repeated uploading of multiple images that infringe copyright. CarlosEduardoPA (talk) 04:56, 10 April 2024 (UTC)Reply

Is there any other particular abuse here? We don't lock users for copyright violations, that is something that Commons administrators is able to take care of. EPIC (talk) 05:10, 10 April 2024 (UTC)Antwort

Agree, the user is currently not blocked at any project and their most edited projects are large enough that local admins can deal with any copivyo issues. No need for steward action. Johannnes89 (talk) 05:29, 11 April 2024 (UTC)Reply

Not done Johannnes89 (talk) 05:29, 11 April 2024 (UTC)Antwort