On 01/31/13 14:57 -0500, Tim Glen wrote:
http://downforeveryoneorjustme.com/amazon.com
Doesnt happen too often...
It's down for me as well. ~$ traceroute amazon.com traceroute to amazon.com (72.21.211.176), 30 hops max, 60 byte packets 1 10.0.2.1 (10.0.2.1) 2.874 ms 3.055 ms 3.304 ms 2 olp-67-217-152-5.olp.net (67.217.152.5) 3.561 ms 3.801 ms 4.286 ms 3 router.olp.net (67.217.151.97) 2.069 ms 2.260 ms 2.466 ms 4 olp-67-217-152-34.olp.net (67.217.152.34) 3.979 ms 4.448 ms 4.700 ms 5 ae5-694.edge9.Dallas1.Level3.net (4.30.66.17) 10.744 ms 10.985 ms 11.236 ms 6 vlan80.csw3.Dallas1.Level3.net (4.69.145.190) 44.496 ms vlan60.csw1.Dallas1.Level3.net (4.69.145.62) 44.507 ms vlan70.csw2.Dallas1.Level3.net (4.69.145.126) 53.549 ms 7 ae-93-93.ebr3.Dallas1.Level3.net (4.69.151.170) 43.508 ms ae-83-83.ebr3.Dallas1.Level3.net (4.69.151.158) 41.666 ms ae-73-73.ebr3.Dallas1.Level3.net (4.69.151.146) 42.679 ms 8 ae-7-7.ebr3.Atlanta2.Level3.net (4.69.134.22) 44.381 ms 44.583 ms 44.074 ms 9 ae-2-2.ebr1.Washington1.Level3.net (4.69.132.86) 42.944 ms 42.201 ms 43.318 ms 10 ae-81-81.csw3.Washington1.Level3.net (4.69.134.138) 45.646 ms ae-71-71.csw2.Washington1.Level3.net (4.69.134.134) 50.224 ms ae-91-91.csw4.Washington1.Level3.net (4.69.134.142) 43.586 ms 11 ae-2-70.edge1.Washington1.Level3.net (4.69.149.77) 101.728 ms ae-1-60.edge1.Washington1.Level3.net (4.69.149.13) 44.683 ms ae-2-70.edge1.Washington1.Level3.net (4.69.149.77) 101.907 ms 12 AMAZON.COM.edge1.Washington1.Level3.net (4.28.125.110) 38.018 ms AMAZON.COM.edge1.Washington1.Level3.net (4.28.51.94) 38.667 ms AMAZON.COM.edge1.Washington1.Level3.net (4.28.125.110) 35.289 ms 13 72.21.220.165 (72.21.220.165) 36.194 ms 72.21.220.141 (72.21.220.141) 36.057 ms 36.386 ms 14 72.21.222.147 (72.21.222.147) 36.158 ms 35.761 ms 205.251.245.63 (205.251.245.63) 36.607 ms 15 * * * 16 * * * ~$ wget www.amazon.com --2013-01-31 14:06:28-- http://www.amazon.com/ Resolving www.amazon.com (www.amazon.com)... 176.32.98.166 Connecting to www.amazon.com (www.amazon.com)|176.32.98.166|:80... connected. HTTP request sent, awaiting response... 503 Service Unavailable 2013-01-31 14:06:29 ERROR 503: Service Unavailable. -- Dan White