This is a beta/testing instance of PeeringDB. Some features may work differently than production. Do not store data here that you intend to keep - automatically scheduled refreshes from production are currently disabled.
Amazon.com
Organization
Also Known As
Amazon Web Services
Company Website
Primary ASN
16509
IRR as-set/route-set
AS-AMAZON
Route Server URL
Looking Glass URL
Network Type
Enterprise
IPv4 Prefixes
5000
IPv6 Prefixes
2000
Traffic Levels
Not Disclosed
Traffic Ratios
Balanced
Geographic Scope
Global
Protocols Supported
Unicast IPv4
Multicast
IPv6
Never via route servers
Last Updated
2019-12-29T14:56:38Z
Notes
If you have a connectivity issue to Amazon then please visit:
- IPv4: http://ec2-reachability.amazonaws.com/
- IPv6: http://ipv6.ec2-reachability.amazonaws.com/
And include detail on prefixes you think you have a problem with if you contact our Ops alias. This will reduce time with troubleshooting.
The following Amazon US locations and associated IX's carry routes/traffic specific only to the services with infrastructure in that metro. For example, Jacksonville is CloudFront only, whereas Ashburn is CloudFront, EC2, S3, etc.)
- Seattle
- Palo Alto
- San Jose
- Los Angeles
- Dallas
- St Louis
- South Bend
- Jacksonville
- Miami
- Ashburn
- Vienna
- Newark
- New York
The following locations and associated IX's are part of Amazon's EMEA Backbone, carrying routes/traffic for other AWS services (e.g. EC2, S3), Amazon retail, as well as local CloudFront caching. For each of these locations, Amazon will provide local routes/traffic for all services within that locality unless peers are able to meet in at least two diverse locations within the region, in which case, routes/traffic for all services within that region will be provided.
- Dublin
- Amsterdam
- London
- Frankfurt
- Paris
- Stockholm
- Copenhagen
- Helsinki
- Oslo
- Madrid
- Marseille
- Milan
- Palermo
- Rome
- Dusseldorf
- Munich
- Berlin
- Sofia
- Bucharest
- Budapest
- Cape Town
- Johannesburg
- Dubai
- Fujairah
- Manama
The following Amazon AP locations and associated IX's carry routes/traffic specific only to the services with infrastructure in that metro. For example, Hong Kong is CloudFront only, whereas Sydney is CloudFront, EC2, S3, etc.)
- Tokyo
- Osaka
- Hong Kong
- Singapore
- Sydney
- Kuala Lumpur
- Taipei
When new peering sessions are established, they will initially be configured to not announce or accept any prefixes. Sessions will be normalized in a maintenance window the following evening, usually centered around 11:00 PM to 3:00 AM local time.
*** Please don't add our NOC alias listed below to peering requests. Our NOC alias is for trouble issues only. ***
Peering Policy Information
Peering Policy
General Policy
Selective
Multiple Locations
Preferred
Ratio Requirement
No
Contract Requirement
Not Required
Contact Information
Some of this network's contacts are hidden because they are only visible to authenticated users and you are currently not logged in.
Public Peering Exchange Points
Exchange
ASN
IPv4
IPv6
Speed
RS Peer
You may filter by Exchange, ASN or Speed.
1418
1214
DE-CIX DusseldorfDE-CIX Dusseldorf Peering LAN
16509
185.1.58.80
2001:7f8:9e::407d:0:1
10G
1418
107
MSK-IX Saint-PetersburgMSK-IX Saint-Petersburg peering network
16509
194.226.100.44
2001:7f8:20:201::100:44
100G
1418
107
MSK-IX Saint-PetersburgMSK-IX Saint-Petersburg peering network
16509
194.226.102.44
2001:7f8:20:202::102:44
100G
1418
1310
Netnod Stockholm STH-A -- MTU4470STH-A -- MTU4470
16509
195.245.240.47
2001:7f8:d:fc::47
100G
1418
1311
Netnod Stockholm STH-B -- MTU1500STH-B -- MTU1500
16509
194.68.128.47
2001:7f8:d:fe::47
100G
1418
1312
Netnod Stockholm STH-B -- MTU4470STH-B -- MTU4470
16509
195.69.119.47
2001:7f8:d:fb::47
100G
Private Peering Facilities
Facility
ASN
Country
City
You may filter by Facility, ASN, Country or City.
