Yep me too. C:\Users\HTS-DVR>tracert www.amazon.com
Tracing route to www.amazon.com [205.251.242.54] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 10.10.1.1 2 3 ms 3 ms 2 ms 172.31.1.2 3 2 ms 1 ms 10 ms 10.10.2.13 4 9 ms 6 ms 20 ms 172.28.2.1 5 10 ms 9 ms 9 ms 10.10.254.1 6 10 ms 9 ms 13 ms static133-block97.intelleqcom.net [64.19.97.133] 7 20 ms 13 ms 19 ms lag-8-329.ear1.Dallas1.Level3.net [4.31.137.145] 8 54 ms 50 ms 51 ms vlan60.csw1.Dallas1.Level3.net [4.69.145.62] 9 59 ms 47 ms 46 ms ae-63-63.ebr3.Dallas1.Level3.net [4.69.151.134] 10 * * * Request timed out. 11 52 ms 57 ms 49 ms ae-2-2.ebr1.Washington1.Level3.net [4.69.132.86] 12 48 ms 49 ms 59 ms ae-61-61.csw1.Washington1.Level3.net [4.69.134.1 30] 13 49 ms 45 ms 49 ms ae-1-60.edge3.Washington1.Level3.net [4.69.149.1 7] 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete. > dying at L3 for us. > > > [image: Inline image 1] > > > Robbie Wright > Siuslaw Broadband <http://siuslawbroadband.com> > 541-902-5101 > > **For support issues, please email [email protected].** > > > On Fri, Feb 21, 2014 at 3:46 PM, Dj Padzensky <[email protected]> wrote: > >> >> No problems in East King County, WA. >> >> traceroute to www.amazon.com (205.251.242.54), 64 hops max, 52 byte >> packets >> 1 * gw (192.168.1.1) 1.424 ms 0.733 ms >> 2 10.60.128.1 (10.60.128.1) 9.041 ms 8.490 ms 11.409 ms >> 3 24-113-43-225.wavecable.com (24.113.43.225) 8.609 ms 8.934 ms >> 11.994 ms >> 4 24-113-43-30.wavecable.com (24.113.43.30) 11.154 ms 10.728 ms >> 14.028 ms >> 5 24-113-43-34.wavecable.com (24.113.43.34) 14.343 ms 11.580 ms >> 10.602 ms >> 6 24-113-43-93.wavecable.com (24.113.43.93) 14.553 ms 15.583 ms >> 16.086 ms >> 7 agg2-sea-b-p200.bb.spectrumnet.us (216.243.24.93) 13.873 ms 16.139 >> ms 13.539 ms >> 8 xe-0-5-0-3.r04.sttlwa01.us.bb.gin.ntt.net (198.104.202.17) 14.380 >> ms >> 13.713 ms 15.128 ms >> 9 ae-6.r20.sttlwa01.us.bb.gin.ntt.net (129.250.5.42) 15.613 ms >> 28.168 >> ms 14.479 ms >> 10 ae-5.r21.snjsca04.us.bb.gin.ntt.net (129.250.3.39) 39.677 ms >> ae-0.r20.sttlwa01.us.bb.gin.ntt.net (129.250.2.53) 13.502 ms >> 42.304 >> ms >> 11 ae-5.r21.dllstx09.us.bb.gin.ntt.net (129.250.4.24) 73.945 ms >> ae-5.r21.snjsca04.us.bb.gin.ntt.net (129.250.3.39) 30.644 ms >> 32.001 >> ms >> 12 ae-2.r08.dllstx09.us.bb.gin.ntt.net (129.250.3.81) 80.939 ms >> 73.379 >> ms >> ae-5.r21.dllstx09.us.bb.gin.ntt.net (129.250.4.24) 74.897 ms >> 13 ae-2.amazon.dllstx09.us.bb.gin.ntt.net (129.250.201.158) 63.314 ms >> ae-1.amazon.dllstx09.us.bb.gin.ntt.net (129.250.201.154) 65.644 ms >> 63.799 ms >> 14 54.240.229.106 (54.240.229.106) 99.587 ms >> ae-1.amazon.dllstx09.us.bb.gin.ntt.net (129.250.201.154) 68.553 ms >> 54.240.229.108 (54.240.229.108) 96.919 ms >> 15 54.240.229.14 (54.240.229.14) 109.246 ms >> 54.240.229.18 (54.240.229.18) 92.771 ms >> 54.240.229.104 (54.240.229.104) 97.733 ms >> 16 54.240.229.2 (54.240.229.2) 92.322 ms >> 54.240.229.16 (54.240.229.16) 94.506 ms >> 54.240.229.8 (54.240.229.8) 114.901 ms >> 17 54.240.229.174 (54.240.229.174) 91.388 ms * >> 54.240.229.170 (54.240.229.170) 99.532 ms >> 18 205.251.245.33 (205.251.245.33) 90.515 ms 92.953 ms >> 54.240.229.129 (54.240.229.129) 111.709 ms >> 19 205.251.245.33 (205.251.245.33) 95.427 ms >> 205.251.245.41 (205.251.245.41) 93.439 ms >> 205.251.245.121 (205.251.245.121) 109.442 ms >> 20 * * * >> >> --Dj >> >> On Feb 21, 2014, at 3:36 PM, [email protected] wrote: >> >> > Is anyone else seeing traffic routing all over the place trying to get >> to >> > Amazon.com? >> > >> > >> > Chris >> > >> > >> > _______________________________________________ >> > Outages mailing list >> > [email protected] >> > https://puck.nether.net/mailman/listinfo/outages >> >> _______________________________________________ >> Outages mailing list >> [email protected] >> https://puck.nether.net/mailman/listinfo/outages >> > _______________________________________________ Outages mailing list [email protected] https://puck.nether.net/mailman/listinfo/outages
