Question Trying to figure out the source of inconsistent packet loss and ping spikes

Aug 24, 2022
6
0
10
0
In the beginning of August, I have been playing video games, and recently my ping has been really inconsistent, which is typically paired with packet loss. Typically, I would average around 11-15ms of latency in game, with zero packet loss. Now, sometimes I would get 11-15ms one game, and the next game I would get 40-50ms of latency, while losing 500-1000 packets every minute.

I am trying to find out the reasoning behind the inconsistencies behind my ping and packet loss, so I did some research. I seem to have a similar problem to user ypmxx in the following thread: https://forums.tomshardware.com/threads/packet-loss.3740059/

I did everything from restarting the router, changing ethernet cable, changed ip address on Windows, etc.

I then followed instructions within the thread regarding "tracert 8.8.8.8" and pinging certain hops.

C:\WINDOWS\system32>tracert 8.8.8.8

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168..
2 * * * Request timed out.
3 4 ms 3 ms 3 ms te2-3-0-4---0.lcr01.ontr.ca.frontiernet.net [172.102.105.244]
4 * 4 ms 4 ms ae8---0.scr02.lsan.ca.frontiernet.net [74.40.3.49]
5 4 ms 12 ms 5 ms ae1---0.cbr03.lsan.ca.frontiernet.net [45.52.201.131]
6 4 ms 3 ms 3 ms 74.40.26.254
7 5 ms 4 ms 4 ms 142.250.236.213
8 4 ms 4 ms 4 ms 142.251.60.99
9 4 ms 4 ms 4 ms dns.google [8.8.8.8]

I then did a ping test on individual cmd windows for hops 3,4, and 5.

100 Pings for Hop 3:
C:\WINDOWS\system32>ping -n 100 172.102.105.244

Pinging 172.102.105.244 with 32 bytes of data:
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=7ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=3ms TTL=253
Reply from 172.102.105.244: bytes=32 time=7ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=7ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=7ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=7ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=3ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=3ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=7ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=3ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=7ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=7ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=7ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=7ms TTL=253
Reply from 172.102.105.244: bytes=32 time=3ms TTL=253
Reply from 172.102.105.244: bytes=32 time=7ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=3ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=3ms TTL=253
Reply from 172.102.105.244: bytes=32 time=3ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=7ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=3ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253

Ping statistics for 172.102.105.244:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 7ms, Average = 5ms

100 Pings for Hop 4:
C:\WINDOWS\system32>ping -n 100 74.40.3.49

Pinging 74.40.3.49 with 32 bytes of data:
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=5ms TTL=61
Reply from 74.40.3.49: bytes=32 time=5ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=3ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=5ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=5ms TTL=61
Reply from 74.40.3.49: bytes=32 time=5ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=5ms TTL=61
Reply from 74.40.3.49: bytes=32 time=5ms TTL=61
Reply from 74.40.3.49: bytes=32 time=5ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=5ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=5ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61

Ping statistics for 74.40.3.49:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 5ms, Average = 4ms

100 Pings for Hop 5:
C:\WINDOWS\system32>ping -n 100 45.42.201.131

Pinging 45.42.201.131 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 45.42.201.131:
Packets: Sent = 100, Received = 0, Lost = 100 (100% loss),

My questions are "Why is Hop 2 request timed out?", "What causes the asterik on hop 4 (on the tracert)?", "Does the spike on Hop 5 (from 4-12ms on tracert) correlated to ping spike in game?", and "What is causing the issue of inconsistent network latency and packet loss?"
 
I don't know as much about the Windows tools, but not all asterisk ("*") are actually an error in ping. Ping uses the ICMP protocol, whereas most of the traffic uses either UDP or TCP (or a few others). Not all network hops are programmed to respond to ICMP, which is not an error. Disabling ICMP might for example be used to prevent some form of malicious flooding. Trying to ping a node with ICMP disabled on it will show as 100% loss even if nothing is lost.

