Permanently protected page

Wikipedia:Sockpuppet investigations

From Wikipedia, the free encyclopedia
  (Redirected from Wikipedia:SPI)
Jump to navigation Jump to search

Administrator instructions

If you suspect sock puppetry 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?

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 sock puppetry.

  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 sock puppetry 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 Filed at (UTC) Last user edit Last clerk/CU edit
User Time (UTC) User Time (UTC)
Vrahomarinaner CU completed 2019-11-02 13:06 Ivanvector 2019-11-02 13:06 Ivanvector 2019-11-02 13:06
Happinesskey CU completed 2019-11-06 19:55 UW Dawgs 2019-11-12 00:52 KrakatoaKatie 2019-11-11 17:26
Oluwa2Chainz CU completed 2019-11-18 23:11 Berean Hunter 2019-11-25 16:40 Berean Hunter 2019-11-25 16:40
AuthorWiki99 CU completed 2019-11-27 08:31 ST47 2019-11-27 21:20 ST47 2019-11-27 21:20
Dereks1x CU completed 2019-12-02 15:22 EvergreenFir 2019-12-02 20:08 Ivanvector 2019-12-02 18:59
TheLoanWalker CU completed 2019-12-04 04:06 Winged Blades of Godric 2019-12-04 17:52 Sro23 2019-12-04 04:09
Isabelle.ferreras.assistant CU completed 2019-12-04 07:49 Ivanvector 2019-12-05 16:30 Ivanvector 2019-12-05 16:30
Amfithea CU completed 2019-12-05 16:59 Berean Hunter 2019-12-05 18:53 Berean Hunter 2019-12-05 18:53
Mahbubur.bcd CU completed 2019-12-05 19:48 ST47 2019-12-05 20:26 ST47 2019-12-05 20:26
Skischduo Open 2019-12-04 15:24 Kb03 2019-12-04 15:24
JatBrand Open 2019-12-05 07:53 Zzuuzz 2019-12-05 07:53 Zzuuzz 2019-12-05 07:53
Datomicheal Open 2019-12-05 07:56 Zzuuzz 2019-12-05 07:56 Zzuuzz 2019-12-05 07:56
Nittin Das Open 2019-12-05 08:40 Begoon 2019-12-05 09:07
Brunodam Open 2019-12-06 00:18 Rosguill 2019-12-06 00:18
14 chiragjani Declined (CU) 2019-12-01 12:58 RoySmith 2019-12-04 19:21 Bbb23 2019-12-01 14:37
Bodiadub Closed 2019-10-06 21:53 ST47 2019-12-05 20:26 ST47 2019-12-05 20:26
BrookeCook Closed 2019-10-14 20:39 ST47 2019-12-05 20:27 ST47 2019-12-05 20:27
Frank marine Closed 2019-11-26 19:52 Mz7 2019-12-06 01:05 Mz7 2019-12-06 01:05
Vigilem Closed 2019-11-27 17:37 RoySmith 2019-11-30 01:02 ST47 2019-11-27 21:05
Benebimo Closed 2019-11-29 17:59 JJMC89 2019-11-30 06:31 JJMC89 2019-11-30 06:31
米記123 Closed 2019-12-03 07:04 Mz7 2019-12-04 01:27 Mz7 2019-12-04 01:27
Ramesmurmu214 Closed 2019-12-04 07:54 TheSandDoctor 2019-12-04 19:12 TheSandDoctor 2019-12-04 19:12
Agshin Abbasli Closed 2019-12-04 12:41 Mz7 2019-12-06 02:14 Mz7 2019-12-06 02:14
מוקהמוקה Closed 2019-12-04 14:05 TheSandDoctor 2019-12-04 15:51 TheSandDoctor 2019-12-04 15:51
Cosmin2005 Closed 2019-12-05 07:55 TheSandDoctor 2019-12-05 16:28 TheSandDoctor 2019-12-05 16:28
NoCal100 Closed 2019-12-05 17:09 Bbb23 2019-12-05 20:16 Bbb23 2019-12-05 20:16
WhiteStarG7 Closed 2019-12-05 17:20 TheSandDoctor 2019-12-05 17:22 TheSandDoctor 2019-12-05 17:22
Rtekleab Closed 2019-12-05 17:32 TheSandDoctor 2019-12-05 17:37 TheSandDoctor 2019-12-05 17:37
WhenDatHotlineBling Closed 2019-12-05 22:53 Zzuuzz 2019-12-05 23:15 Zzuuzz 2019-12-05 23:15
Soccer Refereeing Closed 2019-12-06 04:14 JJMC89 2019-12-06 04:16 JJMC89 2019-12-06 04:16

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 (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 ====
* {{Checkuser|