Steward requests/Global/2017-06

From Meta, a Wikimedia project coordination wiki
Jump to navigation Jump to search
Warning! Please do not post any new comments on this page. This is a discussion archive first created on 01 June 2017, although the comments contained were likely posted before and after this date. See current discussion.

Contents

Requests for global (un)block

Global block for 1.180.215.6

Status:    Done

Continually creating nonsense pages on many wikis using the interface message, such as "Wikipedia does not have an article with this exact name. Please search for ... in Wikipedia to check for alternative titles or spellings". --WhitePhosphorus (talk) 08:36, 27 May 2017 (UTC)

Blocked previously, see Steward_requests/Global/2017-05#Global_block_for_1.180.215.0.2F24.2C_1.180.237.0.2F24_and_124.239.251.0.2F24. --WhitePhosphorus (talk) 08:44, 27 May 2017 (UTC)
Yes check.svg Done by Tegel. - Prinsipe Ybarro (Talk to me) 09:38, 1 June 2017 (UTC)

Global block for 113.53.228.87

Status:    Done

Long-term spam in English Wikinews. —Alvaro Molina ( - ) 07:28, 1 June 2017 (UTC)

Yes check.svg Done by HakanIST. - Prinsipe Ybarro (Talk to me) 09:41, 1 June 2017 (UTC)

Global block for 2601:87:4100:A504:CC89:4E90:6F1C:8D84

Status:    Not done

Vandalism in enwiki, mostly large text such this previous massive vandalism and major massive vandalism. Blocked in 1 day on May 24 and block in 1 week on May 28. - Prinsipe Ybarro (Talk to me) 10:12, 1 June 2017 (UTC)

It can be locally handled. Matiia (talk) 23:34, 1 June 2017 (UTC)

Global block for 71.208.177.245 and 71.208.175.82

Status:    Not done

Cross-wiki vandalism per this edit.   — Jeff G. ツ 11:41, 23 May 2017 (UTC)

The vandalism continues with a new IP address:

  — Jeff G. ツ 00:09, 25 May 2017 (UTC)

A global block doesn't seem to be needed anymore. Matiia (talk) 03:06, 2 June 2017 (UTC)

Global block for 2601:58D:302:9462:5DBB:17C8:5DC3:E757

Status:    Not done

cross-wiki vandalism like that about David Koepp. --NicoScribe (talk) 17:34, 28 May 2017 (UTC)

Now the vandal is using another address: 2601:58D:302:9462:55CE:809C:8032:F559 xwiki-contribs xwiki-date ST IP info WHOIS robtexgblockglistabuselogipchecker
--NicoScribe (talk) 14:48, 30 May 2017 (UTC)
They don't seem to be used anymore. Thanks for the report, anyway. Matiia (talk) 03:01, 2 June 2017 (UTC)

Global block/unblock for 77.245.115.219

Status:    Done

xwiki spam from "Recently reported forum spam source" --Rschen7754 16:48, 29 May 2017 (UTC)

Done. Matiia (talk) 03:03, 2 June 2017 (UTC)

Global block for 162.251.21.209

Status:    Done

Long-term abuse. --209.242.141.28 17:43, 31 May 2017 (UTC)

Done. Matiia (talk) 02:56, 2 June 2017 (UTC)

Global block/unblock for 5.228.5.8

Status:    Done

xwiki spam --Rschen7754 02:43, 2 June 2017 (UTC)

Done. Matiia (talk) 02:46, 2 June 2017 (UTC)

Global block for 24.4.238.223

Status:    Done

Open proxy; open on ports 443 and 60443. --Ks0stm (TCGE) 15:41, 2 June 2017 (UTC)

Yes check.svg DoneDefender (talk) 16:59, 2 June 2017 (UTC)

Global block for 166.84.1.2

Status:    Not done

Dedicated proxy IP, registered to this webhosting service. Likely a banned/blocked user socking. They've engaged in constant harassment of an en.wiki admin. 2601:1C0:4401:F360:7DF8:AF46:7C8B:7470 02:36, 21 March 2017 (UTC)

