Looks like they're having issues again, since 1:50 pm Central. ================================================== [from 96.31.0.5] nagios:/tmp# wget -4 www.amazon.com --2013-08-19 13:54:20-- http://www.amazon.com/ Resolving www.amazon.com... 176.32.98.166 Connecting to www.amazon.com|176.32.98.166|:80... connected. HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers. Retrying. --2013-08-19 13:54:33-- (try: 2) http://www.amazon.com/ Connecting to www.amazon.com|176.32.98.166|:80... connected. HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers. Retrying. --2013-08-19 13:54:36-- (try: 3) http://www.amazon.com/ Connecting to www.amazon.com|176.32.98.166|:80... failed: Connection timed out. Resolving www.amazon.com... 205.251.242.54 Connecting to www.amazon.com|205.251.242.54|:80... connected. HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers. Retrying. --2013-08-19 13:55:11-- (try: 4) http://www.amazon.com/ Connecting to www.amazon.com|205.251.242.54|:80... connected. HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers. Retrying. --2013-08-19 13:55:17-- (try: 5) http://www.amazon.com/ Connecting to www.amazon.com|205.251.242.54|:80... failed: Connection timed out. Resolving www.amazon.com... 205.251.242.54 Connecting to www.amazon.com|205.251.242.54|:80... connected. HTTP request sent, awaiting response... ================================================== nagios:/tmp# tcptraceroute www.amazon.com Selected device eth0.3, address 96.31.0.5, port 39138 for outgoing packets Tracing the path to www.amazon.com (205.251.242.54) on TCP port 80 (www), 30 hops max 1 router-core-inside.mtcnet.net (96.31.0.254) 0.262 ms 0.194 ms 0.182 ms 2 sxct.sxcy.mtcnet.net (167.142.156.197) 0.220 ms 0.133 ms 0.136 ms 3 premier.sxcy-mlx.fbnt.netins.net (173.215.60.5) 1.984 ms 1.949 ms 1.975 ms 4 ins-db1-te-13-2-219.desm.netins.net (167.142.60.157) 7.294 ms 7.348 ms 7.372 ms 5 ins-dc1-et-8-2.desm.netins.net (167.142.67.5) 7.334 ms 7.367 ms 7.308 ms 6 te-3-3.car2.KansasCity1.Level3.net (4.53.34.113) 13.791 ms 13.820 ms 13.756 ms 7 ae-11-11.car1.KansasCity1.Level3.net (4.69.135.233) 73.308 ms 157.964 ms * 8 ae-5-5.ebr2.Dallas1.Level3.net (4.69.135.230) 55.937 ms 55.983 ms 55.809 ms 9 ae-62-62.csw1.Dallas1.Level3.net (4.69.151.129) 56.174 ms 56.251 ms 56.178 ms 10 ae-63-63.ebr3.Dallas1.Level3.net (4.69.151.134) 55.556 ms 55.585 ms 55.822 ms 11 ae-7-7.ebr3.Atlanta2.Level3.net (4.69.134.22) 55.510 ms 55.478 ms 57.041 ms 12 ae-2-2.ebr1.Washington1.Level3.net (4.69.132.86) 55.747 ms 55.730 ms 55.800 ms 13 ae-91-91.csw4.Washington1.Level3.net (4.69.134.142) 55.314 ms 55.380 ms 62.384 ms 14 ae-4-90.edge3.Washington1.Level3.net (4.69.149.209) 55.568 ms 55.603 ms 55.496 ms 15 AMAZON.COM.edge3.Washington1.Level3.net (4.59.144.178) 55.415 ms 55.563 ms 55.488 ms 16 205.251.245.21 56.965 ms 57.036 ms 56.929 ms 17 205.251.245.121 57.045 ms 57.094 ms 57.158 ms 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 205.251.242.54 [open] 56.911 ms 56.833 ms 56.942 ms nagios:/tmp# ================================================== [from puck.nether.net] [fbulk@puck tmp]$ wget -4 www.amazon.com --2013-08-19 14:54:26-- http://www.amazon.com/ Resolving www.amazon.com (www.amazon.com)... 72.21.215.232 Connecting to www.amazon.com (www.amazon.com)|72.21.215.232|:80... connected. HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers. Retrying. --2013-08-19 14:55:28-- (try: 2) http://www.amazon.com/ Connecting to www.amazon.com (www.amazon.com)|72.21.215.232|:80... connected. HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers. Retrying. --2013-08-19 14:55:37-- (try: 3) http://www.amazon.com/ Connecting to www.amazon.com (www.amazon.com)|72.21.215.232|:80... connected. HTTP request sent, awaiting response... ================================================== -----Original Message----- From: Outages-discussion [mailto:outages-discussion-bounces@outages.org] On Behalf Of Frank Bulk (iname.com) Sent: Friday, May 10, 2013 12:19 PM To: outages-discussion@outages.org Subject: [Outages-discussion] Amazon.com interruption Did anyone else see access issues to amazon.com down from 8:50 am to 9:04 am, and then again from 9:09 am until 9:19 am (Central)? I was getting "HTTP/1.1 503 Service Unavailable". Their dashboard only shows an issue with their Flexible Payments Service. Frank nagios:/# tcptraceroute www.amazon.com Selected device eth0.3, address 96.31.0.5, port 50070 for outgoing packets Tracing the path to www.amazon.com (72.21.194.212) on TCP port 80 (www), 30 hops max 1 router-core-inside.mtcnet.net (96.31.0.254) 0.260 ms 0.201 ms 0.181 ms 2 sxct.movl.mtcnet.net (167.142.156.194) 0.207 ms 0.131 ms 0.126 ms 3 premier.movl-mlx.fbnt.netins.net (173.215.60.1) 1.991 ms 1.901 ms 1.961 ms 4 ins-kb1-te-13-2-220.kmrr.netins.net (167.142.64.253) 7.540 ms 7.562 ms 7.620 ms 5 ins-kc2-et-8-3.kmrr.netins.net (167.142.67.37) 9.234 ms 9.178 ms 9.233 ms 6 ins-dc1-po20.desm.netins.net (167.142.67.29) 9.192 ms 9.131 ms 9.215 ms 7 te-3-3.car2.KansasCity1.Level3.net (4.53.34.113) 15.605 ms 15.585 ms 15.560 ms 8 ae-11-11.car1.KansasCity1.Level3.net (4.69.135.233) 57.692 ms 57.626 ms 57.515 ms 9 ae-5-5.ebr2.Dallas1.Level3.net (4.69.135.230) 57.467 ms 57.384 ms 57.397 ms 10 ae-82-82.csw3.Dallas1.Level3.net (4.69.151.153) 57.274 ms 57.169 ms 57.271 ms 11 ae-83-83.ebr3.Dallas1.Level3.net (4.69.151.158) 57.420 ms 57.416 ms 57.881 ms 12 ae-7-7.ebr3.Atlanta2.Level3.net (4.69.134.22) 57.137 ms 57.120 ms 57.146 ms 13 ae-2-2.ebr1.Washington1.Level3.net (4.69.132.86) 57.510 ms 57.610 ms 57.544 ms 14 ae-91-91.csw4.Washington1.Level3.net (4.69.134.142) 57.716 ms 57.613 ms ae-81-81.csw3.Washington1.Level3.net (4.69.134.138) 58.287 ms 15 ae-4-90.edge2.Washington1.Level3.net (4.69.149.206) 57.111 ms 56.997 ms 57.492 ms 16 AMAZON.COM.edge2.Washington1.Level3.net (4.79.22.86) 57.629 ms 57.784 ms 57.705 ms 17 72.21.220.145 58.537 ms 58.471 ms 58.650 ms 18 72.21.222.139 58.438 ms 71.582 ms 58.461 ms 19 205.251.248.3 59.257 ms 59.249 ms 59.251 ms 20 205.251.248.9 59.904 ms 60.060 ms 60.509 ms 21 72.21.194.212 [open] 58.633 ms 58.522 ms 58.677 ms nagios:/# _______________________________________________ Outages-discussion mailing list Outages-discussion@outages.org https://puck.nether.net/mailman/listinfo/outages-discussion