However, if you were to tracert the address of one of the game servers and find a place along the route where the time suddenly grows significantly, then you might still infer that one of the hops along that list are responsible. What becomes really important is if the hop is in your household. Typically the first hop is to the router, and the next hop is to a box just outside of your home, maybe a third hop in the nearby neighborhood. The first two hops might need a service call to fix if it is wired. On the other hand, if the time goes up a little further out, then they probably have degraded wiring picking up noise.

The problem with part of this is that if you can't provide the exact route point of the failure, then they'll likely say your home "looks good" and move on without helping much. If you can point out the address of a specific hop when this starts, then sometimes you can get help. A typical problem of such a case is that the wiring or connections are getting old, and some crack is exposed, but it only fails if (A) moisture has recently gone into the weak point, or (B) some RF noise (example, from AWACS, from which training or other purposes might exist on a schedule) happens to be exposed at the side of the cable where the failure is growing. There isn't much reason someone would climb up on a pole to randomly inspect the top side of cables (where failure points might be invisible from the ground), but such failures are common from aircraft flying over them sometimes (and nobody on the ground would see any reason why there'd be a failure).
 

kanewolf

Titan
Moderator
In the beginning of August, I have been playing video games, and recently my ping has been really inconsistent, which is typically paired with packet loss. Typically, I would average around 11-15ms of latency in game, with zero packet loss. Now, sometimes I would get 11-15ms one game, and the next game I would get 40-50ms of latency, while losing 500-1000 packets every minute.

I am trying to find out the reasoning behind the inconsistencies behind my ping and packet loss, so I did some research. I seem to have a similar problem to user ypmxx in the following thread: https://forums.tomshardware.com/threads/packet-loss.3740059/

I did everything from restarting the router, changing ethernet cable, changed ip address on Windows, etc.

I then followed instructions within the thread regarding "tracert 8.8.8.8" and pinging certain hops.

C:\WINDOWS\system32>tracert 8.8.8.8

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168..
2 * * * Request timed out.
3 4 ms 3 ms 3 ms te2-3-0-4---0.lcr01.ontr.ca.frontiernet.net [172.102.105.244]
4 * 4 ms 4 ms ae8---0.scr02.lsan.ca.frontiernet.net [74.40.3.49]
5 4 ms 12 ms 5 ms ae1---0.cbr03.lsan.ca.frontiernet.net [45.52.201.131]
6 4 ms 3 ms 3 ms 74.40.26.254
7 5 ms 4 ms 4 ms 142.250.236.213
8 4 ms 4 ms 4 ms 142.251.60.99
9 4 ms 4 ms 4 ms dns.google [8.8.8.8]

I then did a ping test on individual cmd windows for hops 3,4, and 5.

100 Pings for Hop 3:
C:\WINDOWS\system32>ping -n 100 172.102.105.244

Pinging 172.102.105.244 with 32 bytes of data:
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=7ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=3ms TTL=253
Reply from 172.102.105.244: bytes=32 time=7ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=7ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=7ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=7ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=3ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=3ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=7ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=3ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=7ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=7ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=7ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=7ms TTL=253
Reply from 172.102.105.244: bytes=32 time=3ms TTL=253
Reply from 172.102.105.244: bytes=32 time=7ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=3ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=3ms TTL=253
Reply from 172.102.105.244: bytes=32 time=3ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=7ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=4ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=3ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=6ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253
Reply from 172.102.105.244: bytes=32 time=5ms TTL=253

Ping statistics for 172.102.105.244:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 7ms, Average = 5ms

100 Pings for Hop 4:
C:\WINDOWS\system32>ping -n 100 74.40.3.49

Pinging 74.40.3.49 with 32 bytes of data:
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=5ms TTL=61
Reply from 74.40.3.49: bytes=32 time=5ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=3ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=5ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=5ms TTL=61
Reply from 74.40.3.49: bytes=32 time=5ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=5ms TTL=61
Reply from 74.40.3.49: bytes=32 time=5ms TTL=61
Reply from 74.40.3.49: bytes=32 time=5ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=5ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=5ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61
Reply from 74.40.3.49: bytes=32 time=4ms TTL=61