Stale. – Ajraddatz (talk) 18:02, 3 June 2017 (UTC)

Global block for 213.136.64.0/20

Status:    Not done

Webhosting/VPN service. Connected through "MobiProxy" VPN service.—The preceding unsigned comment was added by 213.136.77.188 (talk)

Stale. – Ajraddatz (talk) 18:02, 3 June 2017 (UTC)

Global block for 210.209.72.0/24

Status:    Not done

Webhosting/VPN service. Connected through "MobiProxy" VPN service.—The preceding unsigned comment was added by 210.209.72.186 (talk)

Stale. – Ajraddatz (talk) 18:02, 3 June 2017 (UTC)

Global block for 113.20.28.0/22

Status:    Not done

Webhosting/VPN service. Connected through "MobiProxy" VPN service.—The preceding unsigned comment was added by 198.236.201.79 (talk)

Stale. – Ajraddatz (talk) 18:02, 3 June 2017 (UTC)

Global block for Brazilian IP Addresses

Status:    Not done

Brazilian IPs performing persistent editing war and vandalism and 3RR violation at zh-yue:華地馬 and zh-yue:華德馬艾坎塔拉, and also have got the same edit features in zh-yue:卡米洛 山塔納 this topic. According to the experiences for wikipedia's sock puppets. I think they are USER:JoseNivalJunior2531. Because I have checked for their IPs (see their IPs in iplocation.net), they come from either Fortaleza or Poco da Pedra, Brazil.--PQ77wd (talk) 23:23, 2 April 2017 (UTC)

Newest information: Latest IP have made the same violation in zh-yue:奧巴諾‎. It's so similiar for these IP edit features from above. --PQ77wd (talk) 00:04, 3 April 2017 (UTC)

Comment CommentIf they only make disruptive edits in zh-yue, then why not just block them there? -- ? —The preceding unsigned comment was added by PokestarFan (talk)

Because we have no IP checkers in zh-yue. And also the administrators ignore these IPs' bad behaviors. --PQ77wd (talk) 02:21, 5 April 2017 (UTC)
Newest information: I have seen 177.98.222.173 that IP was the same edit feature like of above in zh-yue:孔愛德 on today.--PQ77wd (talk) 00:24, 6 April 2017 (UTC)
Stale. – Ajraddatz (talk) 18:02, 3 June 2017 (UTC)

Global block for Long-term Wikinews spambots

Status:    Not done

Long-term spam in English Wikinews. —Alvaro Molina ( - ) 11:22, 17 April 2017 (UTC)

Abuse filter blocked the IP which is to expire after 31 hours. -- acagastya 12:03, 17 April 2017 (UTC)
Stale. – Ajraddatz (talk) 18:02, 3 June 2017 (UTC)

Global block for 2607:FB90:0:0:0:0:0:0/32

Status:    Not done

Cross-wiki abuse and Long-term abuse on English Wikipedia. --209.242.141.28 18:16, 17 April 2017 (UTC)

That's a rather large global block request, considering how T-Mobile only hands /128s to its wireless customers. Dargasea (talk)
Stale. – Ajraddatz (talk) 18:02, 3 June 2017 (UTC)

Global block for 209.242.141.28

Status:    Not done

Crosswiki abuse blocked by Widr for one year and it currently blocked by Az1568 for one week can you please global block for one week for now? --2602:306:36D5:5690:ADD7:9362:B1DD:5708 17:24, 29 April 2017 (UTC)

Stale. – Ajraddatz (talk) 18:02, 3 June 2017 (UTC)

Global block for Bertrand101 IPS

Status:    Not done

Long-term abuse; Bertrand101 --99.109.85.105 05:01, 30 April 2017 (UTC)

Stale. – Ajraddatz (talk) 18:02, 3 June 2017 (UTC)

Global block for MRY socks

Status:    Not done

Obvious IP sock of My Royal Young can you make a possible rangeblock on enwiki right now --209.249.5.140 21:59, 25 May 2017 (UTC)

