Post by iconPost by DonJuan21 | 2020-05-21 | 04:20:41

I traced the IP route to VR's server farm to an Amazon AWS server in Dublin. If you want to have quicker connection and use a VPN (as everyone should be), choose an exit node there.

DonJuan21

commenticon 2 Comments
Post by iconPost by zezo | 2020-05-21 | 09:13:12
It's a bit more complicated.

static.virtualregatta.com where most of the data comes from is a CDN, in hundreds of physical locations.

For me (asking the right DNS) it's located in Sofia, Bulgaria (server-52-84-112-103.sof50.r.cloudfront.net) which is 5 hops and less than millisecond from me. No VPN can beat that ;-)

zezo@zezo:~$ ping static.virtualregatta.com
PING static.virtualregatta.com (52.84.112.96): 48 data bytes
56 bytes from 52.84.112.96: icmp_seq=0 ttl=248 time=0.687 ms
56 bytes from 52.84.112.96: icmp_seq=1 ttl=248 time=0.828 ms
56 bytes from 52.84.112.96: icmp_seq=2 ttl=248 time=0.721 ms

Post by iconPost by DonJuan21 | 2020-05-21 | 23:09:35
You are right. It's way more complicated. I hadn't considered the CDN factor.

I set an exit node in Sofia, Bulgaria to see if I could match your numbers. But now I'm tracing the route to Tokyo.

dolive@zeeman:~$ ping static.virtualregatta.com
PING static.virtualregatta.com (54.239.195.57) 56(84) bytes of data.
64 bytes from server-54-239-195-57.otp50.r.cloudfront.net (54.239.195.57): icmp_seq=1 ttl=245 time=170 ms
64 bytes from server-54-239-195-57.otp50.r.cloudfront.net (54.239.195.57): icmp_seq=2 ttl=245 time=161 ms
64 bytes from server-54-239-195-57.otp50.r.cloudfront.net (54.239.195.57): icmp_seq=3 ttl=245 time=166 ms

When I set an exit node to Atlanta Georgia I'm getting around 35ms. That's the best I could do.

Seems like the DNS lag outstrips the network lag. I'm checking a good DNS benchmark on my network now.

Don

border
Topics list
Posts
border
5
border
border
Copyright 2009 by ZEZO.ORG. All Rights Reserved.