Ping statistics for 74.40.3.49:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 5ms, Average = 4ms

100 Pings for Hop 5:
C:\WINDOWS\system32>ping -n 100 45.42.201.131

Pinging 45.42.201.131 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 45.42.201.131:
Packets: Sent = 100, Received = 0, Lost = 100 (100% loss),

My questions are "Why is Hop 2 request timed out?", "What causes the asterik on hop 4 (on the tracert)?", "Does the spike on Hop 5 (from 4-12ms on tracert) correlated to ping spike in game?", and "What is causing the issue of inconsistent network latency and packet loss?"
There is no requirement for intermediate network nodes to respond to pings. Many ISPs disable responding to pings to limit the possibility of a DDOS using ping.
 
This is where you are digging too deep and confusing yourself.

Key is if you leave a ping run in a background cmd window to something like 8.8.8.8 or maybe the game server. Game server many times block ping to prevent denial of service attacks. Maybe a router you see in the trace before the server will work. I would start with 8.8.8.8 since that tends to be very stable. This will show any issues with your equipment or your internet connection. Testing the game server you run the risk the game server might be the problem.

So when you see no issues to the end node but you see issues to intermediate nodes it means this is not a actual problem. For example if all traffic was really being blocked by hop 2 you would have no internet at all.

What is done is some routers are configured to not respond to ping/trace. Some others will respond but they have limits on how many they will do a second to prevent denial of service attacks. In additions routers give the ping process lower priority that passing traffic so they will delay responding if they have other things to do.
 
Aug 24, 2022
6
0
10
0
This is where you are digging too deep and confusing yourself.

Key is if you leave a ping run in a background cmd window to something like 8.8.8.8 or maybe the game server. Game server many times block ping to prevent denial of service attacks. Maybe a router you see in the trace before the server will work. I would start with 8.8.8.8 since that tends to be very stable. This will show any issues with your equipment or your internet connection. Testing the game server you run the risk the game server might be the problem.

So when you see no issues to the end node but you see issues to intermediate nodes it means this is not a actual problem. For example if all traffic was really being blocked by hop 2 you would have no internet at all.

What is done is some routers are configured to not respond to ping/trace. Some others will respond but they have limits on how many they will do a second to prevent denial of service attacks. In additions routers give the ping process lower priority that passing traffic so they will delay responding if they have other things to do.
I pinged 8.8.8.8, and here are the results, which seemed pretty normal:
C:\WINDOWS\system32>ping -n 100 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=5ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=5ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=5ms TTL=117
Reply from 8.8.8.8: bytes=32 time=5ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=5ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=5ms TTL=117
Reply from 8.8.8.8: bytes=32 time=5ms TTL=117
Reply from 8.8.8.8: bytes=32 time=5ms TTL=117
Reply from 8.8.8.8: bytes=32 time=5ms TTL=117
Reply from 8.8.8.8: bytes=32 time=5ms TTL=117
Reply from 8.8.8.8: bytes=32 time=5ms TTL=117
Reply from 8.8.8.8: bytes=32 time=5ms TTL=117
Reply from 8.8.8.8: bytes=32 time=5ms TTL=117
Reply from 8.8.8.8: bytes=32 time=5ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=5ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=13ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=5ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=5ms TTL=117

Ping statistics for 8.8.8.8:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 13ms, Average = 4ms

I then tried doing a traceroute to the Valorant server:
C:\WINDOWS\system32>tracert 192.207.0.1

Tracing route to 192.207.0.1 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168..
2 * * * Request timed out.
3 3 ms 3 ms 7 ms 172.102.111.146
4 4 ms 4 ms 4 ms ae8---0.scr02.lsan.ca.frontiernet.net [74.40.3.49]
5 7 ms 7 ms 8 ms ae1---0.cbr05.lsan.ca.frontiernet.net [45.52.201.139]
6 4 ms 4 ms 4 ms riotsgamesdirect.as6507.any2ix.coresite.com [206.72.211.33]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

I then did a ping to hop 6:
C:\WINDOWS\system32>ping -n 100 206.72.211.33

