No. For example: /usr/local/bin/tcptraceroute 208.39.178.1 <snip> 9 208.173.53.138 54.790 ms 55.312 ms 55.207 ms 10 pos-0-9-0-0-cr01.losangeles.ca.ibone.comcast.net (68.86.85.186) 57.883 ms 57.948 ms 57.676 ms 11 pos-0-14-0-0-cr01.dallas.tx.ibone.comcast.net (68.86.85.142) 93.850 ms 94.420 ms 93.846 ms 12 pos-0-14-0-0-cr01.atlanta.ga.ibone.comcast.net (68.86.85.154) 112.976 ms 113.173 ms 113.260 ms 13 pos-0-11-0-0-cr01.mclean.va.ibone.comcast.net (68.86.85.242) 129.032 ms 129.078 ms 128.753 ms 14 pos-0-0-0-0-pe01.ashburn.va.ibone.comcast.net (68.86.86.26) 129.215 ms 129.142 ms 129.110 ms 15 ccs-pe01.ashburn.va.ibone.comcast.net (68.86.92.198) 136.825 ms 136.564 ms 136.844 ms 16 ge-11-0-cr01.phl.comcastcommercial.net (208.39.157.41) 142.110 ms 142.837 ms 142.407 ms 17 ge-3-1-br01.phl.comcastcommercial.net (208.39.156.2) 141.837 ms 142.068 ms 142.010 ms 18 208.39.178.1 [closed] 145.743 ms 145.467 ms 145.180 ms --- dnightin@wellesley.edu wrote: From: Don Nightingale <dnightin@wellesley.edu> To: "nanog@nanog.org" <nanog@nanog.org> Subject: GBLX I2 connection issues? Date: Tue, 03 Mar 2009 15:37:21 -0500 We're seeing packet loss getting to 208.39.178.0/23 over I2, anyone else seeing any issues? 1 * 207.210.142.2 212 msec 236 msec 2 ge5-3-0-1000M.ar1.SJC2.gblx.net (64.208.110.25) 4 msec 4 msec 4 msec 3 te9-3-10G.ar5.NYC1.gblx.net (67.16.131.109) 80 msec 208 msec 8 msec 4 * * * 5 * * * 6 * * * 7 * * * 8 -- Don Nightingale Systems and Networks Manager Wellesley College 781-283-3271