How to reduce ping from Thailand (Phuket) to a server in Russia for comfortable work via ssh? VPN, etc?

Question

VPN

Good afternoon!
Faced the problem of "slow" Internet in Phuket.
There is an ADSL modem provider 3BB (10 Mbps).
Requires low ping to work comfortably via ssh.
Ping from here to my server ~300-500ms.
Ping from the server to my ISP's gateway in Thailand is 300ms.
Maybe there is some kind of VPN server, from where the ping is decent in both directions.
Maybe there are some special local providers?
Maybe there are other ways to implement a high-speed tunnel?
os:ubuntu
traceroute:

1  192.168.1.1 (192.168.1.1)  1.338 ms  1.772 ms  2.836 ms
2  10.121.83.77 (10.121.83.77)  136.591 ms  137.701 ms  138.581 ms
3  10.121.83.78 (10.121.83.78)  156.070 ms  156.927 ms  158.860 ms
4  mx-ll-110.164.0-156.static.3bb.co.th (110.164.0.156)  160.138 ms  162.337 ms  164.052 ms
5  * * *
6  * mx-ll-110.164.1-117.static.3bb.co.th (110.164.1.117)  162.901 ms  129.654 ms
7  mx-ll-110.164.0-49.static.3bb.co.th (110.164.0.49)  186.518 ms  188.080 ms  191.001 ms
8  20485.hkg.equinix.com (119.27.63.53)  417.541 ms  417.568 ms  417.840 ms
9  Krasn-net-gw.transtelecom.net (217.150.52.17)  397.693 ms * *

Answer 1

MOSH put.

Answer 2

Sorry for replying to an old thread.
But faced the same problem ping to my projects from Tai 300-500 ms.
Went through some providers.
3BB and dtac have the best results.
The problem is rather in the crooked route between countries.
Now 09/28/2015 is much better than in April of this year. The second submarine cable was restored, which connects the entire Southeast Asia.
I also found that through Swedish or Arabic VPNs the path straightens (less buggy nodes on the way).
Plus strongly influences upload. Because asynchronous ADSL is flourishing in Thailand. I had to transfer backups to outside working hours.
Watch carefully tracert through whom the route goes.
Use the mtr utility.
I had a problem with the 3BB provider on their line. Called and fixed the problem.
But the route through Sweden remains gorgeous. Instead of 460 pings I get 360 and no packet loss.
The type of equipment you have also has a big effect. Free routers from providers are a horror.
And to be honest, for 7 months, work with a ping of 360-600 has become the norm.
About mtr and tracing.
The goal is to achieve after the provider's network one single intermediate network, behind which there will immediately be a network of that provider where your services are connected.
If there are two or three such networks or more than one hop, then there are all the problems
. I have a 62 ms ping to Bangkok.
Further 250-240 ms to this international backbone network.
Further 360-450 ms to the provider's network in Moscow time.
Through the Swedes if.
To 62 Bangkok.
150-200 Swedish network
300-360 Moscow time.
And in Msk 1-2 hop, not 4-5 if directly.
I 'll also add ToT - a terrible provider
Ping is the same, but packet loss is 10-20% ...
Well, yes, for ssh use screen , for rdp - compression and 8 bits. Yes, yes, I sometimes sit on RDP with such a ping.

Answer 3

Once there was a problem with ping in games, I found a script similar to this . Which reduced ping not only in games, but also the connection speed with the server was faster.

Answer 4

Here I met such an article on Habré, maybe it will help, take a look.

Answer 5

look for a short route
tyts
Ps: A lot of humor)

Answer 6

I bought an account on HideMyAss (they provide a bunch of VPN servers).
I pinged all the VPN servers of this service from Thailand (701 pieces) with scripts, I did the same from Russia.
I found the most optimal ones in terms of ping (one of them ended up in Hong Kong) on ​​both sides, I managed to bring down the ping to 260 ms (-60 ms).
But this is not enough.
Still hoping for an existing solution.

Answer 7

Before Krasnoyarsk, ping will not be better, 3bb has better connectivity, I want more stability, run a cable, not a modem,
I have a very stable ping
Packet exchange
from 217.150. =345ms TTL=239
Reply from 217.150.52.17: number of bytes=32 time=350ms TTL=239
Reply from 217.150.52.17: number of bytes=32 time=348ms TTL=239
Reply from 217.150.52.17: number of bytes=32 time=344ms TTL=239
Reply from 217.150.52.17: number of bytes=32 time=344ms TTL=239
Reply from 217.150.52.17: number of bytes=32 time=349ms TTL=
239 one third of a second completely suits me, there are no lags.