Chicago Amazon

Lyle Giese lyle at lcrcomputer.net
Sun Dec 7 17:45:45 UTC 2014


Interesting traceroute from Comcast in Chicago:

Goes from Chicago to Seattle to New York inside the Comcast network.

Lyle Giese
LCR Computer Services, Inc.

traceroute to www.amazon.com (176.32.98.166), 30 hops max, 40 byte 
packets using UDP
  1  lancomcast.lcrcomputer.com (192.168.250.252)  0.165 ms   0.142 ms   
0.139 ms
  2  c-98-206-192-1.hsd1.il.comcast.net (98.206.192.1)  9.226 ms 15.067 
ms   13.166 ms
  3  te-0-3-0-13-sur03.mchenry.il.chicago.comcast.net (68.85.131.5) 
12.778 ms   11.690 ms   10.688 ms
  4  te-2-3-0-1-ar01.elmhurst.il.chicago.comcast.net (68.86.197.165) 
16.734 ms te-2-3-0-0-ar01.elmhurst.il.chicago.comcast.net 
(69.139.235.109)  16.518 ms te-3-1-ur01.mchenry.il.chicago.comcast.net 
(68.87.210.61)  19.275 ms
  5  he-1-6-0-0-11-cr01.seattle.wa.ibone.comcast.net (68.86.92.33) 
18.112 ms   12.269 ms   14.449 ms
  6  be-10406-cr01.350ecermak.il.ibone.comcast.net (68.86.84.210) 19.087 
ms   18.882 ms   17.678 ms
  7  be-10206-cr01.newyork.ny.ibone.comcast.net (68.86.86.225) 35.173 
ms   34.970 ms   36.902 ms
  8  c-eth-0-2-0-pe04.111eighthave.ny.ibone.comcast.net (68.86.87.98)  
34.642 ms   34.394 ms   33.321 ms
  9  50.242.148.122 (50.242.148.122)  36.920 ms   35.969 ms   33.625 ms
10  54.240.229.84 (54.240.229.84)  33.564 ms   32.941 ms   36.129 ms
11  54.240.228.186 (54.240.228.186)  43.054 ms 54.240.228.204 
(54.240.228.204)  42.900 ms 54.240.228.202 (54.240.228.202)  41.204 ms
12  54.240.229.219 (54.240.229.219)  45.652 ms 54.240.229.221 
(54.240.229.221)  45.447 ms 54.240.229.223 (54.240.229.223)  44.213 ms
13  54.240.228.163 (54.240.228.163)  40.113 ms 54.240.228.161 
(54.240.228.161)  43.994 ms 54.240.228.181 (54.240.228.181)  43.778 ms
14  205.251.244.99 (205.251.244.99)  43.681 ms 205.251.244.91 
(205.251.244.91)  42.487 ms   46.121 ms
15  205.251.245.232 (205.251.245.232)  43.837 ms   43.749 ms 
205.251.245.226 (205.251.245.226)  43.723 msOn 12/07/14 10:24, Mike 
Hammett wrote:
> Is anyone else seeming issues reaching Amazon through Zayo in Chicago?
>
> 8 37 ms 44 ms 27 ms 64.125.204.11.allocated.above.net [64.125.204.11]
> 9 28 ms 13 ms 44 ms ge-11-1-2.mpr2.ord6.us.above.net [64.125.172.81]
> 10 28 ms 46 ms 27 ms ae11.cr2.ord2.us.above.net [64.125.22.130]
> 11 95 ms 34 ms 41 ms ae11.cr1.ord2.us.above.net [64.125.20.245]
> 12 41 ms 54 ms 34 ms ae4.er1.ord7.us.above.net [64.125.28.50]
> 13 * * * Request timed out.
> 14 * * * Request timed out.
> 15 * * * Request timed out.
>
>
>
> Looks like HE is having difficulty as well.
>
> 7 	20.243 ms 	21.120 ms 	19.500 ms 	72.21.220.175 205.251.244.93 72.21.220.183
> 8 	97.293 ms 	21.906 ms 	22.774 ms 	205.251.245.242 72.21.222.157 205.251.245.53
> 9 	* 	* 	* 	-
> 10 	* 	* 	* 	-
> 11 	* 	* 	* 	-
>
>
>
> Well, I guess unless they're dropping ICMP...
>
>
>
> -----
> Mike Hammett
> Intelligent Computing Solutions
> http://www.ics-il.com
>
>
>




More information about the NANOG mailing list