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

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:

Global unblock for

Status:    Done

I guess there were good reasons for Vituzzu to globally block this range. But it seems that it also may block legitimate users from Lipetsk. At least we got a message from a user, and he also wrote to Vituzzu publicly: [1]. The reading on the Vituzzu's talk page recommends to write the requests here instead. I checked the ISP that owns the range, and it seems that it's definitely NOT hosting provider only. The requester to my best knowledge, ФВ is legitimate, have written a lot of articles and never have been blocked. Could you please check the situation and unblock the range, or maybe I shoud provide him IP blocks exempt (however there may be other legitimate users from Lipetsk as well)? Dr Bug (Vladimir V. Medeyko) 15:15, 9 February 2018 (UTC)

  • Inaction is inappropriate. Appreciate those who create content! JukoFF (talk) 00:33, 10 February 2018 (UTC)
@Drbug: from what I can see is a colo facility. The range doesn't seem to be allocated to residential customers do you know of more users caught? If only ФВ is caught it may be caused by some malware affecting ФВ's devices. --Vituzzu (talk) 13:04, 11 February 2018 (UTC)
@Vituzzu: According to ip lookup this ip ( belongs to dial-up provider "Lipetskie Kabelnie Seti LLC" (, not to hosting provider --DR (talk) 08:06, 14 February 2018 (UTC)
It seems there are two overlapping assignaments: is it possible LKS owns P3? --Vituzzu (talk) 14:48, 15 February 2018 (UTC)
@Vituzzu: It doesn't looks like. They are located in different cities more than a thousand kilometers apart (( is from Perm and LKSist from Lipetsk) and have neither common owners nor shareholders. Maybe IP-range was reassinged by RIPE? We have several members who was editing from this range before and they claim that the IP address was received from their usual provider. If you don't want to unblock it completely, can you please reduce it to anononly? --DR (talk) 17:44, 18 February 2018 (UTC)
@DR: I've unblocked it while blocking onlyì, I think I'll reblock a smaller range after a series of investigations though. --Vituzzu (talk) 16:10, 19 February 2018 (UTC)
Thank you. --DR (talk) 20:14, 19 February 2018 (UTC)

Global unblock for

Status:    In progress


Why am I blocked? The IP adress is my private PC. I use it for Wikipedia editing since about 4 years ?!?!--Croscher (talk) 13:01, 24 January 2018 (UTC)

Private pc or private VPN/VPS? --Vituzzu (talk) 13:06, 11 February 2018 (UTC)

Global unblock for

Status:    In progress

This range belongs to Deutsche Telekom, probably the largest provider in Germany --Eingangskontrolle (talk) 18:47, 14 January 2018 (UTC)

Then BGP info says otherwise. According to that, belongs to Digital Ocean which is a web hosting service. -★- PlyrStar93. Message me. 18:52, 14 January 2018 (UTC)
I would agree with PlyrStar. As the WHOIS tool on Labs and RIPE itsself would confirm this. --Wiki13 talk 18:58, 14 January 2018 (UTC) the same thing - I am a customer of Deutsche Telekom and I am again blocked after two edits --Eingangskontrolle (talk) 19:06, 14 January 2018 (UTC)

That one's still Digital Ocean. I also did a traceroute from my network to the IP's you mentioned, and the packet never goes through Deutsche Telekom's nodes, while I did another traceroute for a Deutsche Telekom (AS3320) IP and I can see hops belonging to that network. Maybe you should check if your computer has certain VPN services enabled, and see if there are potentially unwanted programs hijacking your traffic, and use different devices under the same network (e.g. cell phone etc. connected to your wifi) and see if they still give you the same IP as the current device you are using. -★- PlyrStar93. Message me. 19:19, 14 January 2018 (UTC)
I would say the use has some kind of VPN service running, cause otherwise you wouldn't end at Digital Ocean. If this is indeed the case maybe a global IP exempt could be granted to the account. --Wiki13 talk 19:28, 14 January 2018 (UTC)

Global block for,, 2a0b:4342:4000::/36, 2400:8900::/30, and

Status:    In progress
  1. Those IP addresses belong to companies who provide VPS services which can be used for open proxies.
  2. Those IP ranges were related to disruptive editing on Chinese Wikipedia involved posting rumors and attacking informations of Wikimedia User Group China (WUGC) and discrimination article content against Shanghai immigrants (e.g. [2], [3], [4], [5], [6]).
  3. A subset of 2400:8900::/30 has already been globally blocked by Vituzzu.
  4. This edit reveals that 守望者爱孟 (who's been banned globally by WMF) was related to this proxy. (He deleted the response from 守望者爱孟 and wrote this in the summary: "有啥好回应的,谁爱撕谁撕,谁爱封谁封,封一个号这么爽,我滋磁"; translation: There's nothing needed to be responded. Enjoy your quarrel and block. [If ]blocking one account gives you such pleasure, I support [you in doing it].).
  5. The first two IP ranges was unblocked in Chinese Wikipedia by User:Techyan who is one of the liaisons of Wikimedians of Mainland China (WMC).
  6. There is a competition between the WMC and WUGC, and members of WMC have posted a lot of rumors and attacking informations against WUGC on Chinese Wikipedia (see the history of WP:中国维基媒体用户组). I didn't believe that the Chinese Wikipedia can prevent those edits happening again in the future. --PhiLiP (talk) 10:26, 28 December 2017 (UTC)

I totally have no idea why you mentioned me. That's a nonsense to global block IP ranges without being abused globally. Tons of excuses, none of them are related to cross-wiki vandalism. --TechyanTalk) 21:43, 29 December 2017 (UTC)

The policy states that "[g]lobal blocks should only be placed where ... local blocks... would be ineffective, or inefficient." Given that there are admins actively sabotaging the local effort to contain vandals, escalating to global blocks is not only suitable, but necessary. -Mys_721tx (talk) 20:45, 31 December 2017 (UTC)
When banning PhiLiP and Mys 721tx globally, Wikipedia will be peaceful.Gszq (talk) 07:10, 3 January 2018 (UTC)

Global block for Special:Contributions/2804:431:d718::/47

Status:    In progress

Cross-wiki vandalism. Repetitively adds and removes whitespace characters. This IP range was globally blocked in September 2017 and has become active again on several wikis. NinjaRobotPirate (talk) 01:01, 7 January 2018 (UTC)

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 unblock

IP is owned by Hotel and it is not Open Proxy, a lot of times before I could easily use Wiki in hotels but now I watch a message that I signed in via open proxy and it was blocked. Voltmetro (talk) 17:11, 12 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)

Global block for

Status:    In progress

Cross-wiki vandalism, in some sort of crusade to remove English words everywhere: [7][8][9][10][11][12][13][14][15][16][17][18][19][20][21][22][23][24][25][26][27][28][29][30][31][32][33][34][35][36][37][38][39][40][41][42][43][44][45]. --Thibaut120094 (talk) 08:06, 1 February 2018 (UTC)

Global block for

Status:    In progress

Massive cross-wiki activity of questionable value: creation of pages of technical purpose in main namespace (be:b:Blockedtext‎). 130+ edits today only. Blocked in Russian wikisource on 28 January. Warned in English wikipedia. Now he chooses wikis where there is no local sysop who can block him (be:b:). --Jarash 13:00, 1 February 2018 (UTC)

Global block for

Status:    In progress

Some weird disruptive edit on my talk page - User_talk:Iggy the Swan & user page User:Iggy the Swan. They come from the Philippines and is part of LTA:My Royal Young. --Iggy the Swan (talk) 22:02, 2 February 2018 (UTC)

@Iggy the Swan: Automatically blocked by the abuse filter in local, I think your user page should be make the request for protection at RFH. SA 13 Bro (talk) 00:54, 3 February 2018 (UTC)
I will rephrase it - LTA:My Royal Young - cross wiki abuse. Iggy the Swan (talk) 08:52, 3 February 2018 (UTC)

Global block for

Status:    Not done

Cross-wiki vandalism. --Ilzhabimantara (talk) 22:28, 13 February 2018 (UTC)

Stale. – Ajraddatz (talk) 00:03, 19 February 2018 (UTC)

Global unblock for

Status:    In progress

I have written a lot of articles and never have been locked. Could you please check the situation and unlock the range? Thank you. (This is not my languaje and I do not know the difference between unlock and unblock) --Sannicolasdeugarte (talk) 19:48, 9 February 2018 (UTC)

Global block for Spambots

Status:    In progress

Open Proxys + Spambots. —AlvaroMolina ( - ) 13:32, 15 February 2018 (UTC)

Global block for

Status:    In progress

Used by enwiki user Vorpzn who is blocked for cross-wiki harassment. Yesterday they also used the IP which was determined to be an open proxy range, it's likely this address on the same ISP is one as well. Ivanvector (talk) 13:37, 15 February 2018 (UTC)

Global block for

Status:    Done

Cross-wiki disruption, so far en, simple and simple-wiktionary. Appears to take pride in their work.Favonian (talk) 10:31, 16 February 2018 (UTC)

Yes check.svg Done by Hoo. – Ajraddatz (talk) 00:04, 19 February 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 (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.
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 unlock for Diegusjaimes

Status:    Done

Hi, I'm not a normal IP. I am the same user. I can't edit with my original account, because this actually locked, and i can't access its. I request unlock and ask for forgiveness for the damages caused at this time. Thanks in advance -- 03:25, 27 July 2017 (UTC) PD: Sorry for my english

To the Stewards, Bernard is a CU and can confirm a new block evasion [46] --Ks-M9 [disc.] 16:24, 28 July 2017 (UTC).
I created it simply to continue editing. There is no vandalism or anybad. I am worried that Wikipedia in Spanish will be so drastic with users who want to edit for the first time, or who want to resume editing, and I am also puzzled by the fact that they consider everyone as a "toxic element" to Anyone who gets blocked. 18:23, 28 July 2017 (UTC) PD: The last text is traduced by Google"
See w:WP:BE and w:WP:SOCK - Using other account to continue editing while blocked is not permitted in most Wikimedia projects, even if the editor only makes good edits.
  • For Diegusjaimes: I suggest you do no edit in Spanish Wikipedia, using any account or anonymously, in no less than six months (i.e. until at least 2018-1-29) and request an unblock there. You're free to contribute other Wikimedia projects once you are unlocked.
  • For stewards: I think the account can be unlocked as long as there're no longer crosswiki issue. This allows user to make significant and useful contributions to other WMF projects (which is beneficial for unblocking in eswiki).

--GZWDer (talk) 19:18, 28 July 2017 (UTC)

Comment. I believe that the initial lock is wrong on a number of grounds. 1) Socking has no impact upon the use of the primary account. 2) Socks are not against WMF terms and use, and the use of global lock is not for this purpose of locking primary accounts. If the user is to be excluded we should be using a consensus of the community discussed in a global ban rather than summary exclusion by judge and jury stewardry.  — billinghurst sDrewth 22:07, 5 September 2017 (UTC)
Yes check.svg Done - no longer any indication of cross-wiki abuse. Eswiki problems can be resolved locally. If cross-wiki abuse resumes, the account can be re-locked. – Ajraddatz (talk) 00:10, 19 February 2018 (UTC)

