Commons:Requests for checkuser
Shortcuts: COM:CHECK • COM:RFCU • COM:SOCK
This is the place to request investigations of abuse of multiple accounts or of other circumstances that require use of checkuser privileges.
Requesting a check
These indicators are used by CheckUsers to allow easier at-a-glance reading of their notes, actions and comments. | |
---|---|
Request completed | |
Confirmed | Technically indistinguishable |
Likely | Possilikely |
Possible | Unlikely |
Inconclusive | Unrelated |
No action | Stale |
Request declined | |
Declined | Checkuser is not for fishing |
Checkuser is not magic pixie dust. | The CheckUser Magic 8-Ball says |
It looks like a duck to me | Checkuser is not a crystal ball. |
Information | |
Additional information needed | Deferred to |
Doing… | Info |
Please do not ask us to run checks without good reason; be aware of the following before requesting a check:
- Checkuser is a last resort for difficult cases; pursue other options first, such as posting on the administrator's noticeboard. (This is not a venue for requesting administrative action such as blocks or file clean-up.)
- Running a check will only be done to combat disruption on Commons, or as required to assist checkuser investigations on other Wikimedia wikis.
- Valid reasons for running a check include, for example: vandalism where a block of the underlying IP or IP range is needed and suspected block evasion, vote-stacking, or other disruption where technical evidence would prevent or reduce further disruption.
- Requests to check accounts already confirmed on other projects may be declined as redundant.
- Requests to run a check on yourself will be declined.
- Evidence is required. When you request a check, you must include a rationale that demonstrates (e.g., by including diffs) what the disruption to the project is, and why you believe the accounts are related.
- Requests to run a check without evidence or with ambiguous reasoning will result in delays or the request not being investigated.
- The privacy policy does not allow us to make a check that has the effect of revealing IP addresses.
Outcome
Responses will be brief in order to comply with Wikimedia privacy policy. Due to technical limitations, results are not always clear. Closed requests are archived after seven days.
Privacy concerns
If you feel that a checkuser request has led to a violation of the Wikimedia Foundation privacy policy regarding yourself, please refer the case to the Ombuds commission.
If this page is displaying outdated contents even after you refresh the page in your browser, please purge this page's cache.
Requests[edit]
LIV2[edit]
- LIV2 (talk • contribs • Luxo's • SUL • deleted contribs • logs • block user • block log )
[edit]
- 166.48.119.67 (talk • contribs • 166.48.119.67/lookup WHOIS • 166.48.119.67.html RBL • tools • luxo's • 166.48.119.67 crossblock • block user • block log
Rationale, discussion and results[edit]
Reason:trying to get File:Fancy pants logo for Wikipedia.png kept, and continuing to delete the DR template while the [[1]] DR is open. The IP continues the trend. All the best -- Chuck Talk 23:00, 12 May 2024 (UTC)
- Declined - Please review COM:RFCU: "The privacy policy does not allow us to make a check that has the effect of revealing IP addresses." Эlcobbola talk 23:12, 12 May 2024 (UTC)
Theresadayog[edit]
- Theresadayog (talk • contribs • Luxo's • SUL • deleted contribs • logs • block user • block log )
[edit]
- Hellobracey (talk • contribs • Luxo's • SUL • deleted contribs • logs • block user • block log )
- TraceyRustia (talk • contribs • Luxo's • SUL • deleted contribs • logs • block user • block log )
Rationale, discussion and results[edit]
Reason: Similar behaviour; uploading the exact same copyrighted image that was deleted twice when uploaded by sockmaster few days back. — Paper9oll (🔔 • 📝) 16:06, 5 May 2024 (UTC)
- I also requested SPI on English Wikipedia, results (en:Wikipedia:Sockpuppet investigations/Theresadayog) came back that all are related to each other. I don't think any CU is required anymore on Commons hence may proceed to close this case. — Paper9oll (🔔 • 📝) 14:03, 6 May 2024 (UTC)
- Given cross-wiki results, I have blocked and tagged all of these accounts. This case page may be archived now. ─ Aafī (talk) 14:44, 6 May 2024 (UTC)
- Not done - Noting for posterity and clarity in case of future requests, as already marked as resolved. Indeed, except in cases of error, sister project CU findings are valid globally for SUL accounts. Эlcobbola talk 16:26, 12 May 2024 (UTC)
E333ter[edit]
- E333ter (talk • contribs • Luxo's • SUL • deleted contribs • logs • block user • block log )
[edit]
- Gtefer (talk • contribs • Luxo's • SUL • deleted contribs • logs • block user • block log )
Rationale, discussion and results[edit]
Reason: The former user, who is globally locked, posted in Russian Wikipedia an image used only for vandalism which was uploaded by the latter. Тай Лунг (talk) 06:25, 5 May 2024 (UTC)
- And the latter is to be globally locked as well as the former. 185.10.224.66 06:30, 5 May 2024 (UTC)
- @Тай Лунг: both now locked, this request is now moot. — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 13:49, 5 May 2024 (UTC)
- Not done - Noting for posterity and clarity in case of future requests, as already marked as resolved. Indeed, as per above, both accounts globally locked (E333ter as of, and Gtefer less than 13 minutes after, this request), so no CU needed to prevent disruption. Эlcobbola talk 16:24, 12 May 2024 (UTC)
A3cb1[edit]
- A3cb1 (talk • contribs • Luxo's • SUL • deleted contribs • logs • block user • block log )
[edit]
- Frederickos12 (talk • contribs • Luxo's • SUL • deleted contribs • logs • block user • block log )
Rationale, discussion and results[edit]
Same edit pattern as previous socks. 81.41.177.91 21:46, 7 May 2024 (UTC)
- Done --Krd 05:24, 9 May 2024 (UTC)
- For older requests, please see Commons:Requests for checkuser/Archives