Similar- Boston to Chicago MCI- seeing high latency 6 3 ms 3 ms 3 ms 544.at-5-0-0.xr1.bos4.alter.net [152.63.24.222] 7 3 ms 3 ms 3 ms 0.so-4-0-0.xl1.bos4.alter.net [152.63.16.121] 8 91 ms 95 ms 95 ms 0.so-7-0-0.XL1.CHI6.ALTER.NET [152.63.65.161] 9 93 ms 95 ms 92 ms pos6-0.gw6.chi6.alter.net [152.63.68.97] 10 94 ms 81 ms 83 ms netlogic-gw.customer.alter.net [157.130.101.2] 11 87 ms 80 ms 89 ms 206-80-93-67.chi.netlogic.net [206.80.93.67] Trace complete. H:\> ________________________________ From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu] On Behalf Of Mike Hammett Sent: Monday, November 13, 2006 3:14 PM To: nanog@nanog.org Subject: MCI < - > Savvis in Chicago Anyone else seeing this? [root@ds00209 mhammett]# tcptraceroute 206.80.93.67 4569 Selected device eth0, address 205.218.65.34, port 54461 for outgoing packets Tracing the path to 206.80.93.67 on TCP port 4569, 30 hops max 1 205.138.198.193 0.444 ms 0.322 ms 0.319 ms 2 bpr2-ge-6-2-0-302.chicagoequinix.savvis.net (208.174.225.201) 0.411 ms 0.348 ms 0.330 ms 3 bpr1-ae0.ChicagoEquinix.savvis.net (208.174.226.85) 0.370 ms 0.403 ms 0.403 ms 4 208.174.226.26 30.460 ms 30.159 ms 29.601 ms 5 0.so-5-3-0.XL2.CHI2.ALTER.NET (152.63.64.58) 29.147 ms 28.063 ms 30.176 ms 6 0.so-6-0-0.XL2.CHI6.ALTER.NET (152.63.65.126) 32.394 ms 35.813 ms 35.976 ms 7 POS7-0.GW6.CHI6.ALTER.NET (152.63.68.189) 37.018 ms 36.800 ms 37.723 ms 8 netlogic-gw.customer.alter.net (157.130.101.2) 38.169 ms 41.228 ms 37.870 ms 9 206-80-93-67.chi.netlogic.net (206.80.93.67) [closed] 35.334 ms 33.460 ms 34.075 ms ---- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com