Global unlock for Celestianpower

Status:    Done

I am not sure why my account was blocked in the first place. It says my account was compromised and so globally blocked, but I see no evidence of this in my contributions. I used to be an administrator on en-wikipedia and en-wiktionary but I have been inactive for a while. Looking to make some sporadic edits, but unable to log in. The message on my en-wikipedia talk page says that I should contact a steward to have it reversed. Is this the correct channel for that? Thanks! —The preceding unsigned comment was added by (talk) 22:30, 29 October 2017‎ (UTC)

Your account was locked by WMF staff due to account compromised in the past. @Tim Starling (WMF): There is a unlock requests issue at here. SA 13 Bro (talk) 23:25, 29 October 2017 (UTC)
I was watching filtered authentication logs and saw the attacker successfully log in to your account in real time. So I locked it immediately, before they were able to do any damage. This attacker typically defaced the English Wikipedia main page within minutes of each account compromise, so it was important to act quickly. The attacker was using publicly available password databases from other websites, such as Yahoo and LinkedIn, correlating email addresses with user names, and trying the passwords against Wikipedia. So it's important that you change your password on any website where you've been using it. See -- Tim Starling (WMF) (talk) 23:47, 29 October 2017 (UTC)
@Tim Starling (WMF): Thank you for alerting me. That's quite worrying. So if I change my password, am I able to continue using this account? Thanks 00:04, 30 October 2017 (UTC)
Yes, you can continue to use that account. I assume you still have access to your email? A steward should contact you, confirm your identity, unlock your account, and give you advice on setting up 2FA. -- Tim Starling (WMF) (talk) 02:00, 30 October 2017 (UTC)
@Tim Starling (WMF): That's great news. Happy to set up 2FA. When might a steward contact me and through what channel? Email? Thanks, 12:41, 30 October 2017 (UTC)
You should e-mail if you want your account unlocked. Ruslik (talk) 19:47, 30 October 2017 (UTC)
The related ticket on OTRS is ticket:2017103110006322. Trijnsteltalk 22:37, 27 November 2017 (UTC)
Tagging as not done; being handled via email. – Ajraddatz (talk) 00:08, 19 February 2018 (UTC)
Now unlocked as "account under control". SA 13 Bro (talk) 00:25, 19 February 2018 (UTC)

