Hi all, I'm hosting my website with Site 5 and I am using hosting on data center that is located in Amsterdam, Netherlands. My problem is that in last few weeks my website became very slow and when I checked the site IP address I got 108.174.149.222 and that IP is located in United States. Now when I asked Site 5 support how come that my site is hosted on EU server in Amsterdam when the IP is from US they answered that theirs data centers use US IP address... I just don't believe that my site is hosted on EU datacenter. Could you please tell me is there a way to check where it is hosted and is their answer possible. Thank you.
It would appear as if it is in fact in Amsterdam: Tracing route to s7-amsterdam.accountservergroup.com [108.174.149.222] over a maximum of 30 hops: 1 38 ms 163 ms 26 ms xx.xx.xx.xx 2 10 ms 10 ms 11 ms xx.xx.xx.xx 3 17 ms 16 ms 16 ms so-4-0-2.CR1.REA2.ALTER.NET [158.43.252.13] 4 16 ms 9 ms 11 ms ge-0-2-0.XT1.LND9.ALTER.NET [158.43.252.21] 5 15 ms 23 ms 62 ms xe-11-1-0.BR2.LND18.ALTER.NET [140.222.232.153] 6 80 ms 13 ms 15 ms r01.londen03.uk.bb.gin.ntt.net [146.188.112.18] 7 16 ms 17 ms 21 ms ae-4.r02.londen03.uk.bb.gin.ntt.net [129.250.2.1 26] 8 16 ms 15 ms 16 ms ae-3.r02.londen05.uk.bb.gin.ntt.net [129.250.2.1 19] 9 11 ms 12 ms 16 ms 83.231.204.150 10 21 ms 19 ms 20 ms ae7.bbr02.tg01.lon01.networklayer.com [50.97.18. 207] 11 25 ms 25 ms 24 ms ae0.bbr02.eq01.ams02.networklayer.com [50.97.18. 211] 12 22 ms 23 ms 20 ms ae6.dar02.sr01.ams01.networklayer.com [50.97.18. 251] 13 * * * Request timed out. 14 24 ms 24 ms 26 ms s7-amsterdam.accountservergroup.com [108.174.149 .222] Code (markup):
Site5 uses data centers such as SoftLayer, SingleHop and others. Its not uncommon to see IPs registered in the US with end points across the pond. Try a trace to see where the latency is coming from. Mark
IP address WHOIS data can be differ with where the actual physical server located. based on the traceroute of the IP address you've given, the server is located in Amsterdam
Hi, I guess that before getting to traceroute and MTRs, we can go down to plain old physics. The light travels at 300.000Km/s. Doing some simple math reveals that a network packet travels 7500 Km in 25 ms. Under ideal conditions (no network gear induced latencies) an echo reply of 25ms packet translates into a 3750 Km journey to the designated target and 3750 Km back to your host. That is under ideal conditions. In real life, expect for a 25ms packet reply to travel 2000-2500 Km because the network equipment induces a certain latency in packet forwarding, especially when dealing with ICMP which is tratead like a best effort protocol by most network equipment. Long story short, if you see that your host replies within less than 50ms it is likely that it's geographic location is on a radius of less than 7500 Km under ideal conditions and less than roughly 3500 Km under real life conditions. In other words, if your echo reply times are larger than 100 ms, chances are that your server is on another continent, maybe 10.000 Km away, or they are network induced latencies, or they are routing their traffic in an unusual way, but if the host responds within 50ms, it can't be that far, as you can not beat the speed of light under normal conditions.
You may also find you can 'hire' IP addresses or even a RIPE block for a different country, but have them still point at your Amsterdam server. I use a French company for servers, but rent British IP addresses for them at £1 a month each.