New AWS Edge Location Madrid,Spain. Welcome baby!

New AWS Edge Location Madrid Official Announcement:
http://aws.amazon.com/about-aws/whats-new/2012/09/12/amazon-cloudfront-announces-madrid-edge-location/

Let's give it a look. Some traceroutes from Spain using http://www.rediris.es/red/lg/

Espere, por favor... Please wait... traceroute to 54.240.186.41 (54.240.186.41), 30 hops max, 40 byte packets  1  ge-0.espanix.mdrdsp02.es.bb.gin.ntt.net (193.149.1.36)  6.446 ms  7.397 ms  2.023 ms  2  * 81.19.109.138 (81.19.109.138)  1.758 ms  1.689 ms  3  54.240.186.41 (54.240.186.41)  1.730 ms  1.721 ms  6.010 ms {master}

Espere, por favor... Please wait... traceroute to 54.240.186.41 (54.240.186.41), 30 hops max, 40 byte packets  1  CICA.GE0-2-0.ciemat.rt1.mad.red.rediris.es (130.206.245.37)  13.676 ms  47.461 ms  8.326 ms  2  ge-0.espanix.mdrdsp02.es.bb.gin.ntt.net (193.149.1.36)  8.620 ms  8.306 ms  8.184 ms  3  81.19.109.138 (81.19.109.138)  8.473 ms  11.382 ms  23.109 ms  4  54.240.186.41 (54.240.186.41)  8.322 ms  7.995 ms  9.795 ms {master}

Few hops. Good

Espere, por favor... Please wait... PING 54.240.186.41 (54.240.186.41): 56 data bytes 64 bytes from 54.240.186.41: icmp_seq=0 ttl=61 time=8.081 ms 64 bytes from 54.240.186.41: icmp_seq=1 ttl=61 time=8.006 ms 64 bytes from 54.240.186.41: icmp_seq=2 ttl=61 time=8.144 ms 64 bytes from 54.240.186.41: icmp_seq=3 ttl=61 time=8.129 ms 64 bytes from 54.240.186.41: icmp_seq=4 ttl=61 time=8.221 ms 64 bytes from 54.240.186.41: icmp_seq=5 ttl=61 time=12.117 ms --- 54.240.186.41 ping statistics --- 6 packets transmitted, 6 packets received, 0% packet loss round-trip min/avg/max/stddev = 8.006/8.783/12.117/1.492 ms {master}

Espere, por favor... Please wait... PING 54.240.186.41 (54.240.186.41): 56 data bytes 64 bytes from 54.240.186.41: icmp_seq=0 ttl=63 time=1.749 ms 64 bytes from 54.240.186.41: icmp_seq=1 ttl=63 time=2.006 ms 64 bytes from 54.240.186.41: icmp_seq=2 ttl=63 time=6.273 ms 64 bytes from 54.240.186.41: icmp_seq=3 ttl=63 time=5.281 ms 64 bytes from 54.240.186.41: icmp_seq=4 ttl=63 time=4.484 ms 64 bytes from 54.240.186.41: icmp_seq=5 ttl=63 time=4.070 ms --- 54.240.186.41 ping statistics --- 6 packets transmitted, 6 packets received, 0% packet loss round-trip min/avg/max/stddev = 1.749/3.977/6.273/1.637 ms {master}

And short roud-trip. Good. Yep, looks like this guy is where it has to be. Nice!

Reading CloudFront logs I've noticed that the ID for this Edge Location is MAD50

#Version: 1.0 #Fields: date time x-edge-location sc-bytes c-ip cs-method cs(Host) cs-uri-stem sc-status cs(Referer) cs(User-Agent) cs-uri-query cs(Cookie) x-edge-result-type x-edge-request-id 2012-10-19 10:49:11 MAD50 2111 80.28.28.28 GET d310qyhvupgmlk.cloudfront.net / 200 - Mozilla/5.0%20(X11;%20Linux%20x86_64)%20AppleWebKit/536.11%20(KHTML,%20like%20Gecko)%20Ubuntu/12.04%20Chromium/20.0.1132.47%20Chrome/20.0.1132.47%20Safari/536.11 - - Miss hnyCtybbSg9HGO5NWsBwUMqvd-1JoXqPeo3CN9VxD4SYVKH99rEleQ==

For an updated Edge Location list check this post http://blog.domenech.org/2013/10/amazon-web-services-cloudfront-edgelocation-codes.html


Update February-24-2013: Collected Edge Locations so far: 46

AMS1  Amsterdam
AMS50 Amsterdam
ARN1  Stockholm
BOM2  Mumbai, India
CDG3  Paris, France
CDG50 Paris, France
CDG51 Paris, France
DFW3  Dallas,TX
DFW50 Dallas,TX
DUB2  Dublin, Irealand
EWR2  Newark
FRA2  Frankfurt, Germany
FRA6  Frankfurt, Germany
GRU1  Sau Paulo, Brazil
HKG1  Hong Kong
HKG50 Hong Kong
IAD12 Ashburn
IAD2  Ashburn
IAD53 Ashburn
ICN50 Seoul, South Corea
IND6  South Bend
JAX1  Jacksonville
JFK1  New York
JFK5  New York
JFK6  New York
LAX1  Los Angeles
LAX3  Los Angeles
LHR3  London, UK
LHR5  London, UK
MAA3  Chennai, India
MAD50 Madrid,Spain
MIA3  Miami,FL
MIA50 Miami,FL
MXP4  Milan, Italy
NRT52 Tokyo,Japan
NRT53 Tokyo,Japan
NRT54 Tokyo,Japan
SEA4  Seattle, Australia
SEA50 Seattle, Australia
SFO4  San Jose,CA
SFO5  San Jose,CA
SFO9  San Jose,CA
SIN2  Singapore
SIN3  Singapore
STL2  St Louis
SYD1  Sydney, Australia