93.44.188.218 (talk⁺ · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser(log) · investigate · cuwiki)

• 93.44.188.218 (talk⁺ · tag · contribs · filter log · WHOIS · RBLs · proxy check · block user · spi block · block log · cross-wiki contribs · CheckUser (log))
• User compare report Auto-generated every hour.
• Editor interaction utility

https://en.wikipedia.org/w/index.php?title=User:WildChild666/sandbox&action=history and editing same topics https://en.wikipedia.org/wiki/Special:Contributions/WildChild666 Mlpearc (open channel) 17:51, 16 September 2016 (UTC)[reply]

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

• Ip blocked for 10 days, master warned. Vanjagenije (talk) 16:00, 17 September 2016 (UTC)[reply]

• 93.44.188.218 (talk⁺ · tag · contribs · filter log · WHOIS · RBLs · proxy check · block user · spi block · block log · cross-wiki contribs · CheckUser (log))
• 93.34.112.218 (talk⁺ · tag · contribs · filter log · WHOIS · RBLs · proxy check · block user · spi block · block log · cross-wiki contribs · CheckUser (log))
• User compare report Auto-generated every hour.
• Editor interaction utility

Both Italian editors use the same ISP (Fastweb) in Bologna. The editors both modify band member sections almost exclusively. Please compare edits. 93.44.188.218 was blocked for one month on 2016-09-21, so this is block evasion. Walter Görlitz (talk) 06:04, 6 October 2016 (UTC)[reply]

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

• Both IPs are blocked. Case closed. Vanjagenije (talk) 22:46, 10 October 2016 (UTC)[reply]

• 93.34.112.218 (talk⁺ · tag · contribs · filter log · WHOIS · RBLs · proxy check · block user · spi block · block log · cross-wiki contribs · CheckUser (log))
• User compare report Auto-generated every hour.
• Editor interaction utility

Editing behaviour: unexplained and unsupported changes to band articles has resulted in blocks and continues after the block is lifted. WP:DUCK test is easily passed. Particularly since the anon edited the sock's sandbox, was blocked for this behaviour and then continues with the behaviour. Another month-long block is in order. Walter Görlitz (talk) 06:33, 10 January 2017 (UTC)[reply]

WildChild666 is not blocked, but the editor should be reminded to edit while logged in. I also suspect that the editor won't do so because the editor may be afraid of being blocked, as the IPs have, because the edits do not comply with WP:V and are generally unexplained. At the very least, the editor should be asked to declare all alternate IPs and own those edits. Walter Görlitz (talk) 15:03, 11 January 2017 (UTC)[reply]

93.34.112.218 (talk) was recently blocked for the edit problems. If there is reason to believe that all of these are the same editors, the block may need to extend to all three. 208.81.212.224 (talk) 16:24, 11 January 2017 (UTC)[reply]

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

@Walter Görlitz: When 93.34.112.218 edited User:WildChild666/sandbox, WildChild666 and the IP had an edit war. That makes it seem unlikely to me they're the same user. Why would WildChild666 edit war with his own sock? If there's better evidence that connects them, please post it in the form of diffs. NinjaRobotPirate (talk) 01:46, 14 January 2017 (UTC)[reply]

•  IP blocked, closing. GAB^gab 17:42, 14 January 2017 (UTC)[reply]

IP was blocked for other reasons, but NinjaRobotPirate's point is taken. Walter Görlitz (talk) 22:59, 14 January 2017 (UTC)[reply]

• 93.149.45.180 (talk⁺ · tag · contribs · filter log · WHOIS · RBLs · proxy check · block user · spi block · block log · cross-wiki contribs · CheckUser (log))
• User compare report Auto-generated every hour.
• Editor interaction utility

Editing behaviour: changes to band timelines. WP:DUCK test is easily passed. Editor reverted many of the edits I reverted by 93.34.112.218. Both 93.34.112.218 and 93.149.45.180 reference Encyclopaedia Metallum frequently. Walter Görlitz (talk) 14:37, 10 January 2017 (UTC)[reply]

WildChild666 is not blocked, but the editor should be reminded to edit while logged in. I also suspect that the editor won't do so because the editor may be afraid of being blocked, as the IPs have, because the edits do not comply with WP:V and are generally unexplained. At the very least, the editor should be asked to declare all alternate IPs and own those edits. Walter Görlitz (talk) 15:03, 11 January 2017 (UTC)[reply]

