Thanks to Ed Kern for leaving up his route-servers:
Query: bgp
Addr: 206.79.0.0
BGP routing table entry for 206.79.0.0/16, version 10807499
Paths: (2 available, best #1, advertised over IBGP)
3967
209.185.9.157 (metric 35) from 165.117.1.17 (165.117.1.71)
Origin IGP, metric 2000000000, localpref 100, valid, internal, best
Community: 2548:666
Originator : 165.117.1.71, Cluster list: 0.38.227.186, 165.117.1.71
3967
209.185.9.157 (metric 35) from 165.117.1.35 (165.117.1.71)
Origin IGP, metric 2000000000, localpref 100, valid, internal
Community: 2548:666
Originator : 165.117.1.71, Cluster list: 0.38.227.186, 165.117.1.71
Query: bgp
Addr: 12.0.0.0
BGP routing table entry for 12.0.0.0/8, version 5520488
Paths: (3 available, best #2, advertised over IBGP)
7018, (aggregated by 7018 12.127.1.122)
165.117.1.122 (metric 3) from 165.117.1.122
Origin IGP, localpref 100, valid, internal, atomic-aggregate
Community: 2548:666
Originator : 165.117.1.122, Cluster list: 165.117.1.122
7018, (aggregated by 7018 12.127.1.122)
192.41.177.3 from 192.41.177.3 (192.205.31.162)
Origin IGP, localpref 100, valid, external, atomic-aggregate, best
Community: 2548:666
1 7018, (aggregated by 7018 12.127.1.122)
198.32.186.2 from 198.32.186.2 (4.0.0.10)
Origin IGP, metric 230, localpref 100, valid, external, atomic-aggregate
Community: 2548:666
The top query is an Exodus query, as you can see Digex only sees it from
the Exodus PXs. The bottom query is AT&T's 12.0.0.0/8, which is not only
seen directly from 7018 (AT&T) but from AS1 (the Planet). That is transit.
I'd show you from BBN's route server, but it doesn't prove anything since
it is a RRC, and wouldn't show the longer as-path's anyways.
Rob
Exodus