http://downforeveryoneorjustme.com/amazon.com Doesnt happen too often...
Was down for me, but its back up now. __________________________ Joseph Wilker, Network and Systems Administrator II ITSO - SysNet Operations ---------- Certified Commvault 9 Administrator Apple Certified Associate From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Tim Glen Sent: Thursday, January 31, 2013 1:58 PM To: Outages@outages.org Subject: [outages] Amazon is down.... http://downforeveryoneorjustme.com/amazon.com Doesnt happen too often...
Same error message via cogent in nyc and softlayer from linode in dallas. On Thu, Jan 31, 2013 at 3:00 PM, Joseph Wilker <JWilker@edgewood.edu> wrote:
Was down for me, but its back up now.****
** **
__________________________****
Joseph Wilker, Network and Systems Administrator II****
ITSO – SysNet Operations****
----------****
Certified Commvault 9 Administrator****
Apple Certified Associate ****
** **
*From:* outages-bounces@outages.org [mailto:outages-bounces@outages.org] *On Behalf Of *Tim Glen *Sent:* Thursday, January 31, 2013 1:58 PM *To:* Outages@outages.org *Subject:* [outages] Amazon is down....****
** **
** **
http://downforeveryoneorjustme.com/amazon.com****
Doesnt happen too often...****
****
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- Patrick Hahn
Gizmodo is reporting odd functionality - direct product links work, and AWS appears unaffected. Twitter is ablaze with "amazon down" messages. http://gizmodo.com/5980618/amazon-is-down Thanks, -Tim From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Tim Glen Sent: Thursday, January 31, 2013 1:58 PM To: Outages@outages.org Subject: [outages] Amazon is down.... http://downforeveryoneorjustme.com/amazon.com Doesnt happen too often...
On Thu, Jan 31, 2013 at 1:05 PM, Tim Durnan <tim.durnan@heatseeker.com>wrote:
Gizmodo is reporting odd functionality – direct product links work, and AWS appears unaffected. Twitter is ablaze with “amazon down” messages.****
** **
Down completely via Cox in Phoenix. Sporadic (25%) available via Qwest dedicated connections. Down via Cogent. Did everyone remember to bring a towel? -- Carlos Alvarez TelEvolve 602-889-3003
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
Worked for me when www.amazon.com resolved to 205.251.242.54 and 72.21.194.212. With companies that have such a large Internet presence that's it's not enough to say anymore the "site" is down on port 80 (geographically hosted and potentially anycasted) or 53 (potentially anycasted), one really needs the IP address that was resolved and a traceroute to it so one can see the path. nagios:/tmp# tcptraceroute Selected device eth0.3, address 96.31.0.5, port 59953 for outgoing packets Tracing the path to 205.251.242.54 on TCP port 80 (www), 30 hops max 1 router-core-inside.mtcnet.net (96.31.0.254) 0.228 ms 0.190 ms 0.184 ms 2 sxct.sxcy.mtcnet.net (167.142.156.197) 0.187 ms 0.127 ms 0.175 ms 3 premier.sxcy-mlx.fbnt.netins.net (173.215.60.5) 1.655 ms 1.595 ms 1.582 ms 4 ins-db1-te-13-2-219.desm.netins.net (167.142.60.157) 7.784 ms 7.819 ms 8.325 ms 5 ins-dc1-et-8-2.desm.netins.net (167.142.67.5) 8.338 ms 7.832 ms 7.755 ms 6 te-3-3.car2.KansasCity1.Level3.net (4.53.34.113) 13.936 ms 13.963 ms 13.942 ms 7 ae-11-11.car1.KansasCity1.Level3.net (4.69.135.233) 55.712 ms 55.775 ms 55.777 ms 8 ae-5-5.ebr2.Dallas1.Level3.net (4.69.135.230) 55.578 ms 55.482 ms 55.574 ms 9 ae-72-72.csw2.Dallas1.Level3.net (4.69.151.141) 67.943 ms 56.098 ms 56.108 ms 10 ae-73-73.ebr3.Dallas1.Level3.net (4.69.151.146) 56.019 ms 55.929 ms 56.531 ms 11 ae-7-7.ebr3.Atlanta2.Level3.net (4.69.134.22) 56.342 ms 56.291 ms 56.315 ms 12 ae-2-2.ebr1.Washington1.Level3.net (4.69.132.86) 56.238 ms 56.203 ms 56.128 ms 13 ae-61-61.csw1.Washington1.Level3.net (4.69.134.130) 60.124 ms ae-91-91.csw4.Washington1.Level3.net (4.69.134.142) 55.964 ms ae-61-61.csw1.Washington1.Level3.net (4.69.134.130) 57.213 ms 14 ae-1-60.edge3.Washington1.Level3.net (4.69.149.17) 55.956 ms 56.033 ms 55.926 ms 15 AMAZON.COM.edge3.Washington1.Level3.net (4.59.144.174) 55.973 ms 56.019 ms 55.946 ms 16 205.251.245.23 56.887 ms 56.895 ms 58.231 ms 17 205.251.245.41 57.376 ms 57.438 ms 57.329 ms 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 205.251.242.54 [open] 57.438 ms 57.086 ms 57.101 ms nagios:/tmp# nagios:/tmp# tcptraceroute 72.21.194.212 Selected device eth0.3, address 96.31.0.5, port 57614 for outgoing packets Tracing the path to 72.21.194.212 on TCP port 80 (www), 30 hops max 1 router-core-inside.mtcnet.net (96.31.0.254) 0.280 ms 0.190 ms 0.181 ms 2 sxct.movl.mtcnet.net (167.142.156.194) 0.187 ms 0.132 ms 0.125 ms 3 premier.movl-mlx.fbnt.netins.net (173.215.60.1) 1.926 ms 1.952 ms 1.982 ms 4 ins-kb1-te-13-2-220.kmrr.netins.net (167.142.64.253) 7.021 ms 6.995 ms 6.931 ms 5 ins-kc2-et-8-3.kmrr.netins.net (167.142.67.37) 8.607 ms 8.645 ms 8.599 ms 6 ins-dc1-po20.desm.netins.net (167.142.67.29) 8.660 ms 8.611 ms 8.580 ms 7 te-3-3.car2.KansasCity1.Level3.net (4.53.34.113) 36.713 ms 199.513 ms 61.553 ms 8 ae-11-11.car1.KansasCity1.Level3.net (4.69.135.233) 56.652 ms 56.700 ms 56.630 ms 9 ae-5-5.ebr2.Dallas1.Level3.net (4.69.135.230) 56.795 ms 56.835 ms 56.771 ms 10 ae-82-82.csw3.Dallas1.Level3.net (4.69.151.153) 59.351 ms 56.919 ms 69.167 ms 11 ae-83-83.ebr3.Dallas1.Level3.net (4.69.151.158) 56.550 ms 56.583 ms 56.619 ms 12 ae-7-7.ebr3.Atlanta2.Level3.net (4.69.134.22) 59.007 ms 56.837 ms 56.930 ms 13 ae-2-2.ebr1.Washington1.Level3.net (4.69.132.86) 56.341 ms 56.239 ms 56.268 ms 14 ae-71-71.csw2.Washington1.Level3.net (4.69.134.134) 63.664 ms 56.611 ms 67.998 ms 15 ae-2-70.edge2.Washington1.Level3.net (4.69.149.78) 56.646 ms 56.593 ms 56.545 ms 16 AMAZON.COM.edge2.Washington1.Level3.net (4.79.22.74) 56.341 ms 56.374 ms 56.470 ms 17 72.21.220.153 57.774 ms 57.644 ms 57.729 ms 18 72.21.222.139 57.646 ms 57.600 ms 57.532 ms 19 205.251.248.1 59.012 ms 59.459 ms 59.981 ms 20 205.251.248.9 61.936 ms 62.216 ms 60.018 ms 21 72.21.194.212 [open] 57.243 ms 57.105 ms 57.258 ms nagios:/tmp# From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Tim Glen Sent: Thursday, January 31, 2013 1:58 PM To: Outages@outages.org Subject: [outages] Amazon is down.... http://downforeveryoneorjustme.com/amazon.com Doesnt happen too often...
When it was down it didn't work for me in Thailand. It's working ok now though. On 01/02/2013 03:46, Frank Bulk wrote:
Worked for me when www.amazon.com <http://www.amazon.com> resolved to 205.251.242.54 and 72.21.194.212. With companies that have such a large Internet presence that's it's not enough to say anymore the "site" is down on port 80 (geographically hosted and potentially anycasted) or 53 (potentially anycasted), one really needs the IP address that was resolved and a traceroute to it so one can see the path.
Interesting - - http://downforeveryoneorjustme.com/amazon.com shows Amazon as being down, but I can get to www.amazon.com and drill around in the site just fine. On Thu, Jan 31, 2013 at 1:57 PM, Tim Glen <tglen@asicentral.com> wrote:
**
**** **
http://downforeveryoneorjustme.com/amazon.com
**Doesnt happen too often...**
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- *Colleen Velo email: cmvelo@gmail.com*
Should be http://downforusbutnotyou.com...LOL! Same here, no problems getting to Amazon, did have some brief problems earlier in the day when others reported problems. On 01/31/2013 05:19 PM, Colleen Velo wrote:
Interesting -
* http://downforeveryoneorjustme.com/amazon.com shows Amazon as being down, but I can get to www.amazon.com <http://www.amazon.com> and drill around in the site just fine.
On Thu, Jan 31, 2013 at 1:57 PM, Tim Glen <tglen@asicentral.com <mailto:tglen@asicentral.com>> wrote:
http://downforeveryoneorjustme.com/amazon.com
Doesnt happen too often...
_______________________________________________ Outages mailing list Outages@outages.org <mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages
-- *Colleen Velo email: cmvelo@gmail.com <mailto:cmvelo@gmail.com>*
participants (10)
-
Bret Clark -
Carlos Alvarez -
Colleen Velo -
Dan White -
Frank Bulk -
Joseph Wilker -
Neil -
Patrick Hahn -
Tim Durnan -
Tim Glen