Stale. – Ajraddatz (talk) 18:03, 3 June 2017 (UTC)

Global block for 75.166.108.192

Status:    Done

Cross-wiki abuse, En-Wiki and Commons; see en:User:Bri/Denver LTA for context. -- Favonian (talk) 21:23, 2 June 2017 (UTC)

done by Tegel.--HakanIST (talk) 06:52, 3 June 2017 (UTC)

Global block for 124.244.162.51

Status:    Done

Cross-wiki abuse and Long-term abuse. Blocked on zhwiki --Brandon K  Talk  09:16, 29 May 2017 (UTC)

Done. – Ajraddatz (talk) 18:52, 5 June 2017 (UTC)

Global block for 68.106.31.2

Status:    Done

Open proxy, open on ports 49152, 49153. --Ks0stm (TCGE) 01:11, 5 June 2017 (UTC)

Done. RadiX 01:15, 5 June 2017 (UTC)

Global block for 180.183.161.193

Status:    Done

Open proxy, open on many ports. --Ks0stm (TCGE) 18:48, 5 June 2017 (UTC)

Blocked. – Ajraddatz (talk) 18:50, 5 June 2017 (UTC)

Global block for 208.109.0.0/16

Status:    Not done

Godaddy.com servers, highly abused across several wikis, long-term abuse, block log on en.wiki. 178.45.10.9 23:52, 3 June 2017 (UTC)

Self-close/withdraw. I have handled this locally, and the disruption has only been caused on en.wiki. 2601:1C0:4401:F360:3DB2:F0A8:EEA7:B25F 18:57, 9 June 2017 (UTC)

Global block for 95.215.44.0/22

Status:    Not done

Registered as "Virtual Server hosting" high visibility for abuse. :2601:1C0:4401:F360:291A:C7EC:8E39:D51F 04:57, 4 June 2017 (UTC)

Self-close/withdraw. I have handled this locally, and the disruption has only been caused on en.wiki. 2601:1C0:4401:F360:3DB2:F0A8:EEA7:B25F 18:56, 9 June 2017 (UTC)

Global block for 23.254.128.0/17

Status:    Not done

Registered as hostwinds VPN service. high visibility for abuse. 2601:1C0:4401:F360:3DB2:F0A8:EEA7:B25F 04:57, 5 June 2017 (UTC)

Self-close/withdraw. I have handled this locally, and the disruption has only been caused on en.wiki. 2601:1C0:4401:F360:3DB2:F0A8:EEA7:B25F 18:56, 9 June 2017 (UTC)

Global block for 178.255.154.0/24

Status:    Not done

Registered as Czech Republic dedicated servers VPN service. high visibility for abuse. 2601:1C0:4401:F360:3DB2:F0A8:EEA7:B25F 04:39, 6 June 2017 (UTC)

Self-close/withdraw. I have handled this locally, and the disruption has only been caused on en.wiki. 2601:1C0:4401:F360:3DB2:F0A8:EEA7:B25F 18:56, 9 June 2017 (UTC)

Global block for 117.120.18.0/24

Status:    Not done

Cloud webhosting service. Heavily abused. 2601:1C0:4401:F360:3DB2:F0A8:EEA7:B25F 00:01, 7 June 2017 (UTC)

Self-close/withdraw. I have handled this locally, and the disruption has only been caused on en.wiki. 2601:1C0:4401:F360:3DB2:F0A8:EEA7:B25F 18:56, 9 June 2017 (UTC)

Global block for 94.185.80.0/21

Status:    Not done

Webhosting service. Heavily abused.

Self-close/withdraw. I have handled this locally, and the disruption has only been caused on en.wiki. 2601:1C0:4401:F360:3DB2:F0A8:EEA7:B25F 18:56, 9 June 2017 (UTC)

Global block for 75.166.108.192

Status:    Done

Just came off a short-term, global block and has resumed harassment at Commons; see en:User:Bri/Denver LTA for context. Oddly, his latest "controbutions" don't seem to show up on the global contribs list, by here they are: c:Special:Contributions/75.166.108.192. The remorse is a bit hard to believe. -- Favonian (talk) 19:49, 7 June 2017 (UTC)

