Steward requests/Global

From Meta, a Wikimedia project coordination wiki
Jump to navigation Jump to 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, 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

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 blocks for

Status:    In progress

presumably Olha. Short term block recommended (fr:Wikipédia:Faux-nez/Olha, nl:Wikipedia:Checklijst langdurig structureel vandalisme/Olha) Blocked on sv, no and fr ( Sam Vimes (talk) 11:41, 19 January 2019 (UTC)

Global block for

Status:    In progress

So many IPs of this range are doing vandalism in various wikis, mainly in lists of flags. --Mr. Fulano! Talk 17:09, 24 November 2018 (UTC)

I just came here to report 176 for the same reason. Just blocked on mlwiki -- Razimantv 07:57, 8 December 2018 (UTC)

Global blocks for and

Status:    In progress

(or cross-wiki-contribs ST IP info WHOIS robtexgblockglistabuselog)

At meta I am seeing constant spambot infringements from within the /16, and I see that we have previously blocked the /16 before, though when I do some IP checks they seem to be separate /17s though both still seem to be server colo sets. GUC doesn't show that a block would be problematic, so I am asking for both /17s to have an extended block time, maybe a couple of years if that isn't problematic for logged in users (unknown and may be worth checking for account spambots anyway). Thanks or the consideration.  — billinghurst sDrewth 00:56, 26 November 2018 (UTC)

@Billinghurst: GUC works on subnets again? I get 0 results.   — Jeff G. ツ please ping or talk to me 18:21, 30 November 2018 (UTC)
GUC won't show either abusefilter and spamblocklist hits or deleted contributions, and who knows what accounts may be are created within those two ranges. I do know what I see, hence the report, and we do know that there is a history with these ranges.  — billinghurst sDrewth 06:46, 1 December 2018 (UTC)

Global block for

Status:    In progress

This range is spambot problematic at Meta and has been identified as such previously and now locally blocked until the end of 2020. I will hazard a guess that it is the same xwiki, if it is clear of user accounts, you may wish to consider blacklisting.  — billinghurst sDrewth 01:47, 26 November 2018 (UTC)

Global block for

Status:    In progress

Cross-wiki vandalism. --jdx Re: 12:28, 26 November 2018 (UTC)

Global unblock for

Status:    In progress

This IP address was blocked back in 2014 for "webhost Avante Hosting Services +". It appears that the IP address in question has been rotated to different users. Charwinger21 (talk) 07:01, 30 November 2018 (UTC)

Specifically, the range was assigned to Carrytel (an ISP) on 2018-05-23. Charwinger21 (talk) 09:19, 1 December 2018 (UTC)

Global block for 2001:4898::/32

Status:    In progress

Abused ip range from a cloud provider XXBlackburnXx (talk) 21:14, 2 December 2018 (UTC)

Global block for several ranges in Jakarta, Indonesia

Status:    In progress

Anon-only for ∼1 month, please. Page blanking. Tries to harass cross-wiki those sysops who block them. Subsumes two requests by Jeff_G. above. Incnis Mrsi (talk) 12:07, 3 December 2018 (UTC)

Global block for

Status:    In progress

Cross-wiki vandalism. Vermont (talk) 03:12, 6 December 2018 (UTC)

Global block for 2001:b400::/32(Nipponese Dog Calvero (KAGE) used)

Status:    In progress

Cross-wiki LTA 影武者(KAGE) usually used[1].--MCC214Talk with me#Contributions with me 10:05, 6 December 2018 (UTC)

Is MCC214 kidding about /32? Some half-year ago I requested his /40—that is, 28 times smaller—and yet the block was denied. Lurk in archives and learn which range size is typical for a blocked IPv6. Incnis Mrsi (talk) 18:29, 19 December 2018 (UTC)
I see this[2].--MCC214#aut viam inveniam aut faciam 07:19, 20 December 2018 (UTC)
IPv6 KAGE (Nipponese Dog Calvero) used:2001:B400:E2DA:A886:3150:F5EE:68EB:890B[3], 2001:B400:E2D8:ED2F:D48:DE7D:FF3:25C5[4],2001:b400:e252:64c1:4829:4459:9d43:e16a[5],2001:b400:e231:f6ee:b81e:ce55:e7e:926f[6].--MCC214#aut viam inveniam aut faciam 10:18, 27 December 2018 (UTC)

Obviously not needed to be blocked, just see how active this range is. Go blame Chunghwa telecom which promotes IPv6 real hard and let KAGE take advantage of it. --TechyanTalk) 06:10, 18 January 2019 (UTC)

Global block for 2600:8800:3980:2550:0:0:0:0/64

Status:    In progress

Block evasion by MisterAnthony (talk · contribs), same as this recent request but is now using a slightly different IP range. The same Wikidata item that was linked in that request shows the same behaviour from this IP range and there are already a number of local blocks for this range or IPs from this range. - Nikki (talk) 17:45, 6 December 2018 (UTC)

Global block for

Status:    In progress

Crosswiki vandalism by proxy.   — Jeff G. ツ please ping or talk to me 15:29, 19 December 2018 (UTC)

Global block for

Status:    In progress

WDHB. Vermont (talk) 19:45, 21 December 2018 (UTC)

It seems is an OVH range, so a webhost/proxy. — surjection?〉 20:25, 21 December 2018 (UTC)
Vermont, you beat me to it. Thanks. Please revdel it all, stewards, and when you place a rangeblock, consider not allowing them to use the talk page, and consider blocking 2602:FFF6:F:0:0:0:0:0/48 as well. Drmies (talk) 21:39, 21 December 2018 (UTC)

Global block for

Status:    In progress

