Wikipedia:Sockpuppet investigations

To request CheckUser in a case that does not involve sockpuppetry, please scroll down to Quick CheckUser requests.

If you suspect sockpuppetry by an administrator, or if you need to submit off-wiki evidence for some other reason, you must email the CheckUser team to open an investigation. Private information, emails, logs, and other sensitive evidence must not be posted on Wikipedia. All evidence related to a sockpuppet investigation must otherwise be posted on the designated page.
←What is a sockpuppet? What happens in an SPI?→

Sockpuppet investigations
Current cases Sockpuppetry policy
Information pages
Guide to filing cases Administrator instructions Signs of sockpuppetry
SPI clerk pages
List of clerks Noticeboard (archive 1, archive 2, archive 3) Procedures Training
SPI archives
Malformed cases (whitelist) Archived cases (historical)

This page is for requesting that we investigate whether two or more Wikipedia accounts are being abusively operated by the same person.

Before opening an investigation, you need good reason to suspect sockpuppetry.

1. Evidence is required. When you open the investigation, you must immediately provide evidence that the suspected sock puppets are connected. The evidence will need to include diffs of edits that suggest the accounts are connected. (This requirement is waived if the edits in question are deleted; in this case just provide the names of the pages that the accounts have been editing.)
2. You must provide this evidence in a clear way. Vaguely worded submissions will not be investigated. You need to actually show why your suspicion that the accounts are connected is reasonable.

Investigations are conducted by a clerk, who will compare the accounts' behaviour and determine whether they are probably connected; this is a behavioural evidence investigation. Upon request, investigations can also be conducted by a CheckUser, who can look at the physical location of the accounts (and other technical data) in order to determine how likely it is they are connected; this is a technical evidence investigation.

Due to Wikipedia's CheckUser policy, CheckUsers will conduct a technical investigation only if clear, behavioural evidence of sockpuppetry is also submitted; if you ask for technical evidence to be looked at but do not provide behavioural evidence, the investigation may not be allowed to proceed. Additionally, CheckUsers will not publicly connect an account with an IP address per the privacy policy except in extremely rare circumstances.

How to open an investigation:

To open an investigation (or case), enter the user name (or if there isn't one, IP address) of the oldest-created account (the "sockmaster"), or the previous case name, in the box below, then click "Submit". Note: Do not include "User:" or any other commentary. For example, if the case name is about User:John Doe or a prior case was at Wikipedia:Sockpuppet investigations/John Doe, you should enter John Doe in the box below. You will then be taken to another page containing a form you must complete to open the investigation. The process for opening a subsequent investigation on the same user is the same as for creating a new case. Again, do not include "User:" in any of the sock or ip fields. If you also wish a CheckUser to investigate, change |checkuser=no to |checkuser=yes in the edit box on the next page and explain why you are requesting it. Note: You can also open an investigation using Twinkle if you are autoconfirmed. After installing Twinkle, an "ARV" option will appear in the "TW" tab on any user, user talk, or user contributions page. Clicking on this option and selecting either "Sockpuppeteer" or "Sockpuppet" will allow you to fill in a few simple fields to file a report. The report will be automatically formatted for you. If you are an anonymous (IP address) editor, and the case page is protected or does not exist, please click "show" to the right and use the box below

Cases currently listed at SPI

Investigation	Status	Filer	Date filed	Last user edit	timestamp	Last clerk/CU edit
Bezoma	CU completed	Normal Op	Oct 18	AmandaNP	Oct 20 22h19 UTC	AmandaNP
BossMayhem2509	CU completed	UW Dawgs	Oct 18	AmandaNP	Oct 21 03h13 UTC	AmandaNP
Bothiman	CU completed	Praxidicae	Oct 10	L235	Oct 11 18h34 UTC	L235
CalebHughes	CU completed	UW Dawgs	Aug 15	AmandaNP	Oct 15 11h32 UTC	AmandaNP
CanadianBBQ	CU completed	DanielRigal	Oct 21	Derekbeagle	Oct 22 01h22 UTC	Oshwah
Dani Khoury	CU completed	Destroyeraa	Oct 11	AmandaNP	Oct 15 11h15 UTC	AmandaNP
DevilBlack69	CU completed	Bri.public	Sep 8	Ivanvector	Oct 7 15h07 UTC	Ivanvector
Haitypicky	CU completed	AleatoryPonderings	Oct 13	RoySmith	Oct 19 21h22 UTC	RoySmith
Hoaeter	CU completed	Gyrofrog	Sep 23	TheLionHasSeen	Oct 21 06h37 UTC	RoySmith
Jack Coppit	CU completed	The Four Deuces	Sep 23	AmandaNP	Oct 3 01h09 UTC	AmandaNP
Piznajko	CU completed	Ermenrich	Oct 8	Ermenrich	Oct 17 15h42 UTC	Guerillero
Speaktruth29	CU completed	Aman.kumar.goel	Oct 17	Aman.kumar.goel	Oct 22 05h16 UTC	Callanecc
Ultimate survi	CU completed	Boing! said Zebedee	Oct 14	Boing! said Zebedee	Oct 18 09h30 UTC	AmandaNP
Amrapahal Pahanswan	Endorsed	Fylindfotberserk	Aug 22	Fylindfotberserk	Oct 22 14h57 UTC	Dreamy Jazz
ArthurCurry70	Endorsed	Umakant Bhalerao	Sep 21	RoySmith	Oct 22 14h52 UTC	RoySmith
Agsfdet	CU requested	Conifer	Oct 22	Conifer	Oct 22 14h38 UTC
Mineraltimer	CU requested	Power~enwiki	Oct 21	Power~enwiki	Oct 21 03h52 UTC
Rajputro.nagaland	CU requested	Za-ari-masen	Oct 22	Za-ari-masen	Oct 22 09h49 UTC
Skoojal	CU requested	Genericusername57	Oct 8	Knowledge Contributor0	Oct 22 07h57 UTC
Vamsivemuru	CU requested	Amkgp	Oct 21	Amkgp	Oct 21 15h28 UTC
Authordom	Declined (CU)	TheAafi	Oct 21	Oshwah	Oct 22 01h10 UTC	Oshwah
Sportstir	Declined (CU)	Bilby	Oct 13	Bilby	Oct 21 12h19 UTC	AmandaNP
66.216.235.75	Open	Cyberlink420	Oct 20	Cyberlink420	Oct 20 00h01 UTC
82.132.217.158	Open	Viewmont Viking	Oct 21	Viewmont Viking	Oct 21 14h11 UTC
Ajhenson21	Open	119.93.40.241	Oct 20	Dreamy Jazz	Oct 20 19h09 UTC	Dreamy Jazz
Aveesh51	Open	DannyS712	Oct 18	DannyS712	Oct 18 18h22 UTC
BFAOVAF	Open	Muboshgu	Oct 21	Muboshgu	Oct 21 23h17 UTC
Dbug000	Open	Kj cheetham	Oct 19	Dreamy Jazz	Oct 19 19h05 UTC	Dreamy Jazz
FishMara	Open	Umakant Bhalerao	Oct 22	Umakant Bhalerao	Oct 22 14h55 UTC
JBiskingg	Open	Quisqualis	Oct 22	Quisqualis	Oct 22 05h28 UTC
Lindokuhle Modi	Open	Praxidicae	Oct 22	Praxidicae	Oct 22 12h37 UTC	Praxidicae
Reporter104	Open	GoldenDragonHorn	Oct 21	GoldenDragonHorn	Oct 21 17h06 UTC
Ruhaan Aditya	Open	KH-1	Oct 20	Materialscientist	Oct 21 07h38 UTC	Materialscientist
Skipperboy25080	Open	Aoi	Oct 22	Geraldo Perez	Oct 22 15h07 UTC
Wadamz	Open	Kb03	Oct 21	Kb03	Oct 21 19h22 UTC
Whippy7	Open	Livelikemusic	Aug 23	GeneralNotability	Oct 21 15h31 UTC	GeneralNotability
Xiang09	Open	Stricnina	Sep 27	Ivanvector	Oct 22 15h11 UTC	Ivanvector
Zenomonoz	Open	Genericusername57	Oct 8	Sxologist	Oct 12 21h29 UTC	Doug Weller
Zerolandteam385	Open	Mr.choppers	Oct 21	Mr.choppers	Oct 21 01h10 UTC
פארוק	Open	IamNotU	Oct 19	IamNotU	Oct 19 02h52 UTC
The Little Platoon	More info req.	Onetwothreeip	Oct 9	Onetwothreeip	Oct 21 01h32 UTC	AmandaNP
12.178.190.58	Closed	EDG 543	Oct 21	GeneralNotability	Oct 21 19h44 UTC	GeneralNotability
87.244.116.74	Closed	Thesupremewalrus	Oct 20	GeneralNotability	Oct 21 15h59 UTC	GeneralNotability
Icewhiz	Closed	Dreamy Jazz	Oct 4	RoySmith	Oct 22 14h33 UTC	RoySmith

Quick CheckUser requests

Use this section to request checkuser information relating to a situation that does not involve sock puppetry. You could use this section to request, for example: Underlying IPs of an account, where the autoblock has expired or been ineffective. Collateral damage checks for the informed hardblocking of IPs or ranges. IP block exemption checks before granting IPBE (or to verify it is being used constructively). For threats of harm (to self or others) you must email emergencywikimedia.org (see the threats of harm page) and not use this page. Requests to investigate and confirm sockpuppetry should be listed in the sockpuppet section above, and not here (such requests will be summarily removed). To make a request here, copy the following template and paste it to the end of this section (quick link to edit) – replacing "header" with an informative title, and adding underneath the template any relevant information – then sign using "~~~~", preview, and click "save". ==== HEADER ==== {{SPIquick}} * {{Checkuser|username}}