Self-close; IP has been blocked for a month by Defender. Favonian (talk) 16:15, 9 June 2017 (UTC)

Global block for some open proxies

Status:    Done
Status:    Done
Status:    Done
Status:    Done
Status:    Done

All have been confirmed as being abused via CheckUser on en.wiki and hardblocked locally for one year. --Ks0stm (TCGE) 17:34, 10 June 2017 (UTC)

All done. RadiX 04:01, 12 June 2017 (UTC)

Global block for 75.166.118.17

Status:    Done

Cross-wiki abuse, En-Wiki, source and news; see en:User:Bri/Denver LTA for context. -- Favonian (talk) 17:41, 11 June 2017 (UTC)

Yes check.svg Done. -- Tegel (Talk) 17:49, 11 June 2017 (UTC)

Global block for 93.188.37.174

Status:    Done

Cross-wiki spam, long-term spammer.Syum90 (talk) 09:01, 9 June 2017 (UTC)

Yes check.svg DoneDefender (talk) 16:18, 13 June 2017 (UTC)

Global block for 31.10.97.71

Status:    Done

xwiki spam --Rschen7754 00:51, 14 June 2017 (UTC)

Done. Matiia (talk) 00:57, 14 June 2017 (UTC)

Feasibility of global block for 2A03:2880:____:____:FACE:B00C:0:____

Status:    Not done

Hello,
While patrolling on Wikidata, I frequently see problems from users using the address ranges 2A03:2880:____:____:FACE:B00C:0:____, such as synchronized attacks on items (example1, example2). I have also noticed that:

I am not an expert about open proxy. I don't know whether all these addresses are open proxies and should be blocked. But if I look at the first global block, 2A03:2880:11:1FEC:0:0:0:0/64, I am wondering: perhaps 2A03:2880:11:0:0:0:0:0 corresponds to open proxies too? perhaps 2A03:2880:0:0:0:0:0:0 corresponds to open proxies too (my example of Stalk toy request shows that several Wikipedia administrators think so)? perhaps these address ranges should be blocked?
Regards --NicoScribe (talk) 22:59, 2 May 2017 (UTC) +NicoScribe (talk) 18:11, 4 May 2017 (UTC) +NicoScribe (talk) 17:36, 5 May 2017 (UTC)

The Ipv6 address saboteur sometimes use 66.220.158.103、66.220.158.107、66.220.158.108、66.220.158.109 as well, i used to track the addresses since sep 2016, they have a same pattern of behavior and targets.Cherjau (talk) 23:25, 10 May 2017 (UTC)

Complex situation

Butting my head in here as a former steward who can probably help explain the complexity of the request being made. Noting that mw:Help:Range blocks/IPv6 is pertinent to understanding. The request while sounding (somewhat) simple, has larger implications and should reflect a policy decision and approach rather than a series of blocks.

Questions first:

  • Is there evidence of a system-wide problem for the overarching ranges, excluding the vanity IPs within the sets? Noting that there may be useful edits occurring crosswiki and for stewards to check such usage is not a trivial task, and one would expect a good reason for a global/broader block.
  • Is there evidence from your checkusers of whether this should be a hard or a soft block, as there may or may not be legitimate editing from logged-in accounts.

Commentary:
That said it is an interesting that the IPs is all facebook management IP range, so unless it is facebook staff, it is some type of proxy service. There seems to be clarity about the source, and almost a vanity approach to their range descriptions and use.

  • Do we (collectively) wish to stop/block facebook proxy addresses from editing wikis?
  • Do we have a clear understanding of the process being used to edit, and how widely it can be abused? How/why is facebook offering proxies for editing?
  • Blocking those subranges based solely on the :FACE: component of the IP address is going to be difficult/problematic as you need to start much further up the IP range if collective, and is going to involve significant range blocks. Or we have a plethora of small blocks on the lower ranges, which is time consuming, and difficult to manage.

