Steward requests/Global

Steward requests (Global)

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.

For local requests here on Meta, see Meta:Requests for help from a sysop or bureaucrat

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 stewardswikimedia.org.

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

Cross-wiki requests
CheckUser information Global blocks/locks Permissions (global) Permissions (bot) Permissions (other) Username changes/ Unified login conflict resolution Miscellaneous requests URL blacklisting Title/username blacklisting Vandalism reports
Meta-Wiki requests
CheckUser information Deletion Permissions Requests for help

Requests for global (un)block[edit]

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:

You know the IP address(es) 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, 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 http://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: stewardswikimedia.org

Global block for 81.177.254.196[edit]

Status: In progress

81.177.254.196 cross-wiki-contribs • ST • IP info • robtex • gblock • glist

Blocked 9 wikis, adding copyright in Terms of Use, Cross wiki-abuse. --188.32.110.170 13:04, 24 June 2017 (UTC)

Global block for 207.154.237.200[edit]

Status: In progress

207.154.237.200 cross-wiki-contribs • ST • IP info • robtex • gblock • glist

Open proxy; recently used for abuse. 2601:1C0:4401:F360:5445:E841:5DE8:7EDA 23:35, 24 June 2017 (UTC)

Global block for 194.187.249.118[edit]

Status: In progress

194.187.249.118 cross-wiki-contribs • ST • IP info • robtex • gblock • glist

Open proxy; recently used for abuse. The rangeblock (webhost block) would be 194.187.248.0/22. 172.58.43.11 04:59, 26 June 2017 (UTC)

Global block for 200.170.176.77[edit]

Status: In progress

200.170.176.77 cross-wiki-contribs • ST • IP info • robtex • gblock • glist

Open proxy; recently used for abuse. 172.58.43.11 05:04, 26 June 2017 (UTC)

Global block for spam IPs[edit]

Status: In progress

186.88.57.60 cross-wiki-contribs • ST • IP info • robtex • gblock • glist
24.16.31.18 cross-wiki-contribs • ST • IP info • robtex • gblock • glist

Spam in English Wikinews. —Alvaro Molina (✉ - ✔) 20:36, 26 June 2017 (UTC)

Global unblock for 2A03:2880:0:0:0:0:0:0/32[edit]

Status: In progress

2A03:2880:0:0:0:0:0:0/32 cross-wiki-contribs • ST • IP info • robtex • gblock • glist

By mistakely admin blocked this ip range 2A03:2880:0:0:0:0:0:0/32 abusing this is open proxy actually this proxy is not open this is proxy of facebook's internet.org private organization please review and unblock it. --Gamma+ (talk) 03:26, 17 June 2017 (UTC)

Comment: If it is a "private internet organization" (i.e., private web browsing through facebook's virtual servers), then it is considered to be a "webhost", not an open proxy, which is still blockable. 2601:1C0:10A:F73A:1056:9979:D4E9:73AE 11:18, 18 June 2017 (UTC)

Global unblock for 2a03:2880:30:2fda:face:b00c:0:8000[edit]

Status: In progress

2a03:2880:30:2fda:face:b00c:0:8000 cross-wiki-contribs • ST • IP info • robtex • gblock • glist

This ip is mistakely block by admin on all wikis please unblock this id users are waiting for edit from this ip.

--Compassionate247 (talk) 08:14, 23 June 2017 (UTC)

Global block for 121.54.0.0/17[edit]

Status: In progress

121.54.0.0/17 cross-wiki-contribs • ST • IP info • robtex • gblock • glist

Duck does it again another massive vandalism text which is a new target. Beep and Super Beep IP sockpuppet of My Royal Young --66.87.64.251 03:43, 27 June 2017 (UTC)

Global block for 82.145.53.14[edit]

Status: Done

82.145.53.14 cross-wiki-contribs • ST • IP info • robtex • gblock • glist

Obvious IP sock of LTA Wikinger with cross-wiki abuse, most likely an open proxy. -- Favonian (talk) 18:03, 27 June 2017 (UTC)

Done. -- Tegel _(Talk) 18:19, 27 June 2017 (UTC)

Global block for 77.121.194.65[edit]

Status: In progress

77.121.194.65 cross-wiki-contribs • ST • IP info • robtex • gblock • glist

Spam in Spanish Wikiversity. —Alvaro Molina (✉ - ✔) 23:35, 27 June 2017 (UTC)

Requests for global (un)lock and (un)hiding[edit]

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-stewards^connect or email your request to the stewards OTRS queue at stewardswikimedia.org (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:

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 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}}
*{{LockHide|username|hidename=1}} <!-- if you do not want the name to be visible on this page -->
*...
Reasons, etc, --~~~~

