Amazon EU-West 1 trouble
dovid at telecurve.com
Sun Apr 23 10:57:56 UTC 2017
HE is having issues in Europe. I spoke with them an hour ago, they said they were aware of the issue but didn't have an ETA. Based on the traces we saw issues with connections coming into London.
From: baldur.norddahl at gmail.com
Sent: April 23, 2017 6:52 AM
To: nanog at nanog.org
Subject: Amazon EU-West 1 trouble
We are currently experiencing massive packet loss from Amazon EU-West 1.
This page http://ec2-reachability.amazonaws.com/ will show most of
eu-west-1 as down but actually it is packet loss of 90+ %.
I have found that if I shutdown our link to Hurricane Electric the
problem disappears. Also it is only an IPv4 problem as IPv6 is fine
(also going through Hurricane Electric).
A traceroute shows everything ok until the first hop inside the Amazon
network. The peering is apparently at AMS-IX.
Right now we are ok because I am keeping the HE.Net connection down, but
I managed to find another NLNOG Ring node that has the same problem:
gigabit at casablanca01:~$ ping 22.214.171.124
PING 126.96.36.199 (188.8.131.52) 56(84) bytes of data.
64 bytes from 184.108.40.206: icmp_seq=2 ttl=244 time=35.1 ms
64 bytes from 220.127.116.11: icmp_seq=34 ttl=244 time=35.2 ms
64 bytes from 18.104.22.168: icmp_seq=44 ttl=244 time=35.2 ms
64 bytes from 22.214.171.124: icmp_seq=52 ttl=244 time=35.2 ms
--- 126.96.36.199 ping statistics ---
72 packets transmitted, 4 received, 94% packet loss, time 71228ms
rtt min/avg/max/mdev = 35.170/35.220/35.251/0.232 ms
That IP is one from eu-west-1 taken from the ec2-reachability page. When
I ping it with the HE.Net link down there is 0% packet loss. With it up
we are seeing something like the above. However I notice that Casablanca
is going out through Telia not HE. The return path could very well be
via HE of course, there is no way to know that.
From all the RING nodes I checked only Casablanca01 seems to experience
the problem, so it appears it is not very wide spread.
Anyone know how to get in contact with Amazon and have them debug this
More information about the NANOG