Steward requests/Checkuser

From Meta, a Wikimedia project coordination wiki
Jump to navigation Jump to search
Requests and proposals Steward requests (Checkuser) latest archive
Checkuser icons
These indicators are used by CheckUsers and stewards for easier skimming of their notes, actions and comments.
{{Confirmed}}:  Confirmed {{MoreInfo}}: MoreInfo Additional information needed
{{Likely}}: Likely Likely {{Deferred}}: Deferred Deferred to

{{Possible}}: Possible Possible {{Completed}}: Completed Completed
{{Unlikely}}: Unlikely Unlikely {{TakeNote}}: Note Note:
{{Unrelated}}: Unrelated Unrelated {{Doing}}: Symbol wait.svg Doing...
{{Inconclusive}}: Inconclusive Inconclusive {{StaleIP}}: Stale
{{Declined}}: Declined Declined {{Fishing}}: Fishing CheckUser is not for fishing
{{Pixiedust}}: Pixiedust CheckUser is not magic pixie dust {{8ball}}: 8ball The CheckUser Magic 8-Ball says
{{Duck}}:  It looks like a duck to me {{Crystalball}}: Crystalball CheckUser is not a crystal ball

This page is for requesting CheckUser information on a wiki with no local CheckUsers (see also requesting checkuser access). Make sure to follow the following instructions, or your request may not be processed in a timely manner.

Before making a request:

  1. Make sure you have a good reason for the check. It will only be accepted to counter vandalism or disruption to Wikimedia wikis. Valid reasons include needing a block of the underlying IP or IP range, disruptive sockpuppetry, vote-stacking, and similar disruption where the technical evidence from running a check would prevent or reduce further disruption.
  2. Be specific in your reasons. Ambiguous or insufficient reasons will cause delays. Explain the disruption and why you believe the accounts are related, ideally using diff links or other evidence.
  3. Make sure there are no local checkusers or policies.
  4. Please ensure that the check hasn't already been done:

How to make a request

How to make a request:

  • Place your request at the bottom of the section, using the template below (see also {{srcu}} help).
    === Username@xx.project ===
    {{CU request
     |status          = <!--don't change this line-->
     |language code   = 
     |project shortcut= 
     |user name1      = 
     |user name2      = 
     |user name3      = 
    <!-- Max 10 users -->
     |discussion      = [[Example]]<!-- local confirmation link / local policy link -->
     |reason          = Reasons here. ~~~~

    For example:

    === Example@en.wikipedia ===
    {{CU request
     |status          = <!--don't change this line-->
     |language code   = en
     |project shortcut= w
     |user name1      = Example
     |user name2      = Foo
     |user name3      = Bar
    <!-- Max 10 users -->
     |discussion      = [[:w:en:Example]]<!-- local confirmation link / local policy link -->
     |reason          = Reasons here. ~~~~
  • Specify the wiki(s) you want to perform the check on.
Cross-wiki requests
Meta-Wiki requests



  • no proper local discussion was done for this case yet, request to be placed on hold. --Cohaf (talk) 19:28, 11 September 2018 (UTC)
  • Meta CU is used to only confirm a connection once behavioral evidence has been established, not to be used to see if there is technical evidence that connects these accounts, which is often not so reliable on its own. If there aren't any administrators taking action, perhaps behavioral wise it's not that similar in the first place. Alex Shih (talk) 09:47, 12 September 2018 (UTC)
    • exactly my point conveyed at zhwiki, I temporarily placed this on hold pending further discussion--Cohaf (talk) 11:10, 12 September 2018 (UTC)
For the references, I expect at least more than two or three days of discussion on non-urgent case, and (usually) do check if the discussion is mature enough. — regards, Revi 14:39, 15 September 2018 (UTC)
@-revi and Alex Shih:update: accounts duck blocked, but local sysop request a sleeper check. I don't have the rationale for the check yet.--Cohaf (talk) 12:50, 18 September 2018 (UTC)
If you are clear with what I'm talking about, local discussion hasn't ever been stopped for nearly half a month; in conclusion the discussion is not only "mature enough" but on the edge of turning stale. Moreover, different people and communities have different points of view of what is "Urgent" and what is not. I didn't mean to urge anyone, but please avoid turning CheckUser process into a marathon. --Super Wang on zhwiki (Share your opinions) 09:07, 18 October 2018 (UTC)
@-revi:as of now the master had made an unblock request for the local sysop duck block to be overturned, so now the CU results are crucial. please expedite based on this and I am now endorsing this request formally for the record.--Cohaf (talk) 16:35, 18 October 2018 (UTC)
Hey, (as an excuse) these days I have more work in real life, but this should've got done by few weeks ago, and I will do it tomorrow night (KST), unless someone beats me. — regards, Revi 16:45, 18 October 2018 (UTC)
Thanks -revi,--Cohaf (talk) 02:08, 19 October 2018 (UTC)
Thank you. We are waiting for your reply. --Super Wang on zhwiki (Share your opinions) 08:11, 20 October 2018 (UTC)
Actually Symbol wait.svg Doing... — regards, Revi 08:12, 20 October 2018 (UTC)

Completed, sorry for the delay:

  •  Confirmed: A48498039, Ajack881215
  • Likely Likely to A48498039 group: 李如芯
  • Possible Possible to A48498039 group: A0123456a6695[1], Leo19991101[1], Jun1024, Sonylovef44, H125536198
  • A0953258578a was Stale at the time of submission to SRCU. (Stale as of September 8, 2018)

Bolded usernames are not in the original request.


  1. a b No contributions, but timing and technical details are suspicious

— regards, Revi 08:36, 20 October 2018 (UTC)

  • Thanks -revi, will report back .--Cohaf (talk) 08:39, 20 October 2018 (UTC)


See also[edit]