[snip]
ASnum NetsNow NetsAggr NetGain % Gain Description
AS18566 751 6 745 99.2% CVAD Covad Communications [snip]
not to justify the expense, but perhaps covad is renumbering from one block to another? Looking at their advertisments I see lots of /23 or /24 blocks inside their larger covering routes... So either they deaggregated to renumber more gracefully, or they forgot their prefix-list outbound to williams and exodus ?
perhaps covad can explain? or silently cover up the 'mistake' (which is acceptable as well...)
I've been secretly hoping no one would notice Covad's ascension to the number one spot (which we've held for well over a month now ;). I actually made it through the last NANOG without a single mention of Covad's route bloat! There are no mistakes or excuses here. And there's definitely no renumbering going on. We were actually fully aggregated until an unfortunate incident this past May involving a distant service provider leaking our specifics. Gigs of traffic somehow vanished into Eastern Europe. The net result was deaggregation. It's unlikely we will aggregate down to less than 10 netblocks again. However, we do make every effort to aggregate where possible. Our superblocks are also being advertised, for those of you that want to filter our routes. Want to discuss further? Great. Call me or email me directly. Contact info is below. Think you can do it better? Even better. It turns out I'm hiring. :) Regards, Brad -- Covad Communications 408-434-2048 broldan@covad.com
geoff, your proggy already knows what filter list(s) would keep us from carrying the polluters' rubbish. any chance you could generate the filter code for juniper, procket, and cisco so automated router builds could fetch it with batch wget or ncftp or whatever? another cutie would be if whovever is maintaining peval this week could add an option to not deliver covered prefixes from the same origin? no slur intended on any particular polluter. but i think what we have here is the strafing of the commons. enough is enough. randy
thanks brad :) atleast some answer was provided. On Fri, 12 Nov 2004, Roldan, Brad wrote:
There are no mistakes or excuses here. And there's definitely no renumbering going on.
We were actually fully aggregated until an unfortunate incident this past May involving a distant service provider leaking our specifics. Gigs of traffic somehow vanished into Eastern Europe. The net result was deaggregation.
so, because someone 'hijacked' your more specifics you deaggregated entirely? Makes the 'everyone should prefix filter customers' talk sound more relevant everyday.
participants (3)
-
Christopher L. Morrow -
Randy Bush -
Roldan, Brad