Steward requests/Global

From Meta, a Wikimedia project coordination wiki
Jump to: navigation, search
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, link to the username of the steward who globally blocked the IP address using the code [[User:USERNAME|USERNAME]] so that they are pinged by 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 email using this form or writing at 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

Symbol comment vote.svg 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(at)

Global block 2600:8800:3000:0:0:0:0:0/36

Status:    In progress

Block evasion by globally locked user MisterAnthony. He has been occasionally active on Interlingua wikipedia as various IPs since the locking of his named account:

with a sudden recent flurry of activity:

His signature on iawiki is the creation of micro-stub articles for U.S. actors, each containing one sentence in Interlingua and another in Spanish, partly redundant with the first (ia:Special:Diff/592001). The wikidata item histories indicate he creates similar fill-in-the-blanks micro-stubs for the same actor in dozens of other small languages, together with messing around with wikidata itself.

I havve blocked the /36 on iawiki for 6 months and don't expect collateral problems, based on the size of iawiki and observation of the contributions in the range. There have been previous global blocks within the range:

The 3081 range above is probably stale. The 3080 and 3982 have received blocks as just mentioned. The 3981 is new. If /36 is excessive for a global block, may I suggest:

(Incidentally, a new named account has just appeared: AnthonyAW. Even with only 4 edits, it looks like a sock of this user. Will bear watching.)

--Tortoise0308 (talk) 19:25, 11 January 2018 (UTC)

Global block for and

Status:    In progress

VPN IPs from Windscribe, no major long-term abuse found. However, according to NOP, I suggest that the IP range should be blocked.

Managed to find out this VPN IP range from zh:Special:Permalink/48054315--Hello903hello (talk) 08:42, 30 January 2018 (UTC)

Global block for

Status:    In progress

Cross-wiki vandal (see also en:Wikipedia:Long-term_abuse/Boy_band_vandal) active for more than 10 days. --Horcrux92 (talk) 08:36, 31 January 2018 (UTC)

Could somebody please action this? Also 2001:56a:f580::/41 would need to be blocked, per the last requests linked from the abuse report. Graham87 (talk) 07:16, 27 February 2018 (UTC)
Also, account creation should be allowed, due to collateral damage. I've just found out that the strongest block will apply for IP addresses which have been both locally and globally blocked, so if account creation were disabled in the global block, that would undo the account-creation-enabling effect of the local one. Graham87 (talk) 16:15, 1 March 2018 (UTC)

Global block for

Status:    In progress

Soft block for a year or more, please. Long-term cross-wiki disruption. IP contribs are overwhelmingly—if not exclusively—vandalism and other nonsense. Incnis Mrsi (talk) 10:07, 21 March 2018 (UTC)

@Incnis Mrsi: I think it should be blocked locally on commons, the IP already blocked on, and if you take a look here you'll found that all new changes made on commons! --Alaa :)..! 10:32, 21 March 2018 (UTC)
If the vandal IP projects shit to random Wikimedia sites for more than two years, then why should it be blocked namely on Commons? Incnis Mrsi (talk) 10:43, 21 March 2018 (UTC)
@Incnis Mrsi: 2 edits on simplewiki (2015, 2017), 1 edit on enwikiquote (2017), 5 edits on commons (2018), 5 edits on wikidata (2017), 20 edits on enwiki (2015, 2016), and already blocked until 2019 on enwiki. I don't think it should be blocked globally. Let's wait other stewards --Alaa :)..! 11:02, 21 March 2018 (UTC)

Global block for

Status:    In progress