Notes: 66.220.158.103 and like IPs show up as in the range 66.220.144.0/20 (facebook). It is a pretty tight range, and could be managed by blocking something like 66.220.158.96/28]

So if we need to stop those "...:face:booc:..." IP addresses doing it as global blocks for stewards is a problem, and it may be better to seek a better technical solution from the WMF developers. They may be able to do something outside of the wiki tools, or by other means. We should be resolving what is the issue, and does it constitute a global problem prior to acting.  — billinghurst sDrewth 04:37, 11 May 2017 (UTC)

Thank you, Cherjau. On the French Wikipedia, I have noticed that 66.220.158.108 is interested by the town covè in Benin [1] and that 66.220.158.103 is interested by the same town along with some 2A03:2880:____:____:FACE:B00C:0:____ users, in this history in 2015 and 2016.
Thank you, Billinghurst:
  • I admit that my understanding of the technical aspects is limited.
  • About your first question: I have not searched for evidence of a system-wide problem. I have just noticed that almost all the edits from 2A03:2880:____:____:FACE:B00C:0:____ users were incorrect, while loking at the "recent changes" lists on 2 projects: Wikidata and French Wikipedia. The edits are numerous: the list above has been created during a few days (and since the 5 May I have a local list with many other addresses from this range).
  • About your second question: I have not talked about this problem with administrators or checkusers from Wikidata and French Wikipedia.
  • You mentioned "proxy service", but did you read the last part of this edit on the English Wikipedia? It mentions interesting elements: "Facebook IPs used for vandalism/sockpuppetry", "open proxy for Facebook users", "massive vandalism", "Definitely registered to Facebook", "There's no non-facebook IP addresses being used in the /32 range", "longterm block on 2A03:2880::/32 for this sockdrawer", "abuse from anon-IPs", "face:b00c block collateral", "ip addresses with FACE:B00C in their range are used by internet.org app service", "that block is much too broad...no, it's not", "the persistent disruption and vandalism by that sockmaster is extensive", "someone from that range is trying to change my WP password", etc.
  • Since the beginning, I have talked about the block of 2A03:2880:0:0:0:0:0:0, not the block of all the addresses containing the :FACE: or :FACE:B00C: component.
  • I have one question: I suppose that the policy No open proxies is applicable to all Wikimedia projects, so why the block of an open proxy on one project (for instance 2A03:2880:0:0:0:0:0:0/__ on the English Wikipedia) is not systematically escalated to a global block here?
Thank you, Masti, for the global block that you applied on 9 May to User:2A03:2880:0:0:0:0:0:0/32 with the comment "open proxy". Is it linked to my request here?
Perhaps Tegel or Vituzzu (who have made some global blocks in the list above) or DMacks or JamesBWatson (who have blocked 2A03:2880:0:0:0:0:0:0/__ on English Wikipedia) have more information?
Regards --NicoScribe (talk) 15:36, 12 May 2017 (UTC)
Closing - stale, not done. – Ajraddatz (talk) 17:39, 16 June 2017 (UTC)

Global block for the boy band vandal

Status:    Done

I've just discovered that the boy band vandal has been a cross-wiki vandal, not just localised to the English Wikipedia. Ever since I blocked them there, it seems that their activity on other language Wikipedias has ramped up. For example, see the history at de:Jackson Five. I've had these IP's blocked in enwiki for a month or so, and as far as I know, those blocks haven't caused any collateral damage on that site. Graham87 (talk) 13:42, 30 May 2017 (UTC)

Done. – Ajraddatz (talk) 17:40, 16 June 2017 (UTC)

Global block for MRY (My Royal Young) IP address socks

Status:    Not done

Batch 1:

Batch 2:

Batch 3:

Vandalism on tlwiki, mostly related to articles, such this one. Needs rangeblock. - Prinsipe Ybarro (Talk to me) 11:39, 7 June 2017 (UTC)

