Dear Colleagues, With this email I would like to give you an update on the current coverage of abuse-c in the RIPE Database, for your reference the last update we gave you was sent to this list in the end of April (http://www.ripe.net/ripe/mail/archives/anti-abuse-wg/2013-April/002244.html). -------- NETWORK NUMBERS: Total Number of v4 allocations listed: 20,735 Number of v4 allocations covered with abuse-c: 8,283 or 39.9% of v4 allocations Total Number of v4 PI assignments listed: 28,654 Number of v4 PI assignments covered with abuse-c: 1,091 or 3.8% of v4 assignments Total Number of v6 allocations listed: 5,773 Number of v6 allocations covered with abuse-c: 2,343 or 40.6% of v6 allocations Total Number of v6 assignments: 1,426 Number of v6 assignments covered with abuse-c: 133 or 9.3% of v6 assignments Total Number of objects: 56,588 (IPv4: 49,389 IPv6: 7,199) Number of objects covered with abuse-c: 11,850 or 20.9% (IPv4: 19.0% IPv6: 34.4%) -------- IPv4 NETWORK SIZES: Total size of v4 allocation listed: 594,471,936 Size of v4 allocations covered with abuse-c: 244,133,888 or 41.1% Total size of v4 PI assigned listed: 169,812,536 Size of v4 PI assigned covered with abuse-c: 12,077,344 or 7.1% Total size of listed v4 addresses: 764,284,472 Size of listed v4 addressed covered with abuse-c: 256,211,232 or 33.5% From this we can see that the current abuse-c coverage for IPv4 allocations is at 41.1%, up from 31.3% as reported in the end of April. For more information about these figures please see the link above to Kaveh's previous mail and if you have any further questions feel free to contact me. We just finished sending out the first batch of reminders and are currently busy with preparing the next set. In the beginning of July we will inform about the consequences of not adding the abuse-c and hopefully that will give increased attention. Kind regards, Johan Åhlén Assistant Database Team Manager RIPE NCC Database Team