Hi Ulrich, | Here are the Statistics from today I mentioned on Abuse-C/IRT Thank you for indirectly pointing out an error in the SixXS software. | IPV6 Statistics 2004-05-06 | +----------+----------------------------+-------------------+----------+ | | TYPE | Number of IPs | Number of Objects | Handles | | +----------+----------------------------+-------------------+----------+ | | inetnum | 2.9e+31 (100.0%) [/23.5 ] | 5360 (100.0%) | 0 | | +----------+----------------------------+-------------------+----------+ | | irt | 4e+29 ( 1.4%) [/29.7 ] | 135 ( 2.5%) | 12 | | +----------+----------------------------+-------------------+----------+ | | abuse | 4.4e+29 ( 1.5%) [/29.5 ] | 3213 ( 59.9%) | 0 | | | abuse@ | 4.4e+29 ( 1.5%) [/29.5 ] | 3054 ( 57.0%) | 91 | | +----------+----------------------------+-------------------+----------+ I would have expected the IPv6 IRT usage to be much higher, because SixXS uses IRT in our software (and we are accountable for 3000 or so of the inet6num objects in the RIPE database). We only appear to use them in the allocated (/40) blocks, rather than in the assigned space to endusers. I've ammended the code so you can expect some 2800 or so objects to contain an IRT reference after the next iteration of our cronscript (once daily). Hopefully this sets an example for other IPv6 users. groet, Pim -- Met vriendelijke groet, BIT BV / Ing P.B. van Pelt PBVP1-RIPE (PGPKEY-4DCA7E5E)