Global lock for Waenceslaus

Status:    Not done

Hello. I was very surprised to find out that my account has been blocked on all Wikipedias for WP:NOP. I have not been using any proxy server and I have been editing Wikipedia rarily. This must be a misunderstanding. Waenceslaus (talk) 10:49, 29 January 2018 (UTC)

You are only blocked in English Wikipedia and should appeal your block there, not here. Ruslik (talk) 18:25, 29 January 2018 (UTC)

Global lock for Styron111

Status:    Done

Globally banned user user:Styron111 LTA, plain insults, threats. --Pentachlorphenol (talk) 16:31, 10 February 2018 (UTC)

Support. Agathenon (talk) 17:43, 10 February 2018 (UTC)
Support Support, why is this still pending? Grüße vom Sänger ♫(Reden) 11:24, 16 February 2018 (UTC)
Done by the WMF. – Ajraddatz (talk) 00:13, 19 February 2018 (UTC)

Global lock for Falconfly

Status:    Not done

Falconfly is indefblocked on 3 wikis so far (including for making legal threats on Wikimedia Commons), and has now extended his unwanted behavior to include a personal attack on my English Wikipedia user talk page.   — Jeff G. ツ 03:32, 13 February 2018 (UTC)

Interested OTRS members may test those (deleted) claims against Ticket:2018021210009333.   — Jeff G. ツ 03:46, 13 February 2018 (UTC)
Time2wait.svg On hold pending discussion. RadiX 04:46, 13 February 2018 (UTC)

