Network latency issue

  • 1
  • Problem
  • Updated 6 years ago
Hi,

I'm having network performance issues connecting to my site. I'm connecting from EU. I got some tracing and see the slowness is on your side, somewhere within the Prolexic's network, which I suppose is your network service provider.

There are 3 hops in the path that introduce a very high latency, they are listed below:

13 ms 11 ms 11 ms prolexic-technologies.tengigabitethernet12-1.ar9.lon3.gblx.net [208.178.60.242]
12 ms 14 ms 13 ms unknown.prolexic.com [209.200.156.34]
11 ms 11 ms 11 ms unknown.prolexic.com [72.52.4.95]

Any network packet from here (EU) to USA takes less than 1ms then, when it reaches your network, it gets 11 times slower (at least)

Is this by design or it is a temporary routing path due to a tech issue ? If it's by design, I think I have to move my site somewhere else.
Please let me know, because we just started a new business and we are not happy with this behavior, our site is empty at moment, we have only a basic homepage with contact details ... and it takes ages to shop up in the browser

Thanks
Regards
Vin
Photo of vcnz

vcnz

  • 18 Posts
  • 1 Reply Like

Posted 6 years ago

  • 1
Photo of Jonathan Hitchcock

Jonathan Hitchcock

  • 37 Posts
  • 16 Reply Likes
Hi Vin,

Firstly, if I traceroute any American server from my personal server in Germany, I get much higher latencies than that.

Here is an excerpt from a trace to newyorktimes.com:

8 xe-5-2-0.mpr1.lhr3.uk.above.net (64.125.24.81) 34.257 ms 32.290 ms 32.264 ms
9 ge-3-3-0.mpr1.la5.us.above.net (64.125.26.37) 88.998 ms 88.729 ms 89.070 ms

Which, as you can see, jumps by 54ms (from 34 to 88) when it crosses the Atlantic.

A trace to whitehouse.gov jumps from 32ms to 113ms when it crosses the pond:

13 xe-5-3-0.cr1.lhr1.uk.nlayer.net (69.22.142.94) 32.226 ms xe-11-1-0.cr1.nyc2.us.nlayer.net (69.22.142.90) 93.932 ms 93.930 ms
14 xe-1-2-1.cr2.ord1.us.nlayer.net (69.22.142.85) 113.133 ms 113.132 ms xe-8-1-0.cr1.nyc2.us.nlayer.net (69.22.142.62) 95.020 ms

So, a latency of 13ms doesn't seem that bad - you are probably actually hitting one of our edge servers in Europe instead of actually crossing to the US.

One further point... it is 3470 miles from London to New York. The speed of light is 186282 miles per second. So, travelling at the speed of light, it would take 18ms to cross the Atlantic. So 13ms latency really seems pretty good to me?

I hope this sets your mind at ease.

Cheers,
-Jonathan
Photo of Big G

Big G

  • 65 Posts
  • 1 Reply Like
I'm also suffering from this ..... over all my sites. The image heavy sites (I say image heavy but most the pictures are less than 50kb are slow to load). This only began over the last few days, before my sites used to load at lightening speed.

So, something has changed.
Photo of Big G

Big G

  • 65 Posts
  • 1 Reply Like
p.s. I'm also getting more than the usual gateway timeouts with the odd error network guru page thrown in too.
Photo of Big G

Big G

  • 65 Posts
  • 1 Reply Like
In fact, it's slowly getting worse. :

Load times are anything between 1 and 20 seconds to load a page, across over 50 sites. Hope this helps.
Photo of vcnz

vcnz

  • 18 Posts
  • 1 Reply Like
Hi Jonathan,

thanks for checking, but 13ms is ages for the connection I have, so it's ages for my customers that try to connect to my site too in the future.
If you would be happy with that latency on your network, I tell you I reach any sites in US from Amsterdam within 3-4 ms in the worst case scenario.

See the last hops before reaching withhouse.gov from here:

....
6 1 ms 1 ms 1 ms 84.116.136.30
7 1 ms 1 ms 1 ms adm-b5-link.telia.net [213.248.86.237]
8 2 ms 2 ms 2 ms 80-239-197-14.customer.teliacarrier.com [80.239.197.14]
9 1 ms 1 ms 2 ms a72-246-172-110.deploy.akamaitechnologies.com [72.246.172.110]

So for me (and my potential customers) 12-13ms of latency means the connection to the YOLA site IS 12-13 TIMES SLOWER
So a user that for instance is able to reach any site in 50ms, will take 700ms (at least) when connects to the yola site. This basically means TIME-OUT !

Please see other complains about this.

I want to underline that I get the slowness when my packet hits your network in US. Please check the ip I sent with a GeoIP service and you will see

Could you please escalate this issue if you're not able to pinpoint the cause ?
This is not expected

Thanks a lot
Regards
Vin
Photo of vcnz

vcnz

  • 18 Posts
  • 1 Reply Like
ops I just started to get this in my browser:

504 Gateway Time-out
The server didn't respond in time.

It's getting worst
Photo of Jonathan Hitchcock

Jonathan Hitchcock

  • 37 Posts
  • 16 Reply Likes
Hi Vin,

You did see my calculation about how long it takes to cross the Atlantic at the speed of light, right? It is a violation of the laws of physics for information to get from the US to Amsterdam in less than 18ms.

I must point out that your whitehouse.gov trace ends on an akamaitechnologies.com server, which is owned by Akamai, a content delivery network (CDN). They use a DNS system called "Anycast" (see http://en.wikipedia.org/wiki/Anycast) to run multiple identical servers in various locations around the world, and ensure that you always load resources from the one closest to you. Thus, a GeoIP service would not give the correct result, and you are probably connecting to a geographically close server, thus having a low latency.

All of this said, I don't want you to think I am making excuses or trying to divert from your original issue. We do try to maintain a high level of performance on our servers, and I am trying to replicate the problem you describe.

I asked a friend to run some traces from his machine in the UK, and he also could not discern any noticeable difference between Yola and other US-based sites.

So, I must reiterate that the speed of light is a physical limitation for information exchange, and that some of your scans are landing on CDN edge-nodes which will be physically located in Europe, so the numbers you're giving seem consistent with a pretty good turn-around time on the network.
Photo of Big G

Big G

  • 65 Posts
  • 1 Reply Like
"So, I must reiterate that the speed of light is a physical limitation for information exchange, and that some of your scans are landing on CDN edge-nodes which will be physically located in Europe, so the numbers you're giving seem consistent with a pretty good turn-around time on the network."

Nice physics analogy, but my sites, the sites on other Yola customers packages i've built for customers are all running well below par. We're talking up to 20 seconds to load a page, across all the sites, those that don't time out that is, and those that don't throw up Error 503 message.

This is the worst i've seen the sites run in a long time. The issue is intermittent, so recreating it my take more than clicking on a site this end.

So, while you say "your friend" can see no discernable differences, at this end, from my point of view, it's very poor. Would you like me to start a different thread?