North American Network Operators Group
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: Cogent/Level 3 depeering

  • From: Tom Sands
  • Date: Fri Oct 07 16:13:28 2005 
Yeah, we just noticed the same..

BGP routing table entry for 38.0.0.0/8, version 23735501
Paths: (3 available, best #1, table Default-IP-Routing-Table)
Flag: 0x220
 Advertised to peer-groups:
    core
 Advertised to non peer-group peers:
 64.39.2.107 212.100.225.49
 3356 174, (received & used)
   195.50.112.205 from 195.50.112.205 (4.68.0.240)
     Origin IGP, metric 0, localpref 100, valid, external, best
     Community: 3356:3 3356:86 3356:575 3356:666 3356:2010



Charles Gucker wrote:
On 07 Oct 2005 19:00:46 +0000, Paul Vixie <[email protected]> wrote:

[email protected] (Charles Gucker) writes:


Ok, as I understand it, Level3 can get Cogent connectivity back
simply be restoring the peering that they suspended, right?

First off, that's not my quote. ;-)  Second, it would appear routes
are once again beng exchanged between Level(3) and Cogent.

BGP routing table entry for 209.244.0.0/14, version 103309841
Paths: (1 available, best #1, table Default-IP-Routing-Table)
 Not advertised to any peer
 174 3356, (aggregated by 3356 4.68.0.12)
   66.28.1.1 from 66.28.1.1 (66.28.1.1)
     Origin IGP, metric 1000, localpref 100, valid, external,
atomic-aggregate, best
     Community: 174:21000 16631:1000


From an outside view, it seems like Level(3) caved in to customer
demand, but what the true outcome is, nobody will know [publically].

charles


that's what this press release says:

http://www.cogentco.com/htdocs/press.php?func=detail&person_id=62

disclaimer-- my employer has friendly relations with both Level(3) and Cogent.
--
Paul Vixie



--
------------------------------------------------------
Tom Sands
Chief Network Engineer
Rackspace Managed Hosting (210)447-4065
------------------------------------------------------