A leaky hosting ( The former IP is blocked in zh.Wikipedia as a proxy. The latter IP is currently trolling on Commons. Incnis Mrsi (talk) 16:41, 21 March 2018 (UTC)

Global block for

Status:    In progress

A leaky colocation hosting blocked in en and zh.wikipedias. cross-wiki-contribsSTIP inforobtexgblockglist was recently used on Commons to make personal attacks (likely by a globally banned person). Incnis Mrsi (talk) 16:59, 21 March 2018 (UTC)

Global block for

Status:    In progress

A proxy blocked in en and zh.wikipedias. Not necessarily an open proxy, but accessible by a globally banned long-term abuser or somebody impersonating him. Incnis Mrsi (talk) 17:51, 21 March 2018 (UTC)

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

Symbol comment vote.svg 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(at) (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 global locked, you may appeal here without logging in. If you don't want to leak your IP address, you can also appeal your lock to
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 the template 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, --~~~~

Global lock for LTA User:IPhonehurricane95 socks

Status:    In progress

Recent (within the last 3 years) unlocked IPhonehurricane95 socks. The accounts have pretty much been CU confirmed or given away by behavior. For the Stewards who remember, IPhonehurricane95 was a very severe vandal with massive article vandalism, personal attacks, profanity, 9/11 imagery vandalism, and serial socking. He also inspired the vandal (User:Lightning Sabre) behind the recent UnderArmourKid sock family. There has been evidence that he has continued IP socking within the last 2 years, possibly even as recently as yesterday (see the UnderArmourKid SPI Case for the possible IP sock). Since IPhonehurricane95 is known to log back into his older socks and vandalize across multiple Wikimedia Project sites, I'm requesting that all of these sock accounts are Locked. Also, it has been standard practice to Globally Lock all IPhonehurricane95 sock accounts. LightandDark2000 (talk) 12:43, 16 February 2018 (UTC)

Here is IPhonehurricane95's SPI archive, for anyone who needs a refresher, and this is a CU check result on Commons. Most of the veteran users on Wikipedia's WikiProject Tropical Cyclones remember IPh95 (most of the senior editors and admins have been attacked by him as well), as well as a handful of Stewards and Ex-Stewards, especially during his vandalism spree in 2014. LightandDark2000 (talk) 01:33, 18 February 2018 (UTC)

@LightandDark2000: (it has been standard practice to Globally Lock all IPhonehurricane95 sock accounts) How? IPhonehurricane95 account itself not locked! also did IPhonehurricane95 made any vandalism on wikis than enwiki? --Alaa :)..! 10:39, 21 March 2018 (UTC)

@Rschen7754: what is you opinion here as you previously deal with this sock master? --Alaa :)..! 10:42, 21 March 2018 (UTC)
I am reluctant to comment as I have not followed this in recent years (though I can say that it was crosswiki). Perhaps @Trijnstel: remembers? I think there is CUwiki stuff too. --Rschen7754 18:30, 21 March 2018 (UTC)
Alaa: IPhonehurricane95's master account was not locked because the account was not global (only exists on the English Wikipedia), and maybe also to allow him to make unblock requests via WP:UTRS. I'm not really sure why; I wasn't a part of any Steward discussions regarding this sockmaster. By the way, the Stewards did have a policy of Globally Locking all of IPhonehurricane95's sock accounts back in 2014, because he had a history of logging back into blocked accounts to attack other users, and to use the accounts to vandalize other project sites across the Wikimedia sites. By the way, IPhonehurricane95 continued to vandalize in 2015 and 2016, and there is evidence that he continued IP socking in 2017 (and possibly in February 2018 as well). In addition, IPh95's long history of cross-wiki vandalism and personal attacks warrants a Global Lock on all of his socks. As Rschen7754 stated above, there are Stewards and CUs who remember this sockmaster, and if you were to ask any senior user or admin on WikiProject: Tropical cyclones on the English Wikipedia, they would all remember as well, because each of those users (including me) were attacked repeatedly by IPh95. LightandDark2000 (talk) 22:43, 22 March 2018 (UTC)

Global lock for Manda 1993 (3)

Status:    Done

Long-term abuse. --Ilzhabimantara (talk) 23:59, 21 March 2018 (UTC)

Yes check.svg Thanks for reporting --Jyothis (talk) 00:13, 22 March 2018 (UTC)

Global lock for spam-only accounts

Status:    Done

Black magic spambot. -★- PlyrStar93. Message me. 00:04, 22 March 2018 (UTC)

