Open main menu
Requests and proposals Steward requests (Global) latest archive
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. 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.

If you are here because you have been blocked by a global block, and believe that the block is in error or you have not done anything wrong, there are a few methods through which you can appeal:

  • If the IP is not currently blocked on Meta, you can post a request to this page following the instructions below to have the IP unblocked.
  • If the IP is currently blocked on Meta, you can post an appeal on your talk page. For maximum effectiveness, ping the steward who globally blocked the IP address using the code {{ping|USERNAME}} so that they are notified about it.
  • If you are editing from an account and have been caught by a global IP block that is unlikely to be removed (i.e. because it is an open proxy or because of long-term abuse), you can request an individual exemption from the block at the requests for global permissions page. Please see the section on global IP block exemptions on that page for specific instructions for making a request.
  • If none of those options work, you are free to contact the stewards using this form or sending a direct email to stewards(at)

Note: (un)blocks apply to IP addresses; and (un)locks apply to global accounts

Cross-wiki requests
Meta-Wiki requests


Requests for global (un)block

  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.
Instructions for making a request

Before requesting, make sure that:

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

To make a request for an account to be locked or unlocked

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
You are not required to disclose your IP in public - you may make requests privately to any steward on IRC or by email at: stewards

Global unblock for

Status:    In progress

On june the thirteenth a steward (masti) blocked this ip range globally for six months with the motivation 'Cross-wiki spam: spambot'.The true motivation was not a spambot which is a computer making automatical spam edits but a troll who abused account creation.Indeed the steward also blocked about twenty fake accounts created from that ip range whose only edits were message spamming in various wikipedias.A global block is useful to protect wikipedia but this kind of block exceeds this need because to stop the abuse it was sufficient preventing users from that ip range from creating new accounts instead of blocking completely the possibility to edit anything.I know that every block causes unavoidably some collateral damage but in this case the collateral damage is too high but most important it is not necessary.I would not be asking to unblock the ip range if the problem was a spambot or an anonymous user who spammed his messages from various ip addresses from this range.I am asking to unblock the ip range because the abuser used the new accounts he continued creating to spam messages.The most proper solution which both protects wikipedia and makes the least possible collateral damage is globally blocking new account creations so that users can continue contributing anonymously and it would be even easier checking possible disruptive edits by keeping an eye on the ip range.Also consider that this italian ip range is maybe the most common provided by the telecommunication company 'Wind' and that almost 33000 innocent users are currently prevented from editing for no justified reason.So please review this six months global block and change its settings to allow normal users to make their usual constructive edits while preventing the abuser from creating new accounts.LuluGigi (talk) 14:15, 12 July 2019 (UTC)

LuluGigi pretends to be a new account. admin here. I’ve been chasing this abuser who has created more than 50 socks and engaged in severe harassment. Do not perform this request. Please Checkuser this account. Jehochman (talk) 11:37, 15 July 2019 (UTC)

Pardon but there is a misunderstanding.I did say that there was an abuser who created several accounts using the blocked ip range.I thought he created just about twenty fake accounts but you said that he created over fifty fake accounts that you call socks.If we are talking about the same individual the abuse is worse than it looked like.I am not that abuser nor pretending anything but just asking to unblock the ip range for anonymous users while keeping blocked the possibility to create new accounts.In this way no more socks will be created but normal users sharing this ip range will be able to contribute which is a valid reason and a balanced solution between the need of protection of wikipedia from the abuser and the least possible collateral damage for constructive users.You might not concur with my thought but for me this is the best way to deal with this problem so please review the block as it was set in view of my observations.LuluGigi (talk) 14:09, 15 July 2019 (UTC)

Global unblock for IP#

Status:    In progress

@Revi: Sir my account is blocked. I can't edit. The reason told is open proxy but it is not the case so please review this. Ilyas Marwat (talk) 07:17, 13 July 2019 (UTC)--

@-revi: I think this user meant to ping you. Viztor (talk) 04:17, 14 July 2019 (UTC)
also I think he just accidentally revealed his IP address here, therefore supervision might be needed. Viztor (talk) 04:18, 14 July 2019 (UTC)

Global block for

Status:    In progress