Pinging 206.72.211.33 with 32 bytes of data:
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=6ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250

Ping statistics for 206.72.211.33:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 6ms, Average = 4ms

Does any of this indicate any issues?
 

Alan Alan

Great
Aug 9, 2022
102
4
95
1
I pinged 8.8.8.8, and here are the results, which seemed pretty normal:
C:\WINDOWS\system32>ping -n 100 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=5ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=5ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=5ms TTL=117
Reply from 8.8.8.8: bytes=32 time=5ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=5ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=5ms TTL=117
Reply from 8.8.8.8: bytes=32 time=5ms TTL=117
Reply from 8.8.8.8: bytes=32 time=5ms TTL=117
Reply from 8.8.8.8: bytes=32 time=5ms TTL=117
Reply from 8.8.8.8: bytes=32 time=5ms TTL=117
Reply from 8.8.8.8: bytes=32 time=5ms TTL=117
Reply from 8.8.8.8: bytes=32 time=5ms TTL=117
Reply from 8.8.8.8: bytes=32 time=5ms TTL=117
Reply from 8.8.8.8: bytes=32 time=5ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=5ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=13ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=5ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=4ms TTL=117
Reply from 8.8.8.8: bytes=32 time=5ms TTL=117

Ping statistics for 8.8.8.8:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 13ms, Average = 4ms

I then tried doing a traceroute to the Valorant server:
C:\WINDOWS\system32>tracert 192.207.0.1

Tracing route to 192.207.0.1 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168..
2 * * * Request timed out.
3 3 ms 3 ms 7 ms 172.102.111.146
4 4 ms 4 ms 4 ms ae8---0.scr02.lsan.ca.frontiernet.net [74.40.3.49]
5 7 ms 7 ms 8 ms ae1---0.cbr05.lsan.ca.frontiernet.net [45.52.201.139]
6 4 ms 4 ms 4 ms riotsgamesdirect.as6507.any2ix.coresite.com [206.72.211.33]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

I then did a ping to hop 6:
C:\WINDOWS\system32>ping -n 100 206.72.211.33

Pinging 206.72.211.33 with 32 bytes of data:
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=6ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=5ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250
Reply from 206.72.211.33: bytes=32 time=4ms TTL=250

Ping statistics for 206.72.211.33:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 6ms, Average = 4ms

Does any of this indicate any issues?
You should only ping your local dns server. Anything beyond that point is internet traffic. Call your isp and have the send a hit to your modem.
 
It all looks good and that is the problem with intermittent network errors.

The game company is blocking ping with a firewall so you can't really test to the server. Not unexpected all the little script kiddies would ping the server until it dies on games like valorant.

So what I would try next is to run the constant ping to 8.8.8.8 in a background window while you play the game. When the game has issues quickly switch over and see if the ping also has issues. You might also want a second command window with a ping to hop3 (better hop 2 but your ISP has prevented it).
If you see issues espeically to hop 3 it likely means there is some problem with your internet connection. If you call the ISP and tell them there are issues to 8.8.8.8 they will blame google, ya sure. They might try that even with hop3 but I suspect because the latency is so low this is also a router owned by your ISP.

Now if continue to see no issues with the ping command you start to suspect the game is telling lies. It could be a network issue but it will likely be in the game company ISP or servers. The first few hops are the same so the test to 8.8.8.8 would also show issues.

Games are known to lie about this. One example would be is if a game take a long time in a video processing function and after it is done it check the response to its ping it will blame the extra time on the network when the data was sitting there waiting to be read.
What is strange is people report fixing so called network issues by adjusting video parms. Doesn't make since the video never travels over the network so it is more likely some strangeness on how the game measure these delays.
 
Reactions: Alan Alan
Aug 24, 2022
6
0
10
0
It all looks good and that is the problem with intermittent network errors.

The game company is blocking ping with a firewall so you can't really test to the server. Not unexpected all the little script kiddies would ping the server until it dies on games like valorant.

