Ping latency from Europe to Bali

alucard

Hi, does anyone know the ping latency times from Bali to Europe (Germany)? I am asking because I would like to relocate to Bali. For my work I need a good latency to Servers in germany. It is important to have little delays for working on remote servers using a shell. I remember that working from china was not possible that way because the latency was to high. Can anyone help me to find out the pings from Bali to Germany? I would setup a server here. I just need someone who can perform a ssh login to a server and measure the latency. Regards, alucard

spicyayam

If the internet is a concern, then Bali is probably not going to work out. Some providers are better than others, but overall the experience is fairly poor. If you compare though the internet with other infrastructure and consider Indonesia as a developing country then it is not too bad. https://www.speedtest.net/global-index

Markit

Depends entirely on your application - if it's just transfer of texts or normal pictures than no problem but if you need live video linking/conferencing then you will need to pay for that kind of bandwidth. Saying that Biznet offer between 30 and 80Mbit upload rates with corresponding downloading. But having seen whats "normal" in southern Germany you shouldn't have any problem here.

alucard

As I said. What matters is the latency and not the bandwidth. My concrete usecase is working in a shell on a remote server from Europe. AFAIR the bandwidth was absolutely fine in Bali. I found a server in indonesia I can ping and my latency is 250-350 ms. But I would like to test it in a real scenario. [CODE]ping berlin.de PING berlin.de(www.berlin.de (2a00:cd0:1002:1::17)) 56 data bytes 64 bytes from www.berlin.de (2a00:cd0:1002:1::17): icmp_seq=1 ttl=57 time=15.6 ms 64 bytes from www.berlin.de (2a00:cd0:1002:1::17): icmp_seq=2 ttl=57 time=23.4 ms[/CODE]

spicyayam

[CODE]$ ping berlin.de PING berlin.de (212.45.111.17) 56(84) bytes of data. 64 bytes from 17.111.45.212.in-addr.arpa (212.45.111.17): icmp_seq=1 ttl=243 time=208 ms 64 bytes from 17.111.45.212.in-addr.arpa (212.45.111.17): icmp_seq=2 ttl=243 time=208 ms 64 bytes from 17.111.45.212.in-addr.arpa (212.45.111.17): icmp_seq=3 ttl=243 time=207 ms 64 bytes from 17.111.45.212.in-addr.arpa (212.45.111.17): icmp_seq=4 ttl=243 time=208 ms 64 bytes from 17.111.45.212.in-addr.arpa (212.45.111.17): icmp_seq=5 ttl=243 time=210 ms 64 bytes from 17.111.45.212.in-addr.arpa (212.45.111.17): icmp_seq=6 ttl=243 time=207 ms 64 bytes from 17.111.45.212.in-addr.arpa (212.45.111.17): icmp_seq=7 ttl=243 time=208 ms 64 bytes from 17.111.45.212.in-addr.arpa (212.45.111.17): icmp_seq=8 ttl=243 time=207 ms 64 bytes from 17.111.45.212.in-addr.arpa (212.45.111.17): icmp_seq=9 ttl=243 time=207 ms 64 bytes from 17.111.45.212.in-addr.arpa (212.45.111.17): icmp_seq=10 ttl=243 time=208 ms ^C --- berlin.de ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 9013ms rtt min/avg/max/mdev = 207.289/208.261/210.745/1.063 ms [/CODE]