I had my provider (Internap) test from their 111 N. Canal facility in Chicago, and latency did not exist from that NAP, only at 350 Ceramc, on all upstreams that Internap connects to at 350 Cermac. Looks like it might be a busy router at 350 Cermac on Comcast. Nate On 12/19/2011 12:28 PM, Bill McGonigle wrote:
On Mon, Dec 19, 2011 at 1:15 PM, Nate Burke<nate@blastcomm.com> wrote:
Started seeing High Latency and Packetloss on a Comcast Business Circuit in the far Western Chicago Suburbs. Started around 11:50am CST. Looks like it might be at a cross connect between ATT and Comcast downtown Chicago. I'm seeing this here in Lebanon NH, affecting cross-town traffic between Fairpoint and Comcast:
traceroute to 173.9.115.9 (173.9.115.9), 30 hops max, 60 byte packets 1 64.222.216.1 (64.222.216.1) 20.381 ms 21.252 ms 22.527 ms 2 pool-64-222-213-23.port.east.myfairpoint.net (64.222.213.23) 24.186 ms 25.071 ms 26.528 ms 3 xe-0-2-0.mpr4.bos2.us.above.net (64.124.202.29) 31.227 ms 32.431 ms 33.667 ms 4 xe-0-0-0.mpr3.bos2.us.above.net (64.125.25.61) 35.177 ms 36.522 ms 37.866 ms 5 xe-5-3-0.cr1.lga5.us.above.net (64.125.24.110) 45.022 ms 46.045 ms 46.985 ms 6 xe-0-0-0.cr2.lga5.us.above.net (64.125.29.42) 48.062 ms 29.675 ms 29.242 ms 7 xe-0-2-1.er2.lga5.us.above.net (64.125.30.210) 29.931 ms 30.970 ms 32.314 ms 8 above-comcast.lga5.us.above.net (64.125.12.210) 35.957 ms 36.227 ms 37.505 ms 9 pos-1-5-0-0-cr01.newyork.ny.ibone.comcast.net (68.86.85.17) 39.783 ms 43.557 ms 43.231 ms 10 pos-0-6-0-0-cr01.350ecermak.il.ibone.comcast.net (68.86.88.154) 62.634 ms 66.689 ms 66.438 ms 11 pos-1-6-0-0-cr01.chicago.il.ibone.comcast.net (68.86.88.41) 66.540 ms 67.105 ms 53.298 ms 12 * * * ...
My pager didn't ring until 12:06, and my logs are on the other side of the problem, but wow, I'm still seeing this now, going on 40 minutes by your time schedule.
-Bill