(EC, yes, I didn't and don't know the range and used the history of edits).
DoRD and DeltaQuad, I think you misunderstand my comment and use CU scan to get range contributions from IPs. This is adequate for SPI cases or hard rangeblocks, but not for IP contributions, because those can be extracted from publicly available logs with a proper script, without and time and length limitations of CU logs (sorry if I'm telling the obvious, but ..). To imagine such a script, look here . When this script was hosted at the Toolserver, results were paginated by sets 50, and their number was enough for many months long evaluation. (I don't recall any limit there. Then the Toolserver died, and the results got limited to 30. We've lost functionality in many, many Toolserver tools, but this can be recovered, I believe.)