Make that 4 wikis, including this one for intimidation/harassment edits in this section.   — Jeff G. ツ 15:28, 17 February 2018 (UTC)

X mark.svg Not done - the account is unblocked on the wiki where it has the most edits, and is not engaged in active cross-wiki disruption. – Ajraddatz (talk) 00:15, 19 February 2018 (UTC)

Global lock for Aminnie

Status:    Not done

Long-term cross-wiki spamming, their articles have gone through deletion processes at all applicable wikis and succeeded; repeatedly recreated using this account and a variety of IPs. This user is not competent enough to edit Wikimedia projects, and just doesn't seem to get the point. hiàn 23:07, 14 February 2018 (UTC)

X mark.svg Not done - out of scope for global locks. Not creating obvious disruption across multiple projects. – Ajraddatz (talk) 00:16, 19 February 2018 (UTC)

Global lock for w:Carl Freer-related accounts

Status:    Done

Almost all of them were created around the same time (June-August 2017), often with content based on the w:Carl Freer article, which has been the subject of three WP deletion requests. --Green Giant (talk) 11:10, 16 February 2018 (UTC)

Yes check.svg DoneAjraddatz (talk) 00:17, 19 February 2018 (UTC)

Global lock for LTA User:Iniced

Status:    In progress

Severe vandalism issues, also cross-wiki vandalism issues noted on SPI page. The vandal has been known for severe profanity, sockpuppetry, trolling, attacking other users, mass-scale vandalism, edit warring, and the like. The user has been serial socking via IPs as recently as today. LightandDark2000 (talk) 11:56, 16 February 2018 (UTC)

