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.
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.
Make sure there are no local checkusers or policies.
How come this new user can create a lot of edit. Isn`t there a limit for new user edit? Yosri (talk) 22:38, 10 April 2014 (UTC)
If there is a limit, then it wasn't editing fast enough to trigger it. There is a main IP being used which has now been autoblocked, though like QU said above they are using a couple of IPs. I'll email you the main IP to block if you wish. Ajraddatz (talk) 23:07, 10 April 2014 (UTC)
Let me consult with another admin. Tq for your assistant. Yosri (talk) 05:44, 11 April 2014 (UTC)
I agree the main IP should be properly blocked. An autoblock doesn't last very long. ...Aurora... (talk) 15:24, 11 April 2014 (UTC)
Locked these three. Unfortunately an IP block isn't stopping them. Ajraddatz (talk) 23:12, 14 April 2014 (UTC)
Thank you for your assistant. As we (MS) have no checkuser, I will update here as and when it happen. Your assistant in blocking the IP is much appreciated. What will happen, will happen. Yosri (talk) 01:43, 15 April 2014 (UTC)
The master accounts are probably stale, but the new sock (SHIROKABE) is showing a pattern consistent with the others (cross-wiki hat collecting and copy/pasting).--Jasper Deng (talk) 07:27, 17 April 2014 (UTC)
Request withdrawn, behavorial evidence was strong enough.--Jasper Deng (talk) 07:56, 17 April 2014 (UTC)