Hey, anyone who wanna help improve the net stability?

Without pointing fingers, there are some 9K prefixes that could be
removed by proper aggregation/reconfiguration.

There are also 25,000 /24's, up 20% from six months ago. I don't
have any figures on how many are in the "swamp", but I think this
is the most fruitful place to try to cap growth or hack it back:

Total routes: 39670

8 22 0.1%
9 1 0.0%
10 4 0.0%
11 6 0.0%
12 14 0.0%
13 30 0.1%
14 102 0.3%
15 173 0.4%
16 5687 14.3%
17 246 0.6%
18 493 1.2%
19 921 2.3%
20 954 2.4%
21 1200 3.0%
22 1824 4.6%
23 2425 6.1%
24 25539 64.4%
...

Hi Paul,

you comment leaves me confused. 25,000 24s up 20% in the last six months
means 5,000 NEW prefix 24s in the global routing tables. Where did they
come from? I ask because I had thought that it was just about impossible
to get a 24 routed at the nets defaultless core. And that this
impossibility has been around for at least the last 6 months.

I thought that if "cooknet" as a new MCI customer has a 24 handed to it by
mci all nice and cidrized that "cooknet's" 24 would never appear in your
list being aggregated by mci along with other 24s to make a smaller prefix
that would be announced eventually in the global tables? Have I
misunderstood something or is theory diverging from practice.