Global unlock for GALAXYA8[edit]

Status: In progress

GALAXYA8 (talk • contribs • block • x-wiki • CA • lwcheckuser)

This user was asked to be unlocked globally per ko:user talk:175.117.14.235. And I can trust that the user didn't make 슊슊이 account maybe these accounts are logged in in a same IP, not a same person. The user has requested to be unlocked only original account(Not sock). This user has a real mind of apologizing. This user didn't mean to use sockpuppets. Stewards, this is just a local sockpuppetry, plus I'm the requester who request the lock for 슊슊이 because of abusive username(I believe that other person made/logged in same IPs.). Sorry for bad English. Hope this edit is not a disruptive editing. Thanks. Jerrykim306 (talk) 07:48, 7 June 2017 (UTC)

Adding another comment that this user actually didn't want to use sock puppets. Stewards, I'm saying again that I'm the requester to lock this user's sockpuppets and I cancel it because they're not 슉슉이. Jerrykim306 (talk) 06:28, 19 June 2017 (UTC)

There was very clear evidence, both checkuser and behavioural, connecting him to the other accounts. I am uncomfortable unlocking at this time. – Ajraddatz (talk) 07:35, 19 June 2017 (UTC)

Excuse me, but if you said that checkuser was a clear evidence, maybe that user have logged in to same computer/mobile (like school computer) and the IPs got check usered(see en:WP:SHARE) by an accident. And this user doesn't know that user. How come that the users have been logged in a same IPs? Even other person. Hope stewards understand. :) Jerrykim306 (talk) 09:02, 20 June 2017 (UTC)

Well behavioral is same as "1920x1080", "김 씨", "신태일김윤태짱", but is not same with 슊슊이 and maybe that user did login to a same computer but other person. Jerrykim306 (talk) 12:28, 21 June 2017 (UTC)

Answering "How come that the users have been logged in a same IPs" might violate the Confidentiality Agreement (=Unanswerable), or they are lying. By the way, how can you ensure "And this user doesn't know that user?" — regards, Revi 14:17, 21 June 2017 (UTC)

Answering "By the way, how can you ensure "And this user doesn't know that user?"" That user said multiple times that user abused accounts but not the 슊슊이s. Also Confidentiality Agreement (=Unanswerable) is right though and I'm not 100% sure too. No one is 100% sure too. Thanks. Jerrykim306 (talk) 06:24, 22 June 2017 (UTC)

If I have a question, does it mean that is hard to unlock that user because of these problems? Jerrykim306 (talk) 09:15, 22 June 2017 (UTC)

Global lock for Sher Aziz[edit]

Status: In progress

Sher Aziz (talk • contribs • block • x-wiki • CA • lwcheckuser)

My account id global blocked due to i mailed steward to unblock me and he blocked by globally. I requested on utrs 3 times they are claiming me there is only one way you must request on meta. It is required to unblock me first i need to unblock globally. --119.160.66.68 03:19, 17 June 2017 (UTC)

You're blocked on some five projects and locked globally. What has changed that would make us want to lift those restrictions? – Ajraddatz (talk) 04:42, 17 June 2017 (UTC)

@Ajraddatz: only english wikipedia is important for me i requested on utrs they are claiming to be unblock on english wikipedia you need to global unblock then we will unblock you on english wikipedia119.160.66.68 08:54, 17 June 2017 (UTC)

@Ajraddatz: i am repeating this again i requested unblock request on utrs and also mailed admin they are claiming first you need to unblock on meta globaly. 119.160.66.68 13:05, 26 June 2017 (UTC)