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 European 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

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.