Antares is terribly jittery

[Fearn 0]

Here is an example ping to google (or any other site) with Antares (SG).
 

 

Reply from 216.58.196.196: bytes=32 time=23ms TTL=55
Request timed out.
Reply from 216.58.196.196: bytes=32 time=23ms TTL=55
Reply from 216.58.196.196: bytes=32 time=23ms TTL=55
Reply from 216.58.196.196: bytes=32 time=23ms TTL=55
Reply from 216.58.196.196: bytes=32 time=24ms TTL=55
Reply from 216.58.196.196: bytes=32 time=24ms TTL=55
Reply from 216.58.196.196: bytes=32 time=23ms TTL=55
Reply from 216.58.196.196: bytes=32 time=23ms TTL=55
Reply from 216.58.196.196: bytes=32 time=93ms TTL=55
Reply from 216.58.196.196: bytes=32 time=23ms TTL=55
Reply from 216.58.196.196: bytes=32 time=23ms TTL=55
Reply from 216.58.196.196: bytes=32 time=24ms TTL=55
Reply from 216.58.196.196: bytes=32 time=23ms TTL=55
Reply from 216.58.196.196: bytes=32 time=23ms TTL=55
Reply from 216.58.196.196: bytes=32 time=23ms TTL=55
Request timed out.
Reply from 216.58.196.196: bytes=32 time=23ms TTL=55
Reply from 216.58.196.196: bytes=32 time=24ms TTL=55
Reply from 216.58.196.196: bytes=32 time=23ms TTL=55
Request timed out.
Reply from 216.58.196.196: bytes=32 time=23ms TTL=55
Reply from 216.58.196.196: bytes=32 time=23ms TTL=55
Request timed out.
Reply from 216.58.196.196: bytes=32 time=23ms TTL=55
Reply from 216.58.196.196: bytes=32 time=23ms TTL=55
Reply from 216.58.196.196: bytes=32 time=24ms TTL=55
Reply from 216.58.196.196: bytes=32 time=23ms TTL=55
Request timed out.
Request timed out.
Reply from 216.58.196.196: bytes=32 time=23ms TTL=55
 

 

 
This is not from my side. I have tried various ISP and location but Antares always has these ridiculous request time outs every few seconds. It's been like this since... forever (a year? since I first registered that is), actually, although I only get to post this now. This is not the case with any other server I select, including Hadar / Cebalrai (HK).

 

Antares has the lowest latency I can obtain, and is required in some things I do which Hadar can't replace, but it's unbelievably frustrating to have to deal with these time outs.

I doubt there is any solution though, I just feel like I need to inform AirVPN about this.

[Staff 10019]

Hello,

 

from inside Antares there are no packet loss to Google, so the problem is somewhere between Antares and your ISP(s). Compare also with the Ping Matrix and Antares history:

 

https://airvpn.org/pingmatrix

 

https://airvpn.org/servers/Antares

 

which show sporadic and minimal packet loss in Antares. Totally irrelevant.

 

Kind regards

[Fearn 0]

I see. I have tried over 5 ISP all with same result. Then I will assume this is indeed not possible to solve.

 

Thanks.

[Staff 10019]

Hello,

 

as you can see it does not look like it's on Antares.Maybe traceroute from those five ISPs could provide some hint but again we could do nothing, Antares and datacenter look perfect from all the major transit providers we use in 17 countries.

 

Kind regards

[Fearn 0]

I am sure Antares is fine. However there's probably a bad server that all my 5+ ISP route to before reaching Antares, which is most likely the problem. However at this point I might as well say there is no way to fix it, but thanks anyway!   

[Crimson 0]

I'm having problem with Antares for about a day. And few minutes ago I totally lost VPN connection.

Below is the log:

Feb 17 21:51:58 unknown user.notice root: vpnrouting: searching gateway for tun11
Feb 17 21:52:00 unknown daemon.warn openvpn[1010]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Feb 17 21:52:00 unknown daemon.notice openvpn[1010]: Socket Buffers: R=[114688->131072] S=[114688->131072]
Feb 17 21:52:00 unknown daemon.notice openvpn[1010]: UDPv4 link local: [undef]
Feb 17 21:52:00 unknown daemon.notice openvpn[1010]: UDPv4 link remote: [AF_INET]103.254.153.68:443
Feb 17 21:52:01 unknown user.notice root: vpnrouting: searching gateway for tun11
Feb 17 21:52:04 unknown user.notice root: vpnrouting: searching gateway for tun11
Feb 17 21:52:07 unknown user.notice root: vpnrouting: searching gateway for tun11
Feb 17 21:52:10 unknown user.notice root: vpnrouting: searching gateway for tun11
Feb 17 21:52:13 unknown user.notice root: vpnrouting: searching gateway for tun11
Feb 17 21:52:16 unknown user.notice root: vpnrouting: searching gateway for tun11
Feb 17 21:52:18 unknown daemon.err openvpn[1010]: event_wait : Interrupted system call (code=4)
Feb 17 21:52:18 unknown daemon.notice openvpn[1010]: OpenVPN STATISTICS
Feb 17 21:52:18 unknown daemon.notice openvpn[1010]: Updated,Wed Feb 17 21:52:18 2016
Feb 17 21:52:18 unknown daemon.notice openvpn[1010]: TUN/TAP read bytes,0
Feb 17 21:52:18 unknown daemon.notice openvpn[1010]: TUN/TAP write bytes,0
Feb 17 21:52:18 unknown daemon.notice openvpn[1010]: TCP/UDP read bytes,0
Feb 17 21:52:18 unknown daemon.notice openvpn[1010]: TCP/UDP write bytes,168
Feb 17 21:52:18 unknown daemon.notice openvpn[1010]: Auth read bytes,0
Feb 17 21:52:18 unknown daemon.notice openvpn[1010]: pre-compress bytes,0
Feb 17 21:52:18 unknown daemon.notice openvpn[1010]: post-compress bytes,0
Feb 17 21:52:18 unknown daemon.notice openvpn[1010]: pre-decompress bytes,0
Feb 17 21:52:18 unknown daemon.notice openvpn[1010]: post-decompress bytes,0
Feb 17 21:52:19 unknown user.notice root: vpnrouting: searching gateway for tun11
Feb 17 21:52:22 unknown user.notice root: vpnrouting: searching gateway for tun11

[Khariz 109]

The total loss of connection could have been this:  https://airvpn.org/topic/16738-immediate-emergency-maintenance-on-all-servers/

 

Can't explain the other stuff