Tracert says it all.
Tracing route to 204.2.229.86 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 9 ms 9 ms 96.120.26.133
3 9 ms 9 ms 11 ms 96.110.155.169
4 12 ms 11 ms 11 ms 162.151.184.65
5 14 ms 15 ms 14 ms be-33491-cr01.chicago.il.ibone.comcast.net [68.86.92.33]
6 13 ms 15 ms 12 ms be-10506-cr02.350ecermak.il.ibone.comcast.net [68.86.86.229]
7 12 ms 20 ms 13 ms be-1302-cs03.350ecermak.il.ibone.comcast.net [96.110.36.105]
8 12 ms 11 ms 13 ms 96.110.37.26
9 21 ms 14 ms 14 ms ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
10 144 ms 144 ms 127 ms ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
11 11 ms 12 ms 13 ms ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
12 103 ms 102 ms 93 ms ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
13 126 ms 126 ms 113 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
14 92 ms 108 ms 100 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
15 139 ms 148 ms 137 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
16 88 ms 91 ms * 204.2.229.234
17 136 ms 125 ms 122 ms 204.2.229.86
Trace complete.
This is the same issue that cropped up a few weeks ago and lasted a couple of days. Repeated tracert show packetloss between ae-26 and ae-3 inside NTT's Chicago infrastructure.
Continue reading...
Tracing route to 204.2.229.86 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 9 ms 9 ms 96.120.26.133
3 9 ms 9 ms 11 ms 96.110.155.169
4 12 ms 11 ms 11 ms 162.151.184.65
5 14 ms 15 ms 14 ms be-33491-cr01.chicago.il.ibone.comcast.net [68.86.92.33]
6 13 ms 15 ms 12 ms be-10506-cr02.350ecermak.il.ibone.comcast.net [68.86.86.229]
7 12 ms 20 ms 13 ms be-1302-cs03.350ecermak.il.ibone.comcast.net [96.110.36.105]
8 12 ms 11 ms 13 ms 96.110.37.26
9 21 ms 14 ms 14 ms ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
10 144 ms 144 ms 127 ms ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
11 11 ms 12 ms 13 ms ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
12 103 ms 102 ms 93 ms ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
13 126 ms 126 ms 113 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
14 92 ms 108 ms 100 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
15 139 ms 148 ms 137 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
16 88 ms 91 ms * 204.2.229.234
17 136 ms 125 ms 122 ms 204.2.229.86
Trace complete.
This is the same issue that cropped up a few weeks ago and lasted a couple of days. Repeated tracert show packetloss between ae-26 and ae-3 inside NTT's Chicago infrastructure.
Continue reading...