Question Unusually High Ping/Latency across Multiplayer Games

[iGoRecon]

Hello,

For over the past week I've been experiencing high ping across multiple different games including Tom Clancy's R6 Siege, Battlefield 4, Battlefield V and Minecraft. Today I have set up a brand new NETGEAR Router.

I am using a wired ethernet connection.

Below will be results of multiple PINGs I have performed so far. I am connecting to local regions, I usually get 15-35ms on West servers, 36-60 on Central and 61-90 on Eastern Servers but am experiencing 40-100+ ping on Western servers.

Below are tests I have ran so far.

PING to DEFAULT GATEWAY
Pinging 192.XXX.X.X with 32 bytes of data:
Reply from 192.XXX.X.X: bytes=32 time<1ms TTL=64
Reply from 192.XXX.X.X: bytes=32 time<1ms TTL=64
Reply from 192.XXX.X.X: bytes=32 time<1ms TTL=64
Reply from 192.XXX.X.X: bytes=32 time<1ms TTL=64
Reply from 192.XXX.X.X: bytes=32 time<1ms TTL=64
Reply from 192.XXX.X.X: bytes=32 time<1ms TTL=64
Reply from 192.XXX.X.X: bytes=32 time<1ms TTL=64
Reply from 192.XXX.X.X: bytes=32 time<1ms TTL=64
Reply from 192.XXX.X.X: bytes=32 time<1ms TTL=64
Reply from 192.XXX.X.X: bytes=32 time<1ms TTL=64
Reply from 192.XXX.X.X: bytes=32 time<1ms TTL=64
Reply from 192.XXX.X.X: bytes=32 time<1ms TTL=64
Reply from 192.XXX.X.X: bytes=32 time<1ms TTL=64
Reply from 192.XXX.X.X: bytes=32 time<1ms TTL=64
Reply from 192.XXX.X.X: bytes=32 time<1ms TTL=64
Reply from 192.XXX.X.X: bytes=32 time<1ms TTL=64
Reply from 192.XXX.X.X: bytes=32 time<1ms TTL=64
Reply from 192.XXX.X.X: bytes=32 time<1ms TTL=64
Reply from 192.XXX.X.X: bytes=32 time<1ms TTL=64
Reply from 192.XXX.X.X: bytes=32 time<1ms TTL=64
Reply from 192.XXX.X.X: bytes=32 time<1ms TTL=64
Reply from 192.XXX.X.X: bytes=32 time<1ms TTL=64
Reply from 192.XXX.X.X: bytes=32 time<1ms TTL=64
Reply from 192.XXX.X.X: bytes=32 time<1ms TTL=64
Reply from 192.XXX.X.X: bytes=32 time<1ms TTL=64
Reply from 192.XXX.X.X: bytes=32 time<1ms TTL=64
Reply from 192.XXX.X.X: bytes=32 time<1ms TTL=64
Reply from 192.XXX.X.X: bytes=32 time<1ms TTL=64
Reply from 192.XXX.X.X: bytes=32 time<1ms TTL=64
Reply from 192.XXX.X.X: bytes=32 time<1ms TTL=64

Ping statistics for 192.XXX.X.X:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