It looks to be either an open proxy or to have a web exit point. Edited here today, and shows evidence through GUC of vandalising xwiki previously. Could we please have an extended global block on the IP. Thanks.  — billinghurst sDrewth 05:19, 15 January 2019 (UTC)

Global block for

Status:    In progress

Crosswiki vandalism. --Jivee Blau (talk) 16:52, 15 January 2019 (UTC)

2600:387:a:15::4c potential global block

Status:    In progress

IP address 2600:387:a:15::4c appears to be creating articles titled 1, 2, 3... 10 on lots of small language wiktionaries with the content "1". I've tagged the ones I can find with delete but guc is lagging for me. I don't know if this is an LTA or good faith. --SITH (talk) 14:59, 17 January 2019 (UTC)

Note: regardless of the language or the number, the contribution always reads:

'''1''' [[number]] [[Category:num]]

SITH (talk) 15:07, 17 January 2019 (UTC)
If you look at Special:CentralAuth/StraussInTheHouse, and choose the ones with 10 edits in the edit count column you should be able to see at least 30 of them. SITH (talk) 15:14, 17 January 2019 (UTC)

Global unblock for ( at the moment)

Status:    In progress

This is the wifi given out by Scotrail trains. While it may be wise to block it to those not logged in, it's rather inconvenient to catch logged-in users in the net of a global block. There may be reasons you want to keep it blocked, but I'd find it convenient if I can edit Wikipedia while on the train. Adam Cuerden (talk) 14:21, 20 January 2019 (UTC)

Several open proxies to block globally

Status:    In progress

Open proxies/webhosts. --Martin Urbanec (talk) 09:40, 18 January 2019 (UTC)An address added --Martin Urbanec (talk) 16:16, 18 January 2019 (UTC)Address added --Martin Urbanec (talk) 11:25, 19 January 2019 (UTC)

I've blocked the above mentioned IP addresses locally at cswiki for a month, because they either are abused or attempted to be abused, please perform a global block to stop any (potentional) abuse globally. Thanks. --Martin Urbanec (talk) 11:41, 19 January 2019 (UTC)

Global lock for 2600:1700:6EF1:57D0::/64

Status:    In progress

Cross-Wiki Vandalism since september --Natsu Dragoneel (talk) 23:38, 18 January 2019 (UTC)

Examples: [8], [9], [10], [11], [12], [13], [14], [15], [16], [17], [18] --Natsu Dragoneel (talk) 19:53, 19 January 2019 (UTC)
[19] --Natsu Dragoneel (talk) 15:39, 21 January 2019 (UTC)

Global block for

Status:    Done

Cross-wiki abuse on zh/en/vi/commons, blocked on enwiki. --Stang 11:29, 21 January 2019 (UTC)

Yes check.svg DoneDefender (talk) 21:41, 21 January 2019 (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 globally locked, you should 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 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 Satoshi Kondo/WorldCreaterFighter

Status:    In progress

After being blocked indefinitely in the English-language Wikipedia because of his massive abuse of sockpuppets and persistent POV edits, he switches to the German Wikipedia and got blocked indefinitely there for massive spamming. Hee keeps creating accounts and edits both with IPs and new sockpuppets for years since 2015, as the List in the English-language Wikipedia of Vanjagenije, Sro23 and GeneralizationsAreBad shows it. --Sonra Mint (talk) 17:11, 6 November 2018 (UTC)

Sonra Mint is itself a sock puppet of user de:Benutzer:Dribbler and blocked in german wikipedia(Special:CentralAuth/Sonra Mint). And i do not know how often i have to say this: I am not WorlCreaterFighter. Look at my english talkpage. I have made a list of my former socks.(talkpage) I have also said that I will not work on these topics anymore. Sonra Mint is possibly related to some of them, as he/she is a confirmed sock aswell. Btw. User Tomurtogo is blocked as sock of Tigril(Tirgil34). Satoshi Kondo (talk) 11:17, 7 November 2018 (UTC)
He(or she) is possibly an albanian user, 310 edits on albanian wiki, also blocked on netherland wiki for sockpuppetry... Satoshi Kondo (talk) 11:08, 7 November 2018 (UTC)

Why am I listed here? I just saw the message in Wiki. Please take me from that list. I have nothing to do with this, or am related with this sock in any way. Regards, Akocsg (talk) 17:09, 10 November 2018 (UTC)

Note: Satoshi Kondo is a contributor to Wikimedia Commons user. Why wasn’t our community notified about this de facto ban proposal? Incnis Mrsi (talk) 12:55, 1 December 2018 (UTC)

Global lock for cross-wiki LTA Jessechi sock

Status:    In progress

--MCC214#aut viam inveniam aut faciam 07:23, 8 January 2019 (UTC)

@MCC214: Most of them do not exist. Please check your request properly. RadiX 02:40, 20 January 2019 (UTC)
RadiX,Qwu105730 see [20],2019e11 see [21],2020saveearth see [22],and add Asap2019 (talk • contribs • block • x-wiki • CA • ST • lwcheckuser)[23].--MCC214#aut viam inveniam aut faciam 08:51, 21 January 2019 (UTC)

Global lock for zh.wikipedia LTA SiuMai sock

Status:    In progress

Cross-wiki use sock.--MCC214#aut viam inveniam aut faciam 07:23, 8 January 2019 (UTC)

Global lock for account

Status:    Done

Long-term abuse (Manda 1993) (see my talkpage at MS Wiki). - ArdiPras95 (talk) 06:04, 21 January 2019 (UTC)

Yes check.svg DoneDefender (talk) 15:19, 21 January 2019 (UTC)

Global lock for spammers/puppets

Status:    Done

Lock all:

Spamming cross wiki by the look of them. Thanks --Herby talk thyme 15:48, 21 January 2019 (UTC)

Done. RadiX 16:19, 21 January 2019 (UTC)

See also