So what I would try next is to run the constant ping to 8.8.8.8 in a background window while you play the game. When the game has issues quickly switch over and see if the ping also has issues. You might also want a second command window with a ping to hop3 (better hop 2 but your ISP has prevented it).
If you see issues espeically to hop 3 it likely means there is some problem with your internet connection. If you call the ISP and tell them there are issues to 8.8.8.8 they will blame google, ya sure. They might try that even with hop3 but I suspect because the latency is so low this is also a router owned by your ISP.

Now if continue to see no issues with the ping command you start to suspect the game is telling lies. It could be a network issue but it will likely be in the game company ISP or servers. The first few hops are the same so the test to 8.8.8.8 would also show issues.

Games are known to lie about this. One example would be is if a game take a long time in a video processing function and after it is done it check the response to its ping it will blame the extra time on the network when the data was sitting there waiting to be read.
What is strange is people report fixing so called network issues by adjusting video parms. Doesn't make since the video never travels over the network so it is more likely some strangeness on how the game measure these delays.
While I was playing, I tested pinging 8.8.8.8 and hop 3, like you said, but I even tested pinging hop 5. Pinging 8.8.8.8 and hop 3 was normal, but ping spikes were noticable on hop 5. I was lagging in game while this was happening. In game, I was averaging 40-50 ping, while losing 500 packets per minute. For hop 5, the pings would be 4-5ms for around 10 pings, then it would randomly go to 15, and then another 10 packets of 4-5ms, then it would go to 40-50ms or even 70-80+ for one ping. This would happen every 10 pings. Does this show any signficance on why I am receiving high ping and packet loss? What could I do to fix it?

Here's an example of what I mean:
Reply from 45.52.201.131: bytes=32 time=4ms TTL=60
Reply from 45.52.201.131: bytes=32 time=4ms TTL=60
Reply from 45.52.201.131: bytes=32 time=8ms TTL=60
Reply from 45.52.201.131: bytes=32 time=5ms TTL=60
Reply from 45.52.201.131: bytes=32 time=7ms TTL=60
Reply from 45.52.201.131: bytes=32 time=6ms TTL=60
Reply from 45.52.201.131: bytes=32 time=11ms TTL=60
Reply from 45.52.201.131: bytes=32 time=15ms TTL=60
Reply from 45.52.201.131: bytes=32 time=60ms TTL=60
Reply from 45.52.201.131: bytes=32 time=10ms TTL=60
Reply from 45.52.201.131: bytes=32 time=9ms TTL=60
Reply from 45.52.201.131: bytes=32 time=7ms TTL=60
Reply from 45.52.201.131: bytes=32 time=6ms TTL=60
Reply from 45.52.201.131: bytes=32 time=14ms TTL=60
Reply from 45.52.201.131: bytes=32 time=4ms TTL=60
Reply from 45.52.201.131: bytes=32 time=4ms TTL=60
Reply from 45.52.201.131: bytes=32 time=8ms TTL=60
Reply from 45.52.201.131: bytes=32 time=8ms TTL=6
 
Not very likely since you do not see the packet loss and a few spikes here and there to 60ms is not going to cause much issue.

Your problem is lets say this really is the problem, you are never going to get the ISP to fix that. First you would have to get to some higher level tech that has access to their core routers and then you have to get them to admit they have a bottleneck in their network. If they have maxed out a fiber connection say to riot they are not going to upgrade it for a user who pays maybe $100/month.

If you did not also see the same ping spikes to the 8.8.8.8 IP then again this is likely the router was busy doing something else and delayed responding to your ping command. Things like google dns servers like 8.8.8.8 are extremely powerful clusters of machines and they do not seem to delay ping commands. Note 8.8.8.8 is not in 1 location they have duplicated it in a huge number of cites which is why pretty much everyone sees under 10-20ms of latency. You being on fiber it is even less.
 