Cross-wiki spamming through editing & edit summary. Proxy. --TechyanTalk) 17:05, 15 July 2019 (UTC)

Global block for

Status:    In progress

A blocked user who is a regular at el.WP has expanded his activities in other wikies as well. Vrahomarinaner has been blocked in el.WP but he constantly trolls using a range of IPs and plenty of sock-puppets. This has been going for some years but now it is clear that he is expanding his activities in other projects as well. I 've reported his activities in an admin's page in en.WP (permalink) and here is a copy of it:

  1. [1] as
  2. [2] as
  3. [3] as
  4. [4] as and
  5. [5] as

Thanks. Cinadon36 18:25, 15 July 2019 (UTC)

  • update: It seems, apart from greek and english WP, the same user is active at other WPs as well.
Spanish WP
Portugees WP
  • [7] as Τζουλιάνο 10 (duck test +)
French WP
  • [8] as Τζουλιάνο 10 (duck test +)
  • [9] as and maybe as Bulev88 (contributing/changing "Athens" to Piraeus)
Turkish WP
Dutch WP
  • [12] as Τζουλιάνο 10 (duck test +)

Apparantly, this is a case of crosswiki vandalism.Cinadon36 (talk) 20:15, 15 July 2019 (UTC)

Global block for 2405:204:E10A:59CC:F96B:9B6E:8094:A40A

Status:    In progress

crosswiki vandal. --WikiBayer 👤💬 18:15, 16 July 2019 (UTC)

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

  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 your request 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-stewardsconnect or email your request to the stewards OTRS queue at stewards (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
Instructions for making a request

Before requesting that a global account be (un)locked, please be sure that:

  1. You have evidence of cross-wiki disruption from the account(s).
  2. You can show that it is not feasible to use local-only blocks or other measures like page protection to combat the disruption.
  3. You have considered making the request in #wikimedia-stewardsconnect, 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 [[User:Foo|Foo]] ===
{{status}} <!-- do not remove this template -->
*{{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|hidename=1}} <!-- if you do not want the names to be visible on this page -->
Reasons, etc, --~~~~

Global lock for VERDEDEPAR@ro.wikipedia

The accounts have already been Globally Locked. LightandDark2000 🌀 (talk) 00:43, 15 July 2019 (UTC)

Global lock for GeraldFord attack names

Status:    In progress

See usernames - only serve to insult someone (no edits globally). Thanks, --DannyS712 (talk) 00:41, 15 July 2019 (UTC)

Global lock for 小暮伝衛門

Status:    In progress

Their deleted meta user page indicates they are sockpuppets of a globally locked user デーモン閣下 --94rain Talk 09:25, 15 July 2019 (UTC)

Global lock for Spammer LTA Black magic specialist socks

Status:    In progress

Lock all:

Obvious socks of the serial spammer "Black magic specialist", who has been engaging in prolific cross-wiki serial socking and spamming for at least 10 years. Please run a sleeper check and Globally Block their IPs, because they are logging back in to older sleeper accounts. LightandDark2000 🌀 (talk) 03:24, 16 July 2019 (UTC)

Global lock for abusive accounts

Status:    In progress

Lock all:

Abusive user accounts (possibly related). Please also check for sleepers. The first account has admitted to being the sock of a Globally-Locked vandal (possibly Cruizir). The second account was spamming. LightandDark2000 🌀 (talk) 03:58, 16 July 2019 (UTC)

Glock for more cyrillic spambots/spammers

Status:    In progress

Lock all:

Same MO as the big batch from last week. Please run a check for more.Praxidicae (talk) 10:33, 16 July 2019 (UTC)

Global lock for spambots

Status:    In progress

Lock all:

Tons more Praxidicae (talk) 12:13, 16 July 2019 (UTC)

Global lock for Xwiki vanity spammer (ShyhB)

Status:    In progress

Lock all:

Praxidicae (talk) 12:22, 16 July 2019 (UTC)

Global lock for Yahadzija socks

Status:    Done

Lock all:

New sock puppets of Yahadzija. Эlcobbola talk 18:22, 16 July 2019 (UTC)

  Done.-Jon Kolbert (talk) 18:29, 16 July 2019 (UTC)

See also