[outages] HTTP access to www.amazon.com is down for us

[Ilya Sokolov]

We experienced some connectivity issues as well. It looks like HE propagated a more specific route, black holing traffic. 

Before outage: 
62.23.0.0/16 *[BGP/170] 2d 06:45:04, MED 200, localpref 100 
AS path: 3356 8220 I, 

During outage: 
62.23.128.0/17 *[BGP/170] 00:08:29, MED 250, localpref 100 
AS path: 6939 200759 65021 I 


Things have normalized now. 


Ilya 

----- Original Message -----

From: "Frank Bulk via Outages" <outages at outages.org> 
To: outages at outages.org 
Sent: Friday, April 22, 2016 1:22:39 PM 
Subject: Re: [outages] HTTP access to www.amazon.com is down for us 

How seeing a new IP address, and so now HTTP loads give us a 503: 

root at nagios:/# wget -4 www.amazon.com 
--2016-04-22 12:21:03-- http://www.amazon.com/ 
Resolving www.amazon.com... 54.239.25.192 
Connecting to www.amazon.com|54.239.25.192|:80... connected. 
HTTP request sent, awaiting response... 503 Service Unavailable 
2016-04-22 12:21:03 ERROR 503: Service Unavailable. 

root at nagios:/# 

This IP address now goes via ZAYO rather than HE, but at least completes. 

Frank 

-----Original Message----- 
From: Outages [mailto:outages-bounces at outages.org] On Behalf Of Frank Bulk 
via Outages 
Sent: Friday, April 22, 2016 12:21 PM 
To: outages at outages.org 
Subject: [outages] HTTP access to www.amazon.com is down for us 

Anyone else see the same? 

root at nagios:/# wget -4 www.amazon.com 
--2016-04-22 12:19:00-- http://www.amazon.com/ 
Resolving www.amazon.com... 54.239.26.128 
Connecting to www.amazon.com|54.239.26.128|:80... failed: Connection timed 
out. 
Retrying. 

--2016-04-22 12:19:22-- (try: 2) http://www.amazon.com/ 
Connecting to www.amazon.com|54.239.26.128|:80... failed: Connection timed 
out. 
Retrying. 

--2016-04-22 12:19:45-- (try: 3) http://www.amazon.com/ 
Connecting to www.amazon.com|54.239.26.128|:80... ^C 
root at nagios:/# 


root at nagios:/etc/cron.weekly# tcptraceroute www.amazon.com 
Selected device eth0.3, address 96.31.0.5, port 41361 for outgoing packets 
Tracing the path to www.amazon.com (54.239.26.128) on TCP port 80 (www), 30 
hops max 
1 router-core-inside.mtcnet.net (96.31.0.254) 0.258 ms 0.366 ms 0.356 
ms 
2 sxct.sxcy.mtcnet.net (167.142.156.197) 0.274 ms 0.173 ms 0.150 ms 
3 premier.sxcy-mlx.fbnt.netins.net (173.215.60.5) 2.131 ms 1.453 ms 
1.448 ms 
4 ins-db4-te-0-6-0-4.219.desm.netins.net (167.142.60.157) 7.797 ms 7.594 
ms 7.592 ms 
5 ins-dc1-po200.desm.netins.net (167.142.67.193) 9.304 ms 9.177 ms 
9.219 ms 
6 ins-kc2-po20.kmrr.netins.net (167.142.67.30) 9.407 ms 10.021 ms 9.228 
ms 
7 v504.core1.oma1.he.net (184.105.18.169) 39.532 ms 32.855 ms 41.492 ms 
8 10ge11-15.core2.chi1.he.net (184.105.81.229) 20.037 ms 20.076 ms 
21.987 ms 
9 100ge5-2.core1.chi1.he.net (184.105.81.98) 20.034 ms 20.106 ms 19.997 
ms 
10 100ge5-2.core1.nyc4.he.net (184.105.223.162) 40.097 ms 47.921 ms 
38.699 ms 
11 100ge11-1.core1.par2.he.net (184.105.81.78) 121.681 ms 113.899 ms * 
12 10ge3-2.core1.zrh1.he.net (184.105.222.50) 140.341 ms 131.058 ms 
139.553 ms 
13 * * * 
14 * * * 
15 * * * 
16 * * * 
17 * * * 
18 * * * 
^C 
root at nagios:/etc/cron.weekly# 



-----Original Message----- 
From: nagios at nagios.mtcnet.net [mailto:nagios at nagios.mtcnet.net] 
Sent: Friday, April 22, 2016 12:18 PM 
Subject: PROBLEM: Host amazon is DOWN! 

***** Nagios ***** 

Host: This is a PROBLEM notice that Amazon is DOWN 

Date/Time: Fri Apr 22 12:18:06 CDT 2016 

CRITICAL - Socket timeout after 10 seconds 

_______________________________________________ 
Outages mailing list 
Outages at outages.org 
https://puck.nether.net/mailman/listinfo/outages 


_______________________________________________ 
Outages mailing list 
Outages at outages.org 
https://puck.nether.net/mailman/listinfo/outages 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20160422/5a1b546d/attachment.htm>