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 Date filed Last user to edit case timestamp Last clerk/checkuser to edit case timestamp
Argumentdebate CU requested 2019-04-21 17:46 UTC Serial Number 54129 2019-04-21 17:49 UTC
SolomonV2 CU completed 2019-04-01 10:14 UTC Timotheus Canens 2019-04-18 00:21 UTC Timotheus Canens 2019-04-18 00:21 UTC
Colors of Colors CU completed 2019-04-06 16:24 UTC Berean Hunter 2019-04-14 16:38 UTC Berean Hunter 2019-04-14 16:38 UTC
Sivakarthy CU completed 2019-04-07 16:36 UTC Berean Hunter 2019-04-10 17:04 UTC Berean Hunter 2019-04-10 17:04 UTC
Lm945 CU completed 2019-04-13 00:16 UTC Berean Hunter 2019-04-14 16:29 UTC Berean Hunter 2019-04-14 16:29 UTC
Ck4829 CU completed 2019-04-20 15:53 UTC Levivich 2019-04-21 16:43 UTC Berean Hunter 2019-04-21 14:23 UTC
Dr Samkiv Kumar CU completed 2019-04-21 06:31 UTC Ajraddatz 2019-04-21 17:40 UTC Berean Hunter 2019-04-21 14:09 UTC
Abdelkader123456 Open 2019-03-23 01:22 UTC Bbb23 2019-04-19 14:58 UTC Bbb23 2019-04-19 14:58 UTC
Jaswanthvijay Open 2019-04-16 17:00 UTC Cabayi 2019-04-16 17:00 UTC Cabayi 2019-04-16 17:00 UTC
Batdigitalmeda Open 2019-04-17 21:06 UTC Dreamy Jazz 2019-04-18 12:00 UTC
WillPleasant123 Open 2019-04-19 12:19 UTC 1997kB 2019-04-19 12:24 UTC 1997kB 2019-04-19 12:24 UTC
Ec1801011 Open 2019-04-20 10:20 UTC Pudeo 2019-04-20 23:16 UTC DoRD 2019-04-20 13:52 UTC
Abraham nomura Open 2019-04-21 02:28 UTC GeneralizationsAreBad 2019-04-21 13:58 UTC GeneralizationsAreBad 2019-04-21 13:58 UTC
180.191.154.60 Open 2019-04-21 13:36 UTC Moxy 2019-04-21 13:36 UTC
Jahmalm Open 2019-04-21 13:47 UTC Wumbolo 2019-04-21 13:47 UTC
Torpilorul Declined 2019-03-02 20:09 UTC TonyBallioni 2019-04-21 01:07 UTC TonyBallioni 2019-04-21 01:07 UTC
Arsi786 Declined 2019-04-02 15:52 UTC Sir Sputnik 2019-04-02 22:49 UTC Sir Sputnik 2019-04-02 22:49 UTC
Halosine Declined (CU) 2019-04-14 17:16 UTC Aman.kumar.goel 2019-04-18 11:01 UTC TonyBallioni 2019-04-16 02:36 UTC
FilmLover2016 Declined (CU) 2019-04-16 16:28 UTC Bbb23 2019-04-17 17:43 UTC Bbb23 2019-04-17 17:43 UTC
Jvm21 Declined (CU) 2019-04-19 18:18 UTC Bbb23 2019-04-19 23:50 UTC Bbb23 2019-04-19 23:50 UTC
Itsxerox Awaiting admin 2019-04-21 08:48 UTC Cabayi 2019-04-21 10:56 UTC Cabayi 2019-04-21 10:56 UTC
Awillis75 On hold (CU) 2019-04-03 18:41 UTC TheSandDoctor 2019-04-03 19:07 UTC DeltaQuad 2019-04-03 18:59 UTC
Vishnu suryakanth panchal On hold (CU) 2019-04-07 14:45 UTC JJMC89 2019-04-20 06:01 UTC Bbb23 2019-04-07 17:18 UTC
KibaTheWolf96 Closed 2019-04-07 16:35 UTC Sir Sputnik 2019-04-20 22:29 UTC Sir Sputnik 2019-04-20 22:29 UTC
Lagoo sab Closed 2019-04-07 22:53 UTC Ajraddatz 2019-04-21 17:42 UTC Bbb23 2019-04-21 13:45 UTC
Oreratile1207 Closed 2019-04-19 20:13 UTC Cabayi 2019-04-20 07:06 UTC Cabayi 2019-04-20 07:06 UTC
Moylesy98 Closed 2019-04-20 09:33 UTC Cabayi 2019-04-20 14:41 UTC Cabayi 2019-04-20 14:41 UTC
BushidoBrown Closed 2019-04-21 01:36 UTC GeneralizationsAreBad 2019-04-21 13:38 UTC GeneralizationsAreBad 2019-04-21 13:38 UTC
GTA5Player Closed 2019-04-21 02:03 UTC GeneralizationsAreBad 2019-04-21 13:17 UTC GeneralizationsAreBad 2019-04-21 13:17 UTC
Ramskq Closed 2019-04-21 05:18 UTC Doc James 2019-04-21 06:01 UTC 1997kB 2019-04-21 05:59 UTC
Selim Shaikh Closed 2019-04-21 08:52 UTC Cabayi 2019-04-21 13:29 UTC Cabayi 2019-04-21 13:29 UTC
Dopenguins Closed 2019-04-21 12:57 UTC Berean Hunter 2019-04-21 13:26 UTC Berean Hunter 2019-04-21 13:26 UTC
Astore Malik Closed 2019-04-21 14:06 UTC Sir Sputnik 2019-04-21 17:01 UTC Sir Sputnik 2019-04-21 17:01 UTC
Manda 1993 Closed 2019-04-21 17:29 UTC Vanjagenije 2019-04-21 17:29 UTC Vanjagenije 2019-04-21 17:29 UTC

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 emergency@wikimedia.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}}

Navboxes