This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/

[db-wg] source: field for non RIPE address space

Previous message (by thread): [db-wg] source: field for non RIPE address space
Next message (by thread): [db-wg] source: field for non RIPE address space

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Edward Shryane eshryane at ripe.net
Thu Nov 20 15:03:49 CET 2014

Hi Job,

I checked all route objects in the RIPE database, against the delegated stats file for each region, and found which region the (IPv4) address space belongs in.

RIPE: 185,537
ARIN: 7,609
AFRINIC: 37,683
LACNIC: 1,930
APNIC: 2,004

Regards

Ed Shryane
RIPE NCC


> On 20 Nov 2014, at 14:17, Job Snijders <job at instituut.net> wrote:
> 
> On Fri, Nov 14, 2014 at 10:32:36PM +0100, Job Snijders wrote:
>> Can RIPE NCC provide more information on how many route objects have
>> been created that do not belong to RIPE NCC administrated space or ERX
>> space?
>> 
>> I did find ~ 12.000, but that was only because of that specific
>> "mnt-by:" attribute. If people remove that attribute, as an external
>> observer I cannot find the foreign route objects easily.
> 
> *bump*
>

Previous message (by thread): [db-wg] source: field for non RIPE address space
Next message (by thread): [db-wg] source: field for non RIPE address space

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]