You are here: Home > Publications > RIPE Labs > Robert Kisteleki > Interesting Graph - RIPE DB Objects

Interesting Graph - RIPE DB Objects

Robert Kisteleki — Jun 2010
This graph shows how the number of various RIPE Database objects evolved over time, in particular domain, intenum, route and aut_num objects.


The graph above shows how the number of different RIPE DB objects evolved over time. It only shows "operationally important" object types for now, but we are planning to add persons, roles, and the rest a bit later.


Anonymous says:
25 Jun, 2010 02:36 PM

The discontinuity in the graphs drew my attention. Like... the number of asblocks went from something like 500 to 2000 overnight.


It will be interesting to see what happens with inetnum objects after IPv4 exhaustion. Will we see fragmentation of address space resulting in more of these, or consolidation resulting in less? Or neither, as everyone moves to IPv6 overnight? ;)

Anonymous says:
29 Jun, 2010 02:35 PM

Last year IANA updated their lists of blocks of AS Numbers assigned to which registry. They took into account the early registration transfers (ERX) that have happened over recent years. For each ERX, a previous contiguous block of assignments became three assignment blocks. Even if it was only one single AS Number in the middle of the block that had moved. The RIPE NCC then re-synchronised the RIPE Database with this new information. Then as you pointed out, overnight there was a big increase in the number of AS-BLOCK objects.

Anonymous says:
08 Jul, 2010 11:15 AM

There is a proposal right now within the RIPE PDP, 2010-02, Allocations from the last /8.

We have published an Impact Analysis just recently, and part of it is about fragmentation that is anticipated as an impact of this proposed policy. The analysis reads the following:


"...Compared to the current global routing table statistics as reported in , the number of prefixes would go up by 5% when all 16,384 allocations have been handed out. This growth could come in two stages. In the first stage we could see a rapid increase in a relatively short time when the threshold of the last /8 is reached and existing LIRs matching the criteria each apply for a /22. In the second stage, we could see the extra growth happen more gradually while new entrants join the RIPE NCC and apply for their /22 of IPv4..."


[The equivalent of a /8 will accommodate 16,384 allocations of a size /22, which is the allocation size proposed in 2010-02]


You can find the full proposal and the analysis at:


Filiz Yilmaz

Policy Development Manager


Add comment

You can add a comment by filling out the form below. Comments are moderated so they won't appear immediately. If you have a RIPE NCC Access account, we would like you to log in.