North American Network Operators Group|
Date Prev | Date Next |
Date Index |
Thread Index |
Author Index |
- From: Phil Rosenthal
- Date: Wed Sep 28 07:50:11 2005
For what it's worth, I'm seeing the following:
>show ip bgp 18.104.22.168
BGP routing table entry for 22.214.171.124/14, version 91507552
Paths: (6 available, best #2, table Default-IP-Routing-Table)
Advertised to update-groups:
126.96.36.199 from 188.8.131.52 (184.108.40.206)
Origin IGP, metric 100, localpref 90, valid, external
Community: 3356:3 3356:86 3356:575 3356:666 3356:2010
3356:666 - Peer route
3356:3 - North America
3356:575 - USA
3356:2010 - NYC - New York City
Perhaps this is back up as a paid peer? Perhaps they kissed and made
up? Perhaps XO asked to turn it back up for a short while they set up
transit? Who knows...
Also, doesn't 2828 have transit from 1239?
On Sep 28, 2005, at 1:24 AM, Alex Rubenstein wrote:
Appears to be.
XO's looking glass for BGP looking is broken (did it break today?),
however, traceroute shows:
1 ge5-3-0d4.RAR2.NYC-NY.us.xo.net (220.127.116.11) 0 msec 4 msec 4 msec
2 * * *
L3's looking glass:
Show Level 3 (San Jose, CA) BGP routes for 18.104.22.168
No matching routes found for 22.214.171.124.
On Wed, 28 Sep 2005, Richard A Steenbergen wrote:
Since it hasn't hit nanog yet, I guess I'll go ahead and go ahead
the first to point it out.
It seems that Level 3 (3356) and XO (2828) are no longer carrying
other's routes. :)
And just when I was about to release http://www.e-gerbil.net/ras/
Alex Rubenstein, AR97, K2AHR, firstname.lastname@example.org, latency, Al Reuben
Net Access Corporation, 800-NET-ME-36, http://www.nac.net