So this is looking like it is the machine. Some common things that cause this issue. Maybe the game is using IPV6 for part of its communication. Try turning off IPv6 in the nic
Not sure what motherboard you use but many come bundled with some crap "gamer" network accelerator. Asus tends to be the worst offender. Not sure what they call it used to be something like gamerfirst. You also see a program called CFOSspeed bundled with other motherboards and even some video cards. You want to uninstall any software like that.

I am not sure how you know what the game numbers really mean. If you were getting that much packet loss it would affect things like speedtest. There are other sites that measure jitter and packet loss but I am not so sure how much you trust them.
 
Aug 24, 2022
6
0
10
0
So this is looking like it is the machine. Some common things that cause this issue. Maybe the game is using IPV6 for part of its communication. Try turning off IPv6 in the nic
Not sure what motherboard you use but many come bundled with some crap "gamer" network accelerator. Asus tends to be the worst offender. Not sure what they call it used to be something like gamerfirst. You also see a program called CFOSspeed bundled with other motherboards and even some video cards. You want to uninstall any software like that.

I am not sure how you know what the game numbers really mean. If you were getting that much packet loss it would affect things like speedtest. There are other sites that measure jitter and packet loss but I am not so sure how much you trust them.
I tested packet loss test on sites like https://devicetests.com/packet-loss-test and it would occasionally show packet loss as well. When I do a speed test, like the one on Google, sometimes the ping would be 3ms, and then the next test would be 30ms. I know 30ms may seem fine, but I am so used to seeing <3ms. Other games I play show higher pings than usual with packet loss.

When I went to the network adapter settings for ethernet, it says that IPv6 Connectivity has no network access. I turned off IPv6 under properties, like you said, and will see if the problem will keep happening.

I have an Asus motherboard, but have never heard of CFOSspeed or any program of some sort.
 
Not all asus motherboards come with it and if you are careful about what bloatware you install you might not have installed it. It most times is called gamefirst on the later asus boards.