Not done, abuse only on enwiki. As you are indefinitely blocked on enwiki, I don't think it's appropriate or necessary for you to be policing their accounts.Ajraddatz (talk) 00:23, 19 February 2018 (UTC)
I'm not indef blocked anywhere. By the way, whenever I make such requests concerning sockmasters, either the master account has a history of cross-wiki abuse, or some of their sock accounts do. By the way, Checkusers have left a note on this vandal's SPI page that they have a cross-wiki abuse issue. And if there is not cross-wiki abuse, then why is 1 or 2 of their IP socks currently Globally Blocked? LightandDark2000 (talk) 23:07, 19 February 2018 (UTC)
@LightandDark2000: You're right, I'm sorry. Your signature looks very similar to someone who was reporting accounts who is blocked on enwiki. As to where the abuse is, some socks are locked if the account has vandalism on multiple wikis, or if we think that the accounts may be likely to be used elsewhere. I'll take a closer look at this (and your other reports). – Ajraddatz (talk) 23:57, 19 February 2018 (UTC)
Thanks. BTW, which vandal? I'm completely unaware of the fact that someone else has as a similar signature. I thought that my color pattern was close to unique when I picked it out in October 2017 (I certainly have never seen anyone using a similar color pattern on the English Wikipedia.) LightandDark2000 (talk) 00:18, 20 February 2018 (UTC)
@LightandDark2000: Properly this person good hand sock account, because his signature also have yellow gold color, see this old revision page commented by Poyekhali and find the "Global IP block exempt for Prinsipe Ybarro" section. SA 13 Bro (talk) 23:25, 20 February 2018 (UTC)

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)

Global lock for LTA ROXELANA22 socks

Status:    In progress

These are all unlocked sockpuppet accounts of the Cross-wiki LTA vandal ROXELANA22. All of the accounts have already been CU confirmed. Most of the accounts still have access to other Wikimedia Projects, so all of these accounts should be Locked, since ROXELANA22 is well-known for his cross-wiki vandalism, and because he recently began taking his blocked accounts and "respawned" them on other Wikimedia sites to vandalize. LightandDark2000 (talk) 07:59, 17 February 2018 (UTC)

X mark.svg Not done most of these accounts have no edits, are old, or have no evidence of cross-wiki abuse (or some combination of all three). Also, you are indefinitely blocked on enwiki - you don't need to be policing accounts from there. – Ajraddatz (talk) 23:58, 18 February 2018 (UTC)
@Ajraddatz: What are you talking about? I am not indef blocked on ANY Wikimedia site. By the way, the Cross-wiki abuse is more evident on the most recent socks (which were locked about 1 week ago). This also applies to a couple of my other requests. LightandDark2000 (talk) 23:04, 19 February 2018 (UTC)
Altered status, per the reply at the request for User:Iniced, above. LightandDark2000 (talk)

See ROXELANA22's SPI Archive for some of the vandalism and cross-wiki abuse. The worst acts of vandalism aren't even linked (the most obscene ones were deleted). By the way, this user has been socking via IPs and vandalizing since mid-2006. LightandDark2000 (talk) 07:19, 20 February 2018 (UTC)

Global lock for Naveia ppt

Status:    In progress

WP0 abusers. --jdx Re: 21:04, 17 February 2018 (UTC)

Global lock for Masqueurs

Status:    In progress

This is a legit account created for the sole purpose of enabling people to contact the French oversighters using MediaWiki's Special:Emailuser feature. Its associated email address is that of the privacy-fr-wp OTRS queue. We don't want this account to be used, nor its associated email address to be changed at any time for obvious privacy reasons. We figured out that a global lock would be the most effective way to enforce that. Thanks! — Arkanosis 00:54, 18 February 2018 (UTC)

Or you could just not use the account. It might look odd for people trying to email the account to see that it is locked, especially since the lock reason will not be automatically displayed locally. – Ajraddatz (talk) 23:57, 18 February 2018 (UTC)

Global lock for Manda 1993

Status:    Done

Long-term abuse. --Ilzhabimantara (talk) 02:32, 18 February 2018 (UTC)

