– This SPI case is closed and will be archived shortly by an
SPI clerk or
checkuser.
User is editing same pages as 49.3.90.25 and 49.3.90.116, which had previously been blocked for block evasion . Edits from 49.193.150.69 only began when these previous users were blocked. BryanGaensler ( talk) 21:57, 16 June 2024 (UTC)
Comparing these two diffs: edit by 49.193.150.69 and 49.3.90.25 (previous blocked IP), looks like he likes to 'neaten' up the table code by adding spaces where there isn't (for 49.193.150.69 diff, scroll down and look at 49, 50, 51 entries). — AP 499D25 (talk) 23:44, 17 June 2024 (UTC)
– This SPI case is closed and will be archived shortly by an
SPI clerk or
checkuser.
See also prior block logs for the following IPs: 220.236.126.177 110.175.242.146 220.236.119.43 49.3.90.116
This IP is only active on certain pages frequently edited by these previous ones, the most recent edit on the "2024 NRL Season" page is basically a carbon copy of previous edits made by 49.3.90.116. Obviously early days to be reporting this but anyone who's been involved with this guy's previous account/IPs should be able to recognise him. PhinsUp23 ( talk) 10:11, 21 June 2024 (UTC)
User:PhinsUp23, this particular IP user has already been reported above several days earlier, so I suggest checking this SPI page for an existing report before making one next time. Secondly, keep in mind that on an SPI, Checkusers can't use the Checkuser tool on IP addresses, they can only use it in account-to-account scenarios. Regards, — AP 499D25 (talk) 04:47, 22 June 2024 (UTC)