Router: A1300 Slate Plus (and replicated on AR300M16 Shadow)
Firmware version: 4.5.16
Connected via Wifi to network, and then either LAN or repeater to client. Same issue.
Have experienced issue with both Wireguard and Openvpn
I’m experiencing very spiky connections that can get up to 100 MBPS in speedtests (slowly and often with lots of jitter) and the the packet loss is very high. It often seems to do well for a while and then the packets start to get lost. Video calls becomes impossible and speeds drop tremendously to 0-5 MBPS. This only happens when connected to Wifi at a WeWork coworking location. The overall bandwidth seems fine because when not using the router, WeWork connection speeds are stable at 100+ MBPS.
Could this be something to do with WeWork’s Network/ISP? It seems like WeWork is throttling the VPN router traffic somehow. Are there ways to get around this?
Here’s a sample ping report.
@-Laptop ~ % ping google.com
PING google.com (142.250.113.101): 56 data bytes
64 bytes from 142.250.113.101: icmp_seq=0 ttl=58 time=68.008 ms
64 bytes from 142.250.113.101: icmp_seq=1 ttl=58 time=74.015 ms
64 bytes from 142.250.113.101: icmp_seq=2 ttl=58 time=67.517 ms
64 bytes from 142.250.113.101: icmp_seq=3 ttl=58 time=74.304 ms
64 bytes from 142.250.113.101: icmp_seq=4 ttl=58 time=66.843 ms
64 bytes from 142.250.113.101: icmp_seq=5 ttl=58 time=71.560 ms
64 bytes from 142.250.113.101: icmp_seq=6 ttl=58 time=73.218 ms
64 bytes from 142.250.113.101: icmp_seq=7 ttl=58 time=153.451 ms
64 bytes from 142.250.113.101: icmp_seq=8 ttl=58 time=347.384 ms
64 bytes from 142.250.113.101: icmp_seq=9 ttl=58 time=87.202 ms
64 bytes from 142.250.113.101: icmp_seq=10 ttl=58 time=73.566 ms
64 bytes from 142.250.113.101: icmp_seq=11 ttl=58 time=67.509 ms
64 bytes from 142.250.113.101: icmp_seq=12 ttl=58 time=73.130 ms
64 bytes from 142.250.113.101: icmp_seq=13 ttl=58 time=75.663 ms
64 bytes from 142.250.113.101: icmp_seq=14 ttl=58 time=153.797 ms
64 bytes from 142.250.113.101: icmp_seq=15 ttl=58 time=76.728 ms
64 bytes from 142.250.113.101: icmp_seq=16 ttl=58 time=69.917 ms
64 bytes from 142.250.113.101: icmp_seq=17 ttl=58 time=70.914 ms
64 bytes from 142.250.113.101: icmp_seq=18 ttl=58 time=73.231 ms
Request timeout for icmp_seq 19
Request timeout for icmp_seq 20
Request timeout for icmp_seq 21
Request timeout for icmp_seq 22
Request timeout for icmp_seq 23
Request timeout for icmp_seq 24
Request timeout for icmp_seq 25
Request timeout for icmp_seq 26
Request timeout for icmp_seq 27
Request timeout for icmp_seq 28
Request timeout for icmp_seq 29
Request timeout for icmp_seq 30
Request timeout for icmp_seq 31
Request timeout for icmp_seq 32
Request timeout for icmp_seq 33
64 bytes from 142.250.113.101: icmp_seq=34 ttl=58 time=78.820 ms
^C
— google.com ping statistics —
35 packets transmitted, 20 packets received, 42.9% packet loss
round-trip min/avg/max/stddev = 66.843/94.839/347.384/62.908 ms