My Comcast paths through 350 Cermak have cleared up just after 3:02 CST. Everything is now looking normal. Nate On 12/19/2011 3:11 PM, Nathan Owens wrote:

Looks like it has changed and is now going through 350 E. Cermak, still not the best possible route, but better than Miami I suppose:

1 192.168.1.1 (192.168.1.1) 7.576 ms 0.856 ms 1.265 ms 2 c-68-44-224-1.hsd1.de.comcast.net <http://c-68-44-224-1.hsd1.de.comcast.net> (68.44.224.1) 19.685 ms 21.179 ms 27.908 ms 3 xe-2-1-0-0-sur01.mtlaurel.nj.panjde.comcast.net <http://xe-2-1-0-0-sur01.mtlaurel.nj.panjde.comcast.net> (68.86.192.221) 10.252 ms 17.454 ms 10.343 ms 4 xe-3-1-0-0-ar03.audubon.nj.panjde.comcast.net <http://xe-3-1-0-0-ar03.audubon.nj.panjde.comcast.net> (68.85.62.113) 18.037 ms 59.058 ms 10.627 ms 5 pos-3-9-0-0-cr01.ashburn.va.ibone.comcast.net <http://pos-3-9-0-0-cr01.ashburn.va.ibone.comcast.net> (68.86.95.157) 14.195 ms pos-3-7-0-0-cr01.ashburn.va.ibone.comcast.net <http://pos-3-7-0-0-cr01.ashburn.va.ibone.comcast.net> (68.86.95.149) 15.625 ms pos-3-8-0-0-cr01.ashburn.va.ibone.comcast.net <http://pos-3-8-0-0-cr01.ashburn.va.ibone.comcast.net> (68.86.95.153) 24.694 ms 6 pos-0-11-0-0-cr01.newyork.ny.ibone.comcast.net <http://pos-0-11-0-0-cr01.newyork.ny.ibone.comcast.net> (68.86.85.14) 18.542 ms 36.333 ms 28.741 ms 7 pos-0-8-0-0-cr01.350ecermak.il.ibone.comcast.net <http://pos-0-8-0-0-cr01.350ecermak.il.ibone.comcast.net> (68.86.88.162) 54.815 ms 95.715 ms 59.833 ms 8 pos-1-5-0-0-pe01.350ecermak.il.ibone.comcast.net <http://pos-1-5-0-0-pe01.350ecermak.il.ibone.comcast.net> (68.86.87.126) 41.674 ms 55.666 ms 36.006 ms 9 as6453-pe01.350ecermak.il.ibone.comcast.net <http://as6453-pe01.350ecermak.il.ibone.comcast.net> (75.149.228.250) 35.988 ms 34.610 ms 33.615 ms 10 64.86.79.2 (64.86.79.2) 37.293 ms 35.158 ms 35.995 ms 11 vlan553.icore1.ct8-chicago.as6453.net <http://vlan553.icore1.ct8-chicago.as6453.net> (206.82.141.90) 75.580 ms 35.919 ms 43.436 ms 12 nyk-bb1-link.telia.net <http://nyk-bb1-link.telia.net> (80.91.248.193) 44.056 ms 68.856 ms 41.189 ms 13 ldn-bb1-link.telia.net <http://ldn-bb1-link.telia.net> (80.91.249.248) 118.435 ms ldn-bb1-link.telia.net <http://ldn-bb1-link.telia.net> (213.155.133.148) 108.704 ms ldn-bb1-link.telia.net <http://ldn-bb1-link.telia.net> (80.91.249.248) 120.341 ms 14 adm-bb1-link.telia.net <http://adm-bb1-link.telia.net> (80.91.250.84) 121.795 ms 120.292 ms 126.481 ms 15 adm-b4-link.telia.net <http://adm-b4-link.telia.net> (80.91.253.182) 122.003 ms 136.405 ms 117.161 ms 16 leaseweb-ic-129604-adm-b4.c.telia.net <http://leaseweb-ic-129604-adm-b4.c.telia.net> (213.248.91.222) 114.790 ms 112.027 ms 112.745 ms 17 po80.sr2.evo.leaseweb.net <http://po80.sr2.evo.leaseweb.net> (62.212.80.74) 123.989 ms 129.969 ms 119.358 ms 18 te5-1.sr6.evo.leaseweb.net <http://te5-1.sr6.evo.leaseweb.net> (85.17.129.214) 119.109 ms 181.580 ms 116.043 ms 19 95.211.44.41 (95.211.44.41) 119.680 ms 121.311 ms 118.049 ms

On Mon, Dec 19, 2011 at 8:51 PM, Nate Burke <nate@blastcomm.com <mailto:nate@blastcomm.com>> wrote:

From Within Chicago, still seeing issues. More specifically any comcast destined traffic going through 350 Cermac, latency stays constant at 160ms, but packetloss has significantly increased in last 30 min.

Nate

On 12/19/2011 2:39 PM, Adam Rothschild wrote:

This looks resolved from my prospectives as well. I'd imagine the Comcast folk on this list will be able to provide a more detailed RFO once the dust has settled and a root cause is known.

-a _______________________________________________ Outages mailing list Outages@outages.org <mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages

_______________________________________________ Outages mailing list Outages@outages.org <mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages