Meta:Requests for CheckUser information

This page allows you to request CheckUser information on Meta.

Please read the CheckUser policy before asking for a check.
When adding new requests, please use the {{checkuser}} template to list the user names in question and {{checkip}} for IP addresses, which simplifies investigation.
List your request at the bottom of the "Requests for Meta-Wiki only" heading.
When asking for a check we need to know:
- why do you believe that the accounts are related (please present evidence for that with the help of diffs, etc.),
- why, if the accounts are related, they are being used abusively, in violation of policy; and
- why a block or other measures can't be justified without the need of technical evidence.

Local checkusers
Note: To request checkuser access, see Steward requests/Permissions.
Note: To request information for other wikis, see Steward requests/Checkuser.

Checkuser icons
These indicators are used by CheckUsers and stewards for easier skimming of their notes, actions and comments.
{{Confirmed}}: Confirmed	{{MoreInfo}}: Additional information needed
{{Likely}}: Likely	{{Deferred}}: Deferred to
{{Possible}}: Possible	{{Completed}}: Completed
{{Unlikely}}: Unlikely	{{TakeNote}}: Note:
{{Unrelated}}: Unrelated	{{Doing}}: Doing...
{{Inconclusive}}: Inconclusive	{{StaleIP}}: Stale
{{Declined}}: Declined	{{Fishing}}: CheckUser is not for fishing
{{Pixiedust}}: CheckUser is not magic pixie dust	{{8ball}}: The CheckUser Magic 8-Ball says
{{Duck}}: It looks like a duck to me	{{Crystalball}}: CheckUser is not a crystal ball

SpBot archives all sections tagged with {{Section resolved|1=~~~~}} after 1 day.

Requests for Meta-Wiki only

Obvious ducks making trollish requests. The first three have already been blocked on other wikis. Please check for sleepers. NguoiDungKhongDinhDanh 08:15, 11 July 2026 (UTC)[reply]

all Confirmed and block some socks. There were just way too many accounts, so I skipped blocking the ones that are already locked.--Infinite0694 (Talk) 20:35, 12 July 2026 (UTC)[reply]

Fairly obvious ducks: Both created user pages to claim to have permissions they don't have (IntergYT, Wibl8). Please check for sleepers and perform range blocks as necessary. NguoiDungKhongDinhDanh 19:15, 12 July 2026 (UTC)[reply]

Obvious ducks. The first is linked to the second and the fourth because of this kowiki edit, the second's username and these edits on lvwiki. The third is linked to that group because of these edits on kowiki. Please compare the first three against the fourth and the group right above, check for sleepers and perform range blocks as necessary. NguoiDungKhongDinhDanh 11:06, 14 July 2026 (UTC)[reply]

Obvious ducks: Same naming scheme as those caught in #Lithauen. Please check for sleepers and perform range blocks as necessary. NguoiDungKhongDinhDanh 08:42, 15 July 2026 (UTC)[reply]

Confirmed + block some socks. AramilFeraxa (talk) 09:07, 15 July 2026 (UTC)[reply]

Confirmed - already locked. — xaosflux ^Talk 09:51, 15 July 2026 (UTC)[reply]

Very similar usernames. The first have been locked for cross-wiki vandalism (see also #IntergYT). Please compare them and, if they are the same, check for sleepers. NguoiDungKhongDinhDanh 17:26, 17 July 2026 (UTC)[reply]

Done Locked for lock evasion.

Confirmed through LWCU. A09|(pogovor) 20:20, 17 July 2026 (UTC)[reply]

Both created userpages that are essentially the same as Wibl9's (see #Wibl9). Please check for sleepers and perform range blocks as necessary. NguoiDungKhongDinhDanh 02:35, 18 July 2026 (UTC)[reply]