I have set up a tiny windows VM in the East-US region but when the server comes up it has an IP address that geo-locates to Brazil. Also the traceroute to it looks like it may indeed not be in East-US as desired.
Any reason why my VM created in US-East would actually be provisioned in Brazil?
I got 191.238.50.170 for the IP address of the instance and a similar address when I tried it a second time. Both show in geo-IP tools as being from Brazil and the traceroute to it from a west-coast location seems high enough latency that it may indeed be not on the East coast.
Thoughts? I was able to make a Linux VM in the east zone but when I make a tiny windows one, it goes to Brazil.
Here's part of the trace with RTT times showing a subset of the path where the latency goes from 5ms to 111ms and onwards
...
any2ix.coresite.com 5.1
gi4-1-0.gw3.lax1.asianetcom.net 111.4
202.147.0.121 111.4
ge3-1-0-0.gw3.nrt4.asianetcom.net 111.5
61.8.59.22 166.8
xe-0-2-0-0.tya-96cbe-1a.ntwk.msn.net 167.2
xe-7-1-0-0.lax-96cbe-1b.ntwk.msn.net 102.6
xe-10-0-3-0.bn1-96c-1a.ntwk.msn.net 137.7
207.46.46.114 128.7
???
???
xe-1-2-1-0.blu-96c-1a.ntwk.msn.net 160.0
xe-8-3-1-0.bl2-96c-1a.ntwk.msn.net 185.1
xe-0-0-1-0.bl3-96cbe-1a.ntwk.msn.net 160.6
10.22.123.41 161.0
100.93.195.7 160.6