Yes check.svg DoneAjraddatz (talk) 00:23, 19 February 2018 (UTC)

Global lock for spambots

Status:    Done

Spambots. Wiki13 talk 11:37, 18 February 2018 (UTC)

Yes check.svg Done.--HakanIST (talk) 07:59, 19 February 2018 (UTC)

Global lock for Fernando BL9

Status:    In progress

WP0 abuser. --Ilzhabimantara (talk) 01:37, 19 February 2018 (UTC)

Global lock for

Status:    In progress

Long term abuse, cross-wiki harrasment. --TechyanTalk) 03:21, 19 February 2018 (UTC)

Also, please lock this user,

a sockpuppet confirmed on zhwiki, with cross-wiki abusive behavior as well.--TechyanTalk) 12:41, 19 February 2018 (UTC)

Global lock for INeverCry sock

Status:    Done

. theinstantmatrix (talk) 07:09, 19 February 2018 (UTC)

Yes check.svg DoneAjraddatz (talk) 07:40, 19 February 2018 (UTC)

Global lock for Vivekka

Status:    Done

Sockpuppet of locked User:Shiwam Kumar Sriwastaw. Blocked on two wikis. --Green Giant (talk) 13:42, 19 February 2018 (UTC)

Yes check.svg Done Ruslik (talk) 19:38, 19 February 2018 (UTC)

Global lock for another sock of User:יעל י

Status:    In progress

Hanay (talk) 14:06, 19 February 2018 (UTC)

Global lock for Hhhggg

Status:    Done

The user is frequently spamming Russian Wikimedia members from different Wikimedia projects with emails (via wiki mail) to participate in current community elections. This is a topic that comes up quite a lot: in 2015, in 2016, in 2017 here on Meta etc. Right now we are experiencing another wave of spam emails coming from this user. The community members that are affected by this are probably going to write here.

I think that this is a long-time abuse and cross-wiki spam that needs to be stopped at global level. The user is currently blocked indefinitely on Wikidata and in Russian Wikipedia with email disabled and they specifically target active users of Russian Wikipedia. stjn[ru] 20:01, 19 February 2018 (UTC)

This page is not a vote. Accounts are not locked based on how many people show up and place the support template on the request. That said, given that there is active, cross-wiki abuse coming from the account, I have locked it. – Ajraddatz (talk) 20:33, 19 February 2018 (UTC)

Global lock for Mana joana

Status:    Done

WP0 abusers. --Ilzhabimantara (talk) 06:15, 20 February 2018 (UTC)

Yes check.svg Done Ruslik (talk) 19:31, 20 February 2018 (UTC)

Global lock for LittleBigPlanet 44

Status:    Done

LittleBigPlanet 44 is Никита-Родин-2002's sock puppet. --Well-Informed Optimist (talk) 07:16, 20 February 2018 (UTC)

Yes check.svg Done Ruslik (talk) 19:27, 20 February 2018 (UTC)

Global lock for Elizabethjneal2

Status:    Done

Cross-wiki spam --Schniggendiller (talk) 08:55, 20 February 2018 (UTC)

Yes check.svg Done Ruslik (talk) 19:26, 20 February 2018 (UTC)

Global lock for Fina dp dp

Status:    Done

WP0 abuser. --Ilzhabimantara (talk) 09:50, 20 February 2018 (UTC)

Done by Stryn. SA 13 Bro (talk) 19:00, 20 February 2018 (UTC)

Global lock for 개굴개굴개굴

Status:    In progress

Sock of Special:CentralAuth/울음주머니. — regards, Revi 12:04, 20 February 2018 (UTC)

Global lock for John Daker sockpuppets

Status:    In progress

Sockpuppets of Special:CentralAuth/John Daker. Ivanvector (talk) 15:29, 20 February 2018 (UTC)

Global lock for spambots

Status:    In progress

Spambots. Wiki13 talk 17:04, 20 February 2018 (UTC)

Global lock for CyrilSturgess5

Status:    In progress

Probably spambot, tries to add blacklisted links at nl.wiktionary. Blocked there. -- Curious (talk) 19:32, 20 February 2018 (UTC)

See also