Here is your problem. If you do not see loss/delay to hop 1 (your router) or hop2..hop3 in your case, it means everything is out of your control. Hop1 issues would be inside your house so you can fix it. Hop2 issues would the be the connection between your house and the ISP which since you directly pay for that the ISP would be somewhat helpful. When you look at hops past there this is not something you have any control over. The level 1 tech you talk to has only been trained to fix stuff in your house and stuff connecting to your house. Even if they are able to understand what you tell them about trace/ping/lag (many don't) they have no access to the equipment. When I had similar happen the only reason I got anywhere is someone I used to work with now worked at the ISP and knew my qualifications and got me a senior contact. They had a bad fiber port in a router.

Not sure what to recommend as the next step.

You might want to try running a download limited to 50% of your bandwidth while you test the ping to various hops, maybe it is load related.
Lets first say you can find some address you consistently can show loss/delay to with a ping command and not a game. You could then boot a linux USB image. This would test that it was some software or something in the windows install causing it. The problem with using a game to test is most will not run under linux and they tend to run very differently when it comes to support of some advanced video stuff. It is also messy to get a game installed on a USB stick so it does not damage your windows install.

You can try the option people who are desperate try and that is to use a service like exitlag. It is a vpn provider that has a private path to some large game data centers. Problem is you have to be able to get to their network without seeing your problem and it cost money.
 
Aug 24, 2022
6
0
10
0
Not all asus motherboards come with it and if you are careful about what bloatware you install you might not have installed it. It most times is called gamefirst on the later asus boards.

Here is your problem. If you do not see loss/delay to hop 1 (your router) or hop2..hop3 in your case, it means everything is out of your control. Hop1 issues would be inside your house so you can fix it. Hop2 issues would the be the connection between your house and the ISP which since you directly pay for that the ISP would be somewhat helpful. When you look at hops past there this is not something you have any control over. The level 1 tech you talk to has only been trained to fix stuff in your house and stuff connecting to your house. Even if they are able to understand what you tell them about trace/ping/lag (many don't) they have no access to the equipment. When I had similar happen the only reason I got anywhere is someone I used to work with now worked at the ISP and knew my qualifications and got me a senior contact. They had a bad fiber port in a router.

Not sure what to recommend as the next step.

You might want to try running a download limited to 50% of your bandwidth while you test the ping to various hops, maybe it is load related.
Lets first say you can find some address you consistently can show loss/delay to with a ping command and not a game. You could then boot a linux USB image. This would test that it was some software or something in the windows install causing it. The problem with using a game to test is most will not run under linux and they tend to run very differently when it comes to support of some advanced video stuff. It is also messy to get a game installed on a USB stick so it does not damage your windows install.

You can try the option people who are desperate try and that is to use a service like exitlag. It is a vpn provider that has a private path to some large game data centers. Problem is you have to be able to get to their network without seeing your problem and it cost money.
I was getting high ping and packet loss in a game, and I disabled my ethernet adapter, which automatically put me onto my wifi card, and I went back to normal ping and no packet loss. Does this explain anything? Does this mean something is wrong with my ethernet adapter?
 
That is very strange. Normally you see more loss on wifi.
I would also thing the wifi added slightly more latency than the 3ms you are seeing.

But this just adds to the strangeness of this. Your ping test to your router IP shows no loss at all and good latency. This means that the actual ethernet connection is good. You would see packet loss on the ethernet if it was bad.

So if this is not just some coincidence there must be some software that is delaying the traffic on your machine based on the interface it is using. It is not something simple like the drivers or the actual OS. This is more like some QoS program that is attempting to limit some kind of traffic.
You have already checked that you do not have any of the very common things like cfosspeed or gamefirst stuff.
 
Aug 24, 2022
6
0
10
0
That is very strange. Normally you see more loss on wifi.
I would also thing the wifi added slightly more latency than the 3ms you are seeing.

But this just adds to the strangeness of this. Your ping test to your router IP shows no loss at all and good latency. This means that the actual ethernet connection is good. You would see packet loss on the ethernet if it was bad.

So if this is not just some coincidence there must be some software that is delaying the traffic on your machine based on the interface it is using. It is not something simple like the drivers or the actual OS. This is more like some QoS program that is attempting to limit some kind of traffic.
You have already checked that you do not have any of the very common things like cfosspeed or gamefirst stuff.
How could I identify the QoS program on my machine? What is a QoS program? I also know I don’t have cfosspeed or gamefirst.
 
Not sure it is just a guess. What you would need to look for is some kind of software that would delay/drop only certain types of traffic but allow ping and trace to be unaffected. Most things like say a firewall rule block all types of traffic to a IP and tends to be on/off not say 10% is blocked.

Many times issue like this you can blame on the game itself. Games are more impacted by the video system than other things. What is strange is you would think any issues with the game would not care about which interface is being used.

The normal trick to rule out any hardware is to boot a linux USB image but since you only see the problems during games it does not help because most games do run under linux and it is a pain to install it on the USB stick to not damage your windows install.

The large problem is you can currently only detect this issue when you play games. None of the other more common networking test tools is detecting it. It would be nice if the game told you why it thinks there is data loss or delay. Many times you can snoop on say web traffic using something like wireshark. Even with encrypted traffic you can still see data loss and delays. You might not know what the traffic is but you can tell if it is transferring cleanly. Most games use UDP which has all the things like data reception acknowledgments built into the application and the traffic tends to be encrypted to keep the game hackers out. It would be nice if games used TCP so you could monitor the communication but UDP tends to be better for games because they don't really care much if data is lost they will not resend it unlike things that use TCP.

So I guess the 2 big question are why does it matter what interface is being used and why can you not detect the problem with other tools or application other than games.
 
Jul 10, 2022
9
0
10
0
In this case, you most likely need to solve the problem through your provider. There are also possible problems on the game server itself, which we cannot rule out. I checked the path of the data packets with a special tool host-tracker.com/en/ic/check-trace that I use often. At first glance, everything is ok, but the ping may fluctuate depending on the geographical location. Therefore, it should be taken into account.
 
Last edited:

ASK THE COMMUNITY

TRENDING THREADS