New to the list, however there is a master ticket open w/Sprint (TK#2172676) for a fiber cut in DC. Verizon was dispatched to the site, in which they supposedly had to gain authorization from the Railroad to even work on the facilities with an on-site time of Noon Central. Sprint did not provide an ETA and stated they would be unable to do so until Verizon reported back. All of their Miami traffic was in turn routed via Orlando to Atlanta, etc. We have two DS3's in Tallahassee (Fed from Orlando), Florida and a Gigabit connection in Atlanta and all of the above have been and are still affected by the transition. This apparently affected their DC <-> Miami operations. Hope this helps! Kraig On 5/12/08, Alan Halachmi <alan@halachmi.net> wrote:

I'm seeing a significant slowdown between Atlanta and Orlando. Anyone else?

1 ... 2 ... 3 ... 4 ... 5 ... 6 POS5-1.GW4.NYC4.ALTER.NET (157.130.14.177) 10 ms 15 ms 33 ms 7 146.at-2-0-0.XR3.NYC4.ALTER.NET (152.63.25.98) 26 ms 4 ms 4 ms 8 0.so-4-0-2.XL3.NYC4.ALTER.NET (152.63.17.29) 3 ms 3 ms 3 ms 9 0.ge-6-1-0.BR3.NYC4.ALTER.NET (152.63.3.166) 4 ms 3 ms 4 ms 10 sl-crs2-nyc-0-1-2-0.sprintlink.net (144.232.18.237) 4 ms 23 ms 17 ms 11 sl-crs1-pen-0-4-5-0.sprintlink.net (144.232.20.142) 21 ms 27 ms 23 ms 12 sl-bb21-rly-15-0.sprintlink.net (144.232.20.208) 25 ms 24 ms 17 ms 13 sl-bb21-dc-5-0-0.sprintlink.net (144.232.8.164) 31 ms 33 ms 28 ms 14 sl-crs1-dc-0-4-0-0.sprintlink.net (144.232.15.13) 45 ms 54 ms 50 ms 15 sl-crs1-atl-0-8-0-1.sprintlink.net (144.232.8.146) 291 ms 283 ms 285 ms 16 sl-bb21-orl-2-0.sprintlink.net (144.232.20.87) 500 ms 525 ms * 17 sl-bb20-orl-15-0.sprintlink.net (144.232.0.98) 489 ms 489 ms 489 ms 18 sl-gw12-orl-8-0.sprintlink.net (144.232.2.178) 487 ms 486 ms 486 ms

Best, Alan

_______________________________________________ NANOG mailing list NANOG@nanog.org http://mailman.nanog.org/mailman/listinfo/nanog