Yes check.svg Thanks for reporting --Jyothis (talk) 00:15, 22 March 2018 (UTC)

Global lock for Jakeweber2w13e

Status:    Done

Sock of cross-wiki date vandal User:Aliabbashiraqi79: [1], [2]. NinjaRobotPirate (talk) 00:50, 22 March 2018 (UTC) Yes check.svg Thanks for reporting--Alaa :)..! 03:09, 22 March 2018 (UTC)

Global lock for bunch of socks

Status:    Done

Cross-wiki abuse, socking, vandalism on multiple projects, etc (Tamara787). -★- PlyrStar93. Message me. 03:04, 22 March 2018 (UTC) Yes check.svg Thanks for reporting--Alaa :)..! 03:12, 22 March 2018 (UTC)

Global lock for Parissa Official socks

Status:    Done

Long-term abuse and cross-wiki spam. Sockmaster was previously locked by Alaa. --hiàn 03:11, 22 March 2018 (UTC)

Yes check.svg Thanks for reporting --Alaa :)..! 03:15, 22 March 2018 (UTC)

Global lock for cross-wiki abuse accounts

Status:    Done

Accounts are only being used for vandalism. -★- PlyrStar93. Message me. 03:32, 22 March 2018 (UTC)

Yes check.svg Done --Alaa :)..! 03:42, 22 March 2018 (UTC)

Global lock for spambots

Status:    Done

Spambots, blocked on nl.wiktionary for (attempted) adding of spamlinks --MarcoSwart (talk) 17:09, 22 March 2018 (UTC)

Yes check.svg Done --Alaa :)..! 17:15, 22 March 2018 (UTC)

Global lock for spambots

Status:    Done

Spambots. Wiki13 talk 21:45, 22 March 2018 (UTC)

Done, RadiX 03:55, 23 March 2018 (UTC)

Global lock for spambot

Status:    Done

Dating profile spam on simple.wiktionary, characteristic of other spambots. --hiàn 21:58, 22 March 2018 (UTC)

Done. RadiX 03:48, 23 March 2018 (UTC)

Global lock for Becauseiammm12345

Status:    Done

Cross-wiki abuse. Account is only being used for vandalism (see also enwiki user talk page). -★- PlyrStar93. Message me. 22:08, 22 March 2018 (UTC)

Done. RadiX 03:32, 23 March 2018 (UTC)

Global lock for socks of INeverCry

Status:    Done

Socks of Globally-banned User:INeverCry. None of these socks have been Locked yet. LightandDark2000 (talk) 02:19, 23 March 2018 (UTC)

Done. RadiX 02:32, 23 March 2018 (UTC)

Global lock for cross-wiki socks of LTA ROXELANA22

Cross-wiki socks of LTA vandal User:ROXELANA22. None of these socks have been Globally Locked yet. See this discussion here for why these accounts need to be Locked; in short, there is no time limit to the age of the Sleeper Accounts that ROXELANA22 will revive or "migrate" across Wikimedia sites to continue his cross-wiki vandalism. LightandDark2000 (talk) 02:39, 23 March 2018 (UTC)

It's extremely important to Globally Lock all of these accounts, since it's possible for sock accounts that have been locally blocked on on wiki to be recreated (or "respawned") on another wiki to continue acts of vandalism, even on wiki sites where the sock account had never existed before. And then, there is also ROXELANA22's history of reusing extremely old Sleeper Accounts for cross-wiki vandalism (including 4 and 6 year old accounts). I've pretty much added all of the remaining unlocked socks that are known. LightandDark2000 (talk) 03:17, 23 March 2018 (UTC)
Done. RadiX 03:30, 23 March 2018 (UTC)

Global lock for socks of LTA Tamara787

These have all been CU confirmed as socks of LTA User:Tamara787. None of these socks accounts have been Globally Locked yet. However, given the history of cross-wiki vandalism and socking (including the use of extremely old Sleeper Accounts), it would be best to Lock all of these accounts. Also see the results of the previous request above, where Tamara787 reused a 5-year-old account to resume vandalism across multiple Wikimedia sites (User:YAGN LONG). By the way, I also strongly suggest a Sleeper Check for more socks, given the revived socking activity with the past week. LightandDark2000 (talk) 02:56, 23 March 2018 (UTC)