UPDATED - @Linedwell: The long-term abuse of My Royal Young, can IP global block (including the rangeblock from batch 1 to 2) all from batch 1 to batch 3 please? - Prinsipe Ybarro (Talk to me) 12:05, 7 June 2017 (UTC)
Not seeing enough recent and cross-wiki abuse to justify a global block --> not done. – Ajraddatz (talk) 17:42, 16 June 2017 (UTC)

Global block for 97.72.234.4

Status:    Done

Long term abuse. See CU list users. --Ks0stm (TCGE) 19:11, 7 June 2017 (UTC)

Done by RadiX. – Ajraddatz (talk) 17:41, 16 June 2017 (UTC)

Global block for 83.237.114.134

Status:    Not done

Cross-wiki spam, range blocked on bgwikt. --WhitePhosphorus (talk) 09:14, 9 June 2017 (UTC)

Stale now, not done. – Ajraddatz (talk) 17:42, 16 June 2017 (UTC)

Global block for 118.100.10.42

Status:    Done

Cross-wiki vandalism: blanking pages. --WhitePhosphorus (talk) 06:46, 17 June 2017 (UTC)

Yes check.svg DoneDefender (talk) 17:32, 17 June 2017 (UTC)

Global block for 46.255.35.240

Status:    Done

Cross-Wiki Spam. —Alvaro Molina ( - ) 05:06, 18 June 2017 (UTC)

Yes check.svg Done, Linedwell [talk] 05:22, 18 June 2017 (UTC)

Global block/unblock for 78.137.11.110

Status:    Done

xwiki spam. --Rschen7754 18:20, 19 June 2017 (UTC)

Blocked and mopped, thanks. – Ajraddatz (talk) 18:21, 19 June 2017 (UTC)

Global block for 66.87.151.0/24

Status:    Done

IPs from the range 66.87.151.0/24 are bombarding my talk page at WikiNews. It's not apparent from the log, as some kind soul deletes the page periodically. The sibling range 66.87.150.0/24 has previously been globally blocked for similar transgressions. See en:User:Bri/Denver LTA for context. -- Favonian (talk) 16:44, 20 June 2017 (UTC)

Now cavorting at WikiSource. Favonian (talk) 21:11, 20 June 2017 (UTC)
Self-close; range blocked by Tegel. Favonian (talk) 20:50, 21 June 2017 (UTC)

Global block for 109.195.85.122

Status:    Done

Cross-wiki abuse.--Kkairri (talk) 03:39, 21 June 2017 (UTC)

Yes check.svg DoneDefender (talk) 20:32, 21 June 2017 (UTC)

Global block for 149.126.4.73

Status:    Done

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

Yes check.svg DoneDefender (talk) 18:42, 22 June 2017 (UTC)

Global block for 5.248.165.238

Status:    Done

Spam only. Started 04:51, 20 Jun 2017 on en.wikipedia.org, by the end of that day they had targetted four wikis: es.wikiquote.org; de.wikipedia.org; en.wikipedia.org; es.wikipedia.org. Has since spread to at least 12 wikis in total although their primary target has been en.wikipedia.org. All of their posts are unsigned, most include a partial URL, and all include the text "Forex brokers" in the edit summary, often in the section heading as well. Some of their posts are new sections; some overwrite page content (example). Still active; most recent that I have found is 04:55, 23 Jun 2017 on fr.wikipedia.org. I'm pretty sure that I have come across a user with the same modus operandi in the past, at least a year ago. My worry is that they may again change IP addresses, and become harder to detect. --Redrose64 (talk; at English Wikipedia) 09:02, 23 June 2017 (UTC)

Yes check.svg Done. -- Tegel (Talk) 09:11, 23 June 2017 (UTC)

Global block for 178.155.4.68

Status:    Done

Spam. —Alvaro Molina ( - ) 22:38, 23 June 2017 (UTC) But it's an open proxy. It's blocked by RadiX for six months. 149.62.201.57 10:13, 24 June 2017 (UTC)

Global block for 82.145.53.14

Status:    Done

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

Yes check.svg Done. -- Tegel (Talk) 18:19, 27 June 2017 (UTC)

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

Global lock for Wikinews Spambots

Status:    Done

