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. All Locations below carry routes/traffic for Amazon Edge Services (e.g. CloudFront, Route53). Additionally, locations east of Rocky Mountains carry routes from US-East, and Canada (Central) AWS regions, and the locations west of Rocky Mountains carry routes for the US-West AWS region. East: (us-east-1/2, ca-central-1) - Boston - New York - Newark - Philadelphia - Ashburn - Vienna - Atlanta - Miami - Dallas - Chicago - Cleveland - Minneapolis - Toronto - Montreal West: (us-west-1/2) - Seattle - Portland - San Francisco Bay Area - Los Angeles - Phoenix - Denver The following locations only provide connectivity to edge services (CloudFront, Route53) - Salt lake City 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 - Nairobi - Dubai - Fujairah - Manama The following Amazon AP locations and associated IX's carry routes/traffic specific to Edge services (CloudFront, Route53), plus one or multiple AWS region infrastructure (EC2, S3) as noted below: - Tokyo (ap-northeast-1/2/3, ap-southeast-2) - Osaka (ap-northeast-1/3) - Hong Kong (ap-east-1) - Seoul (ap-northeast-2) - Singapore (ap-southeast-1/2; ap-northeast-1/2/3) - Sydney (ap-south-2) - Melbourne (ap-south-2) - Perth (ap-south-2) The following Amazon AP location and associated IX carry routes/traffic specific to local infrastructure in that metro (CloudFront, Route53) - Kuala Lumpur - Taipei The Following Amazon India Locations and associated Its carry routes/traffic specific only to the Edge services infrastructure to that metro, and AWS AP-South-1 (BOM) region routes. - Mumbai - Delhi - Chennai - Hyderabad - Bangalore - Kolkatta 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. ***