Unable to access Some Amazon EC2 Addresses

All other technical assistance queries (General technical issues, IPv6. P2P, News groups, etc)
Post Reply
jeffborg
Posts: 3
Joined: Tue Jan 20, 2004 12:01 pm
Location: Buff Point

Unable to access Some Amazon EC2 Addresses

Post by jeffborg » Thu Oct 28, 2010 10:36 am

Hi,

At around 2010-10-26 21:41:54 our monitor flagged a ec2 machine as being down, I thought it was ec2 initially and just started a new virtual machine replacing the old one, but it was also inaccessible

The address is currently 50.16.33.145 which is totally inaccessible from 3 different Exetel connections, I can get to it from our hosted server in Sydney.

I think it might have something to do with the availability zone, It's in done us-east-1d, I started up another one in us-east-1a and it's accessable so I changed the launch script for this server to force the availability zone.

EDIT: updated I just tried this and got the ip address 50.16.62.106 which doesn't work as well!
I found this page on amazon
http://developer.amazonwebservices.com/ ... ?annID=795

it lists 50.16.0.0/15 (50.16.0.0 - 50.17.255.255) as a range, if you traceroute to anything in there it appears to not work. vs some of the other addresses which do appear to trace to the right place.

Has anyone else experienced this, Exetel any comments?

Regards
Jeff

Shazir
Exetel Staff
Posts: 17
Joined: Sat Aug 01, 2009 3:11 pm

Re: Unable to access Some Amazon EC2 Addresses

Post by Shazir » Thu Oct 28, 2010 11:11 am

jeffborg wrote:Hi,

At around 2010-10-26 21:41:54 our monitor flagged a ec2 machine as being down, I thought it was ec2 initially and just started a new virtual machine replacing the old one, but it was also inaccessible

The address is currently 50.16.33.145 which is totally inaccessible from 3 different Exetel connections, I can get to it from our hosted server in Sydney.

I think it might have something to do with the availability zone, It's in done us-east-1d, I started up another one in us-east-1a and it's accessable so I changed the launch script for this server to force the availability zone.

EDIT: updated I just tried this and got the ip address 50.16.62.106 which doesn't work as well!
I found this page on amazon
http://developer.amazonwebservices.com/ ... ?annID=795

it lists 50.16.0.0/15 (50.16.0.0 - 50.17.255.255) as a range, if you traceroute to anything in there it appears to not work. vs some of the other addresses which do appear to trace to the right place.

Has anyone else experienced this, Exetel any comments?

Regards
Jeff
Hi Jeff, please email residentialsupport@exetel.com.au along with ping tests & trace routes. One of the support engineers could get this investigated for you, thank you.

Post Reply