PING to DNS SERVERS (X.X.X.X)
Pinging X.X.X.X with 32 bytes of data:
Reply from X.X.X.X: bytes=32 time=30ms TTL=58
Reply from X.X.X.X: bytes=32 time=73ms TTL=58
Reply from X.X.X.X: bytes=32 time=41ms TTL=58
Reply from X.X.X.X: bytes=32 time=41ms TTL=58
Reply from X.X.X.X: bytes=32 time=23ms TTL=58
Reply from X.X.X.X: bytes=32 time=24ms TTL=58
Reply from X.X.X.X: bytes=32 time=19ms TTL=58
Reply from X.X.X.X: bytes=32 time=20ms TTL=58
Reply from X.X.X.X: bytes=32 time=177ms TTL=58
Reply from X.X.X.X bytes=32 time=30ms TTL=58
Reply from X.X.X.X: bytes=32 time=31ms TTL=58
Reply from X.X.X.X: bytes=32 time=21ms TTL=58
Reply from X.X.X.X: bytes=32 time=29ms TTL=58
Reply from X.X.X.X: bytes=32 time=22ms TTL=58
Reply from X.X.X.X: bytes=32 time=31ms TTL=58
Reply from X.X.X.X: bytes=32 time=32ms TTL=58
Reply from X.X.X.X: bytes=32 time=19ms TTL=58
Reply from X.X.X.X: bytes=32 time=53ms TTL=58
Reply from X.X.X.X: bytes=32 time=57ms TTL=58
Reply from X.X.X.X: bytes=32 time=46ms TTL=58
Reply from X.X.X.X: bytes=32 time=149ms TTL=58
Reply from X.X.X.X: bytes=32 time=56ms TTL=58
Reply from X.X.X.X: bytes=32 time=20ms TTL=58
Reply from X.X.X.X: bytes=32 time=24ms TTL=58
Reply from X.X.X.X: bytes=32 time=60ms TTL=58
Reply from X.X.X.X: bytes=32 time=123ms TTL=58
Reply from X.X.X.X bytes=32 time=69ms TTL=58
Reply from X.X.X.X: bytes=32 time=61ms TTL=58
Reply from X.X.X.X: bytes=32 time=70ms TTL=58
Reply from X.X.X.X: bytes=32 time=29ms TTL=58

Ping statistics for X.X.X.X:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 177ms, Average = 49ms

PING to GOOGLE.COM
Pinging www.google.com [172.217.4.132] with 32 bytes of data:
Reply from 172.217.4.132: bytes=32 time=43ms TTL=55
Reply from 172.217.4.132: bytes=32 time=33ms TTL=55
Reply from 172.217.4.132: bytes=32 time=60ms TTL=55
Reply from 172.217.4.132: bytes=32 time=30ms TTL=55
Reply from 172.217.4.132: bytes=32 time=41ms TTL=55
Reply from 172.217.4.132: bytes=32 time=27ms TTL=55
Reply from 172.217.4.132: bytes=32 time=24ms TTL=55
Reply from 172.217.4.132: bytes=32 time=44ms TTL=55
Reply from 172.217.4.132: bytes=32 time=34ms TTL=55
Reply from 172.217.4.132: bytes=32 time=26ms TTL=55
Reply from 172.217.4.132: bytes=32 time=31ms TTL=55
Reply from 172.217.4.132: bytes=32 time=31ms TTL=55
Reply from 172.217.4.132: bytes=32 time=26ms TTL=55
Reply from 172.217.4.132: bytes=32 time=28ms TTL=55
Reply from 172.217.4.132: bytes=32 time=61ms TTL=55
Reply from 172.217.4.132: bytes=32 time=27ms TTL=55
Reply from 172.217.4.132: bytes=32 time=27ms TTL=55
Reply from 172.217.4.132: bytes=32 time=28ms TTL=55
Reply from 172.217.4.132: bytes=32 time=35ms TTL=55
Reply from 172.217.4.132: bytes=32 time=27ms TTL=55
Reply from 172.217.4.132: bytes=32 time=59ms TTL=55
Reply from 172.217.4.132: bytes=32 time=49ms TTL=55
Reply from 172.217.4.132: bytes=32 time=37ms TTL=55
Reply from 172.217.4.132: bytes=32 time=39ms TTL=55
Reply from 172.217.4.132: bytes=32 time=60ms TTL=55
Reply from 172.217.4.132: bytes=32 time=32ms TTL=55
Reply from 172.217.4.132: bytes=32 time=26ms TTL=55
Reply from 172.217.4.132: bytes=32 time=43ms TTL=55
Reply from 172.217.4.132: bytes=32 time=32ms TTL=55
Reply from 172.217.4.132: bytes=32 time=29ms TTL=55

Ping statistics for 172.217.4.132:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 61ms, Average = 36ms


DOWNLOAD SPEED TEST: 120Mbps
UPLOAD SPEED TEST: 10Mbps

 

[rgd1101]

because everyone is working at home or not working at all?