Global block for Praxis-Y

Status:    Done

Sock of Yahadzija (globally banned) --Seb az86556 (talk) 03:42, 23 March 2018 (UTC)

Done. RadiX 03:53, 23 March 2018 (UTC)

Global lock for more spambots

Status:    Done

Obvious spambot/vandalism-only accounts. The operator of the first account also appears to be some kind of scammer, which merely adds another reason for a Global Lock. LightandDark2000 (talk) 04:47, 23 March 2018 (UTC)

I also added some more "Black magic" spambot accounts. Apparently, this appears to be some kind of cross-wiki Long-term abuse, so a Global Rangeblock should be considered for the "Black magic" accounts. Can we please get a Global Rangeblock on the "Black magic" spambot accounts? It appears that the person behind those accounts is still actively in the process of generating new socks right now. The cross-wiki abuse definitely merits a Global Rangeblock. LightandDark2000 (talk) 07:38, 23 March 2018 (UTC)
It seemed that all those accounts had been globally hidden, Jhonatan Dododugnophski didn't seemed any cross-wiki spam while blocked on enwiki as WP:NOTHERE. SA 13 Bro (talk) 10:34, 23 March 2018 (UTC)
So I take it that the "Black magic" spambots have also been Locked? In any case, the underlying IP range needs to be rangeblocked, given the spree of socking account creation within the past few days. LightandDark2000 (talk) 10:50, 23 March 2018 (UTC)
@LightandDark2000: Yes. Once an strings of spam accounts are caught by any stewards it can be globally hidden as locked, they can adds those title blacklist by using the Global AbuseFilter tool to trigger those spam username, and the IP range also anonymous global blocked as well, see this example. SA 13 Bro (talk) 11:45, 23 March 2018 (UTC)

Global lock for Braulio Lucamba

Status:    Done

WP0 abuser. --jdx Re: 05:13, 23 March 2018 (UTC)

Yes check.svg Done --Alaa :)..! 08:59, 23 March 2018 (UTC)

Global lock for GreatWikiBen

Status:    Done

Obvious cross-wiki vandalism. All of the edits are pretty much vandalism, and this user has vandalized at least 3 different Wikimedia sites. LightandDark2000 (talk) 08:17, 23 March 2018 (UTC)

Yes check.svg Done --Alaa :)..! 08:59, 23 March 2018 (UTC)

Global lock for Sexbombhaha

Status:    In progress

Obvious vandalism-only account. The account is also in direct violation of Wikimedia username policies for having a very inappropriate/offensive username. LightandDark2000 (talk) 09:14, 23 March 2018 (UTC)

Global lock for Nyle Cohen

Status:    In progress

Vandalism-only account. Note that this user also has accounts across multiple Wikimedia projects. LightandDark2000 (talk) 11:54, 23 March 2018 (UTC)

Global lock for socks of LTA IPhones-are-for-d!cks

Status:    Done

Obvious sock of the LTA anti-IPhone user with the inappropriate username. Once again, severe cross-wiki vandalism (and personal attacks) is evident. LightandDark2000 (talk) 12:10, 23 March 2018 (UTC)

Yes check.svg Done --Alaa :)..! 12:23, 23 March 2018 (UTC)

Global lock for Cavidan Isgender

Status:    In progress

Cross-wiki vandalism. In addition, this user is inciting violence on multiple Wikimedia sites (this user is calling for an Azerbaijani violence/revolution). This user needs to be Locked before he can cause any further damage. LightandDark2000 (talk) 12:26, 23 March 2018 (UTC)

He is still calling for violence, this time on the Az Wikipedia. Someone needs to head there and revert his edits, and delete his created pages, as necessary. LightandDark2000 (talk) 12:54, 23 March 2018 (UTC)

See also