Spam-only accounts (spambots). —Alvaro Molina ( - ) 07:26, 1 June 2017 (UTC)

Yes check.svg Done by HakanIST. - Prinsipe Ybarro (Talk to me) 09:23, 1 June 2017 (UTC)

Global lock for Astronaut Henry

Status:    Done

Long-term abuse; Henry Applegate --2602:306:36D5:5690:E9E7:ED3D:EB39:79F1 05:26, 1 June 2017 (UTC)

Is this cross-wiki? Ruslik (talk) 02:30, 2 June 2017 (UTC)
@Ruslik0: its already done by Tegel 209.242.141.28 15:31, 2 June 2017 (UTC)

Global lock for Emilyliu009 and Emilyliu00988

Status:    Done
Yes check.svg Done Ruslik (talk) 02:29, 2 June 2017 (UTC)

Global lock for 影武者(Nipponese Dog Calvero)

Status:    Done

--Lanwi1(Talk) 20:58, 1 June 2017 (UTC)

Yes check.svg Done Ruslik (talk) 02:25, 2 June 2017 (UTC)

Global lock for Abhimand

Status:    Done

Spam-only account (spambot). —Alvaro Molina ( - ) 21:12, 1 June 2017 (UTC)

Done. RadiX 00:16, 2 June 2017 (UTC)

Global block for Márcio Gordo

Status:    Done

Confirmed by me through Checkuser Tool as the LTA meta:User:Vhaslhv, block indefinitely on pt.wiki and now vandalizing on pt.wikivoyage --EVinente (talk) 23:26, 1 June 2017 (UTC)

Done. RadiX 00:13, 2 June 2017 (UTC)

Global lock for many LTA socks

Status:    Done

Confirmed via CU on en.wiki. Presumably a mix of two masters. Probably some underlying IPs worthy of global blocks. --Ks0stm (TCGE) 15:39, 2 June 2017 (UTC)

Yes check.svg DoneDefender (talk) 16:54, 2 June 2017 (UTC)

Global lock for Cato

Status:    Done

Globally banned user --2602:306:36D5:5690:E521:BF30:6BF9:581D 22:03, 1 June 2017 (UTC)

Yes check.svg Done Ruslik (talk) 09:33, 3 June 2017 (UTC)

Global lock for 影武者(Nipponese Dog Calvero)

Status:    Done

--Lanwi1(Talk) 12:24, 2 June 2017 (UTC)

Yes check.svg Done.--HakanIST (talk) 06:40, 3 June 2017 (UTC)

Global lock for Dineshkumar510

Status:    Done

Spam only account --Zaenon (talk | contribs | CentralAuth) 02:41, 3 June 2017 (UTC)

Done by Tegel. RadiX 06:54, 3 June 2017 (UTC)

Global lock/unlock for Crouch, Swale

Status:    Not done

User with extensive history of sockpuppetry; en:Category:Wikipedia sockpuppets of Crouch, Swale has more than eight hundred members. A quick check of a few random members of the category (Barnes Wood, Church Farmhouse, E555587, Dorridge, and Fr229839) shows that all of them are locked, but the master account isn't locked. Just between these five socks and the master, we have blocks at simple:en (master), pl (Barnes Wood), nl (Dorridge), and en (all of them)I can't imagine why we'd ever lock a lot of sockpuppets (it looks like all of them have been locked) but not the master, unless someone just made a mistake and forgot to lock the master. --Nyttend (talk) 14:24, 3 June 2017 (UTC)

The user is unblocked and productively contributing on Commons. Until they decide that they don't want him around anymore, it wouldn't be appropriate for the account to be locked. – Ajraddatz (talk) 22:16, 3 June 2017 (UTC)

Global lock for 影武者(Nipponese Dog Calvero)

Status:    Done

--Lanwi1(Talk) 12:24, 2 June 2017 (UTC)

Yes check.svg Done.--HakanIST (talk) 06:40, 3 June 2017 (UTC)

Global unlock for Lorachiu

Status:    In progress

This user already blocked on jawiki. The reason are outsid