| 6:53 pm on Jan 20, 2010 (gmt 0)|
If you're on an island, that may be the problem. The sites may be operating fine to the rest of the world, it's just the traffic to your island may be the bottleneck.
| 7:09 pm on Jan 20, 2010 (gmt 0)|
engine, thank you for your reply.
But if it's an island problem, how can you explain that the problem is only with one data centre. All servers which are located in the same city but another data centers are responding fast.
| 7:46 pm on Jan 20, 2010 (gmt 0)|
This is a part from traceroute results to my server:
5 103 ms 108 ms 106 ms Xe11-0-0-0-grtpartv2.red.telefonica wholesale.net [188.8.131.52]
6 105 ms 102 ms 104 ms 184.108.40.206
7 146 ms 144 ms 151 ms 220.127.116.11
And this is a part of traceroute results to another server in the same city but in another data centre:
6 169 ms 78 ms 84 ms Tsystem-6-1-1-0-grtmadpe3.red.telefonica-wholesale.net [18.104.22.168]
7 137 ms 143 ms 135 ms 22.214.171.124
8 158 ms 158 ms 149 ms 126.96.36.199
As you can see in the first example, the route goes via USA (Ip addresses 188.8.131.52 and 184.108.40.206). In the second example the route from my ISP goes straight to the Germany. IP addresses 220.127.116.11 and 18.104.22.168.
I am right? If yes, my question is - why the route from my computer in Europe to a server in Europe goes via USA? I don't know a lot about it. Is it a fault of my ISP?
| 12:12 pm on Jan 22, 2010 (gmt 0)|
| 2:07 am on Feb 17, 2010 (gmt 0)|
I donīt believe that noone knows how Internet works and why the traceroute from Europe to Europe goes via USA.
Noone knows who creates the route from my computer to the server? Is it my ISP?
Itīs a real horror - I spent more than 3 hours saving 200 mb file. Itīs saved only for 44%.
| 1:38 am on Feb 20, 2010 (gmt 0)|
Visit your site through a proxy, if it's fast via proxy but not directly from your location the slowdown is caused by the hosting company (most likely improper redirects or configuration but it might also be intentional throttling to some ISP ranges).
| 4:25 am on Feb 20, 2010 (gmt 0)|
What you see is caused by the loose networking structure of the Internet. A good ISP has more than one connection to the outside world. If one of the connections fails, the routers of the ISP will automatically try to reroute the connections over the other available connections. Therefore the whole routing structure is not fixed, but is based on algorithms which use regularly updated tables and parameters like current bandwidth usage on each connection and errors/delays/outages encountered on the connections to decide which route to take for each packet.
It seems that your ISP has a connection directly with Europe mainland and one with the US. Which of the connections is used if you want to visit a website is based on the outcome of the routing algorithm. Probably the router algorithm calculates that the IP range of your server in mainland Europe can be best reached via the US connection. Although you know that it isn't the best connection, the router doesn't and forwards your request to their peering partner in the US.
As you are on a Spanish island, I expect the connection to Europe mainland to have a much higher bandwidth than the connection to the US. There may be even bandwidth throttling going on on that line to divide the available bandwidth evenly over many customers. I wouldn't be surprised if the connection with mainland Europe is also much cheaper for the ISP in terms of EUR/gigabyte than the US connection and that they deliberately throttle all traffic through the US pipe just to keep their costs low.
| 10:37 am on May 15, 2010 (gmt 0)|
Thank you very much for your very informative answers.
One more strange thing which I have noticed... My data center's website is never slow. My server and data center's own web server are in the same IP address range, but tracerout results are different.
And one more time - my server is not overloaded. When problems happen all servers in this DC are hardly accessible except the data centers own web server.