Very high latency and packet loss on cryptofree nodes

a917d21a · Post by **a917d21a** » Mon Nov 21, 2016 2:10 am

Hello.

I haven't been using Cryptostorm for a few months and now, being out of the tokens, tried using Cryptofree.
I get ping times on the order of 1.5 sec, serious packet loss, and download speeds about 40 KB/s, so the connection is practically unusable.

I understand that Cryptofree is a free service, and don't expect much, but I occasionally used it before without any issues.

Are there any problems with Cryptofree, or Cryptostorm infrastructure?
Or should I blame my ISP or myself?
Thanks.

Here are some diagnostics.

212.129.10.40 node.

Ping to the server looks fine:

Code: Select all

--- 212.129.10.40 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 1806ms
rtt min/avg/max/mdev = 71.450/76.774/82.009/3.083 ms

After VPN is connected (OpenVPN 2.3.2 x86_64-pc-linux-gnu, latest cryptofree config from Github, just changed the server from random to 212.129.10.40) - ping to the gateway is pretty bad:

Code: Select all

--- 10.55.0.1 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 1843ms
rtt min/avg/max/mdev = 386.780/556.713/692.390/106.199 ms, pipe 4

Sometimes - without me doing anything - ping times drop to normal values, and then rise again in a few minutes:

Code: Select all

--- 10.55.0.1 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 1805ms
rtt min/avg/max/mdev = 73.664/83.626/104.782/8.625 ms

Ping to Google with VPN connected - no good at all:

Code: Select all

$ ping -c10 -i0.2 google.com
PING google.com (173.194.44.78) 56(84) bytes of data.
64 bytes from 173.194.44.78: icmp_seq=5 ttl=52 time=1666 ms
64 bytes from 173.194.44.78: icmp_seq=6 ttl=52 time=2116 ms
64 bytes from 173.194.44.78: icmp_seq=7 ttl=52 time=2037 ms
64 bytes from 173.194.44.78: icmp_seq=8 ttl=52 time=2094 ms
64 bytes from 173.194.44.78: icmp_seq=10 ttl=52 time=2202 ms

--- google.com ping statistics ---
10 packets transmitted, 5 received, 50% packet loss, time 1871ms
rtt min/avg/max/mdev = 1666.764/2023.375/2202.204/186.032 ms, pipe 6

212.129.34.154 node.
Ping to the host isn't good, so VPN is bad as well.

Code: Select all

--- 212.129.34.154 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 1829ms
rtt min/avg/max/mdev = 313.723/451.955/544.070/72.848 ms, pipe 3

Traceroute breaks midway, so not much help from it:

Code: Select all

traceroute to 212.129.34.154 (212.129.34.154), 30 hops max, 60 byte packets
-- snip --
 8  ffm-b7-link.telia.net (213.248.104.253)  69.126 ms  66.350 ms  65.971 ms
 9  ffm-bb3-link.telia.net (62.115.143.94)  65.940 ms ffm-bb3-link.telia.net (80.91.251.233)  57.613 ms ffm-bb3-link.telia.net (80.91.247.74)  66.911 ms
10  prs-bb2-link.telia.net (62.115.122.118)  70.219 ms prs-bb3-link.telia.net (62.115.123.21)  73.439 ms prs-bb3-link.telia.net (62.115.123.19)  65.615 ms
11  prs-b8-link.telia.net (62.115.118.55)  70.901 ms prs-b8-link.telia.net (62.115.118.89)  69.534 ms prs-b8-link.telia.net (62.115.118.41)  74.283 ms
12  online-ic-315748-prs-b8.c.telia.net (62.115.63.94)  68.408 ms  70.783 ms  73.329 ms
13  45-s103-1-dc2-a9k2.dc3.poneytelecom.eu (195.154.1.125)  69.685 ms  69.021 ms  68.049 ms
14  * * *
15  * * *