Terrible packet loss in Canada

[Baraka 32]

I've been with AirVPN for a long, long time. I wrote the original Tomato router guide. I've never had problems like this before. The packet loss is very persistent. Kornephoros is the only node in eastern Canada where I am not having any problems. It's a meganode and that may speak to its capacity to handle large volumes of packets.

I was getting the same packet loss in NYC on Muliphein, but that suddenly resolved. Still, half of the six NYC meganodes are jittery, with lots of latency spikes.

I just rechecked everything. I also checked both the first and second hops off each VPN node to make sure that the packet loss is consistent and not localized to one node/router.

Can anyone at AirVPN figure out what's going on? I already talked to both my ISP and carrier about this and can completely rule out any problems with my connection physically, or at layers 2 or 3. See below for the latency and packet loss numbers.

Lacerta:

96 of 100 packets returned successfully : 4.0% PACKET LOSS 
Round Trip Time (in milliseconds) Maximum/ Minimum/Average: 146/0/75

Ross:

98 of 100 packets returned successfully : 2.0% PACKET LOSS 
Round Trip Time (in milliseconds) Maximum/ Minimum/Average: 166/0/58

Cephei:

95 of 100 packets returned successfully : 5.0% PACKET LOSS 
Round Trip Time (in milliseconds) Maximum/ Minimum/Average: 24/0/18

Kornephoros:

100 of 100 packets returned successfully : 0.0% PACKET LOSS 
Round Trip Time (in milliseconds) Maximum/ Minimum/Average: 32/0/18

Mintaka:

93 of 100 packets returned successfully : 7.0% PACKET LOSS 
Round Trip Time (in milliseconds) Maximum/ Minimum/Average: 76/0/21

Tejat:

86 of 100 packets returned successfully : 14.0% PACKET LOSS 
Round Trip Time (in milliseconds) Maximum/ Minimum/Average: 23/0/19

Tyl:

95 of 100 packets returned successfully : 5.0% PACKET LOSS 
Round Trip Time (in milliseconds) Maximum/ Minimum/Average: 24/0/18

Muliphein:

100 of 100 packets returned successfully : 0.0% PACKET LOSS 
Round Trip Time (in milliseconds) Maximum/ Minimum/Average: 262/0/31

Paikauhale:

100 of 100 packets returned successfully : 0.0% PACKET LOSS 
Round Trip Time (in milliseconds) Maximum/ Minimum/Average: 50/0/28

Sadalmelik:

100 of 100 packets returned successfully : 0.0% PACKET LOSS 
Round Trip Time (in milliseconds) Maximum/ Minimum/Average: 193/0/30

Terebellum:

100 of 100 packets returned successfully : 0.0% PACKET LOSS 
Round Trip Time (in milliseconds) Maximum/ Minimum/Average: 280/0/40

Unukalhai:

100 of 100 packets returned successfully : 0.0% PACKET LOSS 
Round Trip Time (in milliseconds) Maximum/ Minimum/Average: 44/0/28

Unurgunite:

100 of 100 packets returned successfully : 0.0% PACKET LOSS 
Round Trip Time (in milliseconds) Maximum/ Minimum/Average: 86/0/29

 

[Staff 10423]

@Baraka

Thank you.

After the private dialogue in the ticket you kindly opened with the support team we could manage to reduce the packet loss of Tyl and Tejat to 1% from/to the mentioned servers to/from the dozens of datacenter we operate servers in. Packet loss ≤ 1% is ideal for any application and purpose.

Can you confirm that the problem is solved in Tyl and Tejat?

We will proceed in the near future to investigate again about Mintaka, Lacerta and Cephei, where we could not reproduce the problem during our initial tests (we detected packet loss ≈ 0.0%).

Kind regards