Wikipedia:Sockpuppet investigations/2602:30a:2e3e:dff0:846f:670:4726:86fc/Archive

19 October 2013

 * Suspected sockpuppets


 * User compare report Auto-generated every hour.
 * Editor interaction utility

Return of just-banned IP hopping Channel Awesome BLP troll. Doc StrangeMailbox Logbook 17:03, 19 October 2013 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''
 * I'd recommend a rangeblock on the /64 (2602:30A:2E3E:DFF0::/64). All of that range is owned and controlled by one user (because it is a home ISP).--Jasper Deng (talk) 19:18, 19 October 2013 (UTC)

Clerk, CheckUser, and/or patrolling admin comments

 * Blocked the /64 for a week. Closing. Legoktm (talk) 21:04, 19 October 2013 (UTC)

26 November 2013

 * Suspected sockpuppets


 * User compare report Auto-generated every hour.
 * Editor interaction utility

IP hopping vandal. All IPs start with "2602:30a:2e3e". Single-target vandalism of the Channel Awesome page, particularly BLP vandalism involving the site producer "Angry Joe" (see revision history). Every time user is blocked, they make a new IP. Only thing that's stopped them is the page being semi-protected. A previous sockpuppet report here ended with a suggestion of a range block, which was done for a week. Seems to have not stuck. Doc StrangeMailbox Logbook 04:12, 26 November 2013 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * Looks like a rangeblock might be a good idea here. I'm not very familiar with IPV6 rangeblocks, but I've blocked 2602:30a:2e3e:ed40::/64 for one month. Mark Arsten (talk) 04:56, 26 November 2013 (UTC)
 * I haven't looked at the range, but a /64 block should be fine - that is often the address space given to a single customer. ​—DoRD (talk)​ 14:52, 26 November 2013 (UTC)