Hello,
I'm very sorry to use this list for this purpose, but I need a clueful
person at BBN who has dealings with the old Genuity network to contact me.
We're seeing paths like this to nearly everywhere on BBN-announced space,
and we have not been able to get this fixed for over a week:
(this is just one of many examples, but I thought the pure entertainment
value would keep Randy from browbeating me)
This is to a recent verio partner. It is my understanding that verio
peers with bbn and that bbn does not buy transit from sprint for this
purpose. Traffic to uu, cw, you-name-it takes similar paths. We are in
NYC.
Tracing the route to www.nyct.net (204.141.86.3)
(NYC to NYC)
1 fa10-0.nyccolo-border1.bbnplanet.net (207.240.48.45) [AS 3847] 4 msec
0 msec 4 msec
2 f6-0.nyccolo-core1.bbnplanet.net (207.240.1.81) [AS 3847] 4 msec 0
msec 0 msec
3 128.11.124.54 [AS 3847] 80 msec 84 msec 80 msec
4 sl-gw11-ana-6-0-0.sprintlink.net (144.228.207.145) [AS 1239] 92 msec
96 msec 88 msec
5 sl-bb12-ana-0-3.sprintlink.net (144.232.1.61) [AS 1239] 88 msec 92
msec 100 msec
6 sl-gw7-ana-8-0-0.sprintlink.net (144.232.1.38) [AS 1239] 108 msec 92
msec 88 msec
7 sl-atmn-1-0-0.sprintlink.net (144.228.79.14) [AS 1239] 112 msec 112
msec 108 msec
8 lax00.nuq0.verio.net (129.250.2.197) [AS 2914] 104 msec 116 msec 104
msec
9 nuq0.pao5.verio.net (129.250.3.9) [AS 2914] 104 msec 100 msec 100 msec
10 pao5.dca0.verio.net (129.250.2.246) [AS 2914] 172 msec 172 msec 176
msec
11 dca0.iad3.verio.net (129.250.2.61) [AS 2914] 168 msec 168 msec 168
msec
12 iad3.phl00.verio.net (129.250.3.106) [AS 2914] 184 msec 172 msec 176
msec
13 phl00.phl02.verio.net (129.250.3.154) [AS 2914] 172 msec 176 msec 176
msec
14 phl02.nyc1.verio.net (129.250.3.126) [AS 2914] 180 msec 176 msec 176
msec
15 nyc0.new-york.net (129.250.16.210) [AS 2914] 196 msec 196 msec 220
msec
16 nyc1.new-york.net (165.254.27.1) [AS 3384] 216 msec 216 msec 204 msec
17 nyct-gw.new-york.net (204.141.247.202) [AS 3384] 204 msec 232 msec 204
msec
18 www.nyct.net (204.141.86.3) [AS 3384] 240 msec 220 msec 192 msec
and a view from the other end:
1 gw1 (204.141.86.1) 1.716 ms 1.985 ms 1.647 ms
2 nyc1.new-york.net (204.141.247.53) 6.680 ms nyc1.new-york.net (204.141.247.201) 45.256 ms nyc1.new-york.net (204.141.247.53) 4.348 ms
3 nynet.nyc2.verio.net (129.250.16.253) 17.068 ms 15.114 ms 4.134 ms
4 nyc2.ord2.verio.net (129.250.3.133) 80.155 ms 65.077 ms 105.167 ms
5 ord2.bbn.verio.net (129.250.9.58) 83.454 ms 74.323 ms 48.674 ms
6 p2-3.chicago1-nbr1.bbnplanet.net (4.0.1.205) 30.023 ms 28.376 ms 44.516 ms
7 p2-1.paloalto-nbr2.bbnplanet.net (4.24.7.18) 94.908 ms 93.209 ms 100.024 ms
8 p6-2.lsanca1-br2.bbnplanet.net (4.24.5.205) 108.497 ms 101.718 ms 102.779 ms
9 p7-0.lsanca1-ba2.bbnplanet.net (4.24.4.37) 112.947 ms 102.288 ms 104.770 ms
10 p1-0-0.lsanca1-bp1.bbnplanet.net (4.24.5.182) 137.716 ms 115.041 ms 105.331 ms
11 s0-0-0.phnyaz2-cr1.bbnplanet.net (4.24.4.70) 137.202 ms 125.529 ms 120.528 ms
12 fa8-1-0.phxcolo-core2.bbnplanet.net (4.1.110.238) 115.923 ms 126.025 ms 110.862 ms
13 128.11.124.53 (128.11.124.53) 205.543 ms 198.474 ms 190.957 ms
14 f12.border1.nyc1.genuity.net (207.240.1.82) 203.052 ms 254.448 ms 201.596 ms
15 ptp-46.100fe10-0.nyc1.genuity.net (207.240.48.46) 242.274 ms 207.217 ms 233.641 ms
16 covad-dsl-eth0.telehouse.inch.com (207.240.128.21) 210.980 ms 286.533 ms 259.133 ms
17 sdsl-interface-130-208.dsl.inch.com (207.240.208.130) 274.182 ms 270.452 ms 264.278 ms
18 zeus.7nt.com (207.240.214.2) 289.261 ms 265.979 ms *
I am livid, is this any way to run a tier 1 network? More and more often,
I find myself (the customer who is supposed to know less) pointing out
gross errors to these folks. Sorry to vent.
Charles