Could it be that this IP and the one above, whom I also mistook for WildChild666, are the same editor and are both unrelated to WildChild666? In which case, we have a case of an anonymous editor who is editing from two different locations. Now that the other editor is blocked, if this IP goes active, we may have block evasion. Walter Görlitz (talk) 23:05, 15 January 2017 (UTC)[reply]

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

 Administrator note Yeah, it looks like the IP editors are the same person. Besides a large overlap in articles edited, they edit war to restore the same content: [1]/[2], [3]/[4]. Since the first one has been blocked for three months, I'll block this one, too. I don't think there's enough evidence to tie either IP to WildChild666. NinjaRobotPirate (talk) 15:24, 17 January 2017 (UTC)[reply]

• 93.44.80.218 (talk⁺ · tag · contribs · filter log · WHOIS · RBLs · proxy check · block user · spi block · block log · cross-wiki contribs · CheckUser (log))

• User compare report Auto-generated every hour.
• Editor interaction utility

IP was reported at AIV by Walter Görlitz as a suspected sock. Please see WildChild666/sandbox and User talk:93.44.80.218. Appears to be identical methods. — Maile (talk) 19:48, 16 November 2017 (UTC)[reply]

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Thanks for moving this here. It's on my watchlist which is why I noticed it. I do suspect that they are socks and debated opening an SPI earlier (and would appreciate advice for the next time the Italian timeline editor returns) but decided to wait until the editor reached four warnings and go the AIV route. It does make more sense here. If the SPI does not materialize. notice that the editor has been warned four times for adding unsourced information about band members and could be blocked for that behaviour. Walter Görlitz (talk) 21:08, 16 November 2017 (UTC)[reply]

This case is being reviewed by Sir Sputnik as part of the clerk training process. Please allow them to process the entire case without interference, and pose any questions or concerns either on their Talk page or on this page if more appropriate.

•  Clerk declined - CheckUser evidence cannot be used to connect a registered account to an IP address. Sir Sputnik (talk) 20:13, 16 November 2017 (UTC)[reply]
•  Awaiting administrative action - Please block the IP for disruptive behaviour and evading the block against 93.34.112.218 (talk · contribs · WHOIS). This is pretty clearly the same person operating the IP's previously reported here, but are unlikely to be WildChild666. I think we should rename the case to reflect this fact, but I'm unsure of the naming conventions for IP only cases. Ping Vanjagenije as the clerk most involved in this case. Sir Sputnik (talk) 20:54, 18 November 2017 (UTC)[reply]

(edit conflict) Hold on. This block is a matter of disruptive editing, not block evasion. The other IP you listed (93.34.112.218 (talk · contribs · WHOIS)) hasn't been blocked nor edited since April 2017. It's likely the same person, but if you cannot assert with confidence that this IP is the user account, then the IP is not evading a block. I'd have to revoke talk page access, as this is the place the IP's been editing. ~Oshwah~^{(talk) (contribs)} 21:05, 18 November 2017 (UTC)[reply]

Never mind. I'm a nim rod; the 6 month block placed on the other IP totally overlaps with the edits that started with this one. Please don't ask how I got that math wrong... :-) ~Oshwah~^{(talk) (contribs)} 21:10, 18 November 2017 (UTC)[reply]

It is  Done. ~Oshwah~^{(talk) (contribs)} 21:13, 18 November 2017 (UTC)[reply]

@Oshwah: I'm sorry should have specified this, but I think the block should be quite a bit longer than just a day and half. The block they were evading was for six months for example. This person has also been using this IP since at least the end of August, so the risk of collateral damage should be minimal. Sir Sputnik (talk) 21:03, 18 November 2017 (UTC)[reply]

•  On hold - Pending procedural questions. Sir Sputnik (talk) 18:59, 19 November 2017 (UTC)[reply]
• With the procedural questions resolved, I'm closing the case. Sir Sputnik (talk) 01:25, 23 November 2017 (UTC)[reply]

• 93.149.45.180 (talk⁺ · tag · contribs · filter log · WHOIS · RBLs · proxy check · block user · spi block · block log · cross-wiki contribs · CheckUser (log))
• User compare report Auto-generated every hour.
• Editor interaction utility

https://en.wikipedia.org/w/index.php?title=User_talk:93.44.80.218&curid=55076752&diff=811423292&oldid=810992526 ISP is the same as recently blocked. Likely not WildChild666 but is the most recently blocked IP. Please block for six months and extend other IP to match. Would a range block be appropriate? Walter Görlitz (talk) 16:48, 21 November 2017 (UTC)[reply]

I requested page protection of 93.44.80.218's talk page and admin elected to extend block. This SPI may be closed unless a range block is preferred. Walter Görlitz (talk) 20:29, 21 November 2017 (UTC)[reply]

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

This case is being reviewed by Sir Sputnik as part of the clerk training process. Please allow them to process the entire case without interference, and pose any questions or concerns either on their Talk page or on this page if more appropriate.

• IP blocked by Favonian. Closing. Sir Sputnik (talk) 01:47, 22 November 2017 (UTC)[reply]