<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: arial,helvetica,sans-serif; font-size: 10pt; color: #000000'>We experienced some connectivity issues as well. It looks like HE propagated a more specific route, black holing traffic.<br><br>Before outage:<br>62.23.0.0/16 *[BGP/170] 2d 06:45:04, MED 200, localpref 100<br> AS path: 3356 8220 I,<br><br>During outage:<br>62.23.128.0/17 *[BGP/170] 00:08:29, MED 250, localpref 100<br> AS path: 6939 200759 65021 I<br><br><br>Things have normalized now.<br><br><br>Ilya<br><br><hr id="zwchr"><div style="color: rgb(0, 0, 0); font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><b>From: </b>"Frank Bulk via Outages" <outages@outages.org><br><b>To: </b>outages@outages.org<br><b>Sent: </b>Friday, April 22, 2016 1:22:39 PM<br><b>Subject: </b>Re: [outages] HTTP access to www.amazon.com is down for us<br><br>How seeing a new IP address, and so now HTTP loads give us a 503:<br><br>root@nagios:/# wget -4 www.amazon.com<br>--2016-04-22 12:21:03-- http://www.amazon.com/<br>Resolving www.amazon.com... 54.239.25.192<br>Connecting to www.amazon.com|54.239.25.192|:80... connected.<br>HTTP request sent, awaiting response... 503 Service Unavailable<br>2016-04-22 12:21:03 ERROR 503: Service Unavailable.<br><br>root@nagios:/#<br><br>This IP address now goes via ZAYO rather than HE, but at least completes.<br><br>Frank<br><br>-----Original Message-----<br>From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Frank Bulk<br>via Outages<br>Sent: Friday, April 22, 2016 12:21 PM<br>To: outages@outages.org<br>Subject: [outages] HTTP access to www.amazon.com is down for us<br><br>Anyone else see the same?<br><br>root@nagios:/# wget -4 www.amazon.com<br>--2016-04-22 12:19:00-- http://www.amazon.com/<br>Resolving www.amazon.com... 54.239.26.128<br>Connecting to www.amazon.com|54.239.26.128|:80... failed: Connection timed<br>out.<br>Retrying.<br><br>--2016-04-22 12:19:22-- (try: 2) http://www.amazon.com/<br>Connecting to www.amazon.com|54.239.26.128|:80... failed: Connection timed<br>out.<br>Retrying.<br><br>--2016-04-22 12:19:45-- (try: 3) http://www.amazon.com/<br>Connecting to www.amazon.com|54.239.26.128|:80... ^C<br>root@nagios:/#<br><br><br>root@nagios:/etc/cron.weekly# tcptraceroute www.amazon.com<br>Selected device eth0.3, address 96.31.0.5, port 41361 for outgoing packets<br>Tracing the path to www.amazon.com (54.239.26.128) on TCP port 80 (www), 30<br>hops max<br> 1 router-core-inside.mtcnet.net (96.31.0.254) 0.258 ms 0.366 ms 0.356<br>ms<br> 2 sxct.sxcy.mtcnet.net (167.142.156.197) 0.274 ms 0.173 ms 0.150 ms<br> 3 premier.sxcy-mlx.fbnt.netins.net (173.215.60.5) 2.131 ms 1.453 ms<br>1.448 ms<br> 4 ins-db4-te-0-6-0-4.219.desm.netins.net (167.142.60.157) 7.797 ms 7.594<br>ms 7.592 ms<br> 5 ins-dc1-po200.desm.netins.net (167.142.67.193) 9.304 ms 9.177 ms<br>9.219 ms<br> 6 ins-kc2-po20.kmrr.netins.net (167.142.67.30) 9.407 ms 10.021 ms 9.228<br>ms<br> 7 v504.core1.oma1.he.net (184.105.18.169) 39.532 ms 32.855 ms 41.492 ms<br> 8 10ge11-15.core2.chi1.he.net (184.105.81.229) 20.037 ms 20.076 ms<br>21.987 ms<br> 9 100ge5-2.core1.chi1.he.net (184.105.81.98) 20.034 ms 20.106 ms 19.997<br>ms<br>10 100ge5-2.core1.nyc4.he.net (184.105.223.162) 40.097 ms 47.921 ms<br>38.699 ms<br>11 100ge11-1.core1.par2.he.net (184.105.81.78) 121.681 ms 113.899 ms *<br>12 10ge3-2.core1.zrh1.he.net (184.105.222.50) 140.341 ms 131.058 ms<br>139.553 ms<br>13 * * *<br>14 * * *<br>15 * * *<br>16 * * *<br>17 * * *<br>18 * * *<br>^C<br>root@nagios:/etc/cron.weekly#<br><br><br><br>-----Original Message-----<br>From: nagios@nagios.mtcnet.net [mailto:nagios@nagios.mtcnet.net] <br>Sent: Friday, April 22, 2016 12:18 PM<br>Subject: PROBLEM: Host amazon is DOWN!<br><br>***** Nagios *****<br><br>Host: This is a PROBLEM notice that Amazon is DOWN<br><br>Date/Time: Fri Apr 22 12:18:06 CDT 2016<br><br>CRITICAL - Socket timeout after 10 seconds<br><br>_______________________________________________<br>Outages mailing list<br>Outages@outages.org<br>https://puck.nether.net/mailman/listinfo/outages<br><br><br>_______________________________________________<br>Outages mailing list<br>Outages@outages.org<br>https://puck.nether.net/mailman/listinfo/outages<br></div><br></div></body></html>