Question Valorant packet loss issue: ISP not able to figure out what's causing it ?

[pankajpatidar]

Hello Everyone, I have packet loss problem in the Valorant Game. My Ping is about 26ms to 50ms. I have fiber optic connection and 200mbps connection. My internet is running very well when i am surfing or watching yt or like that i dont feel any issue. Additionally, in the game i don't have any ping issue. I have Packet Loss issue. I have logs which i am attaching Valorant Logs and System Logs.

If anyone can read this and can help why this is happening so i can let my ISP know about it and he will do that fix. ISP knew only a few things which help him to run his business and normal consumer requests. He is not a pro who can solve this type of problem. I am from small town so its not easy for me. So i came here for help thank you.

Things my ISP tried:

1. Changed the router
2. Fiber wire connection checked of bubble or like that.
3. Changed to multiple connections owned by him (GTPL, ONE BOARDBAND, RADINET). But all have same problem.
4. DNS cloudflare and google.

He did all this but nothing workout.
I feel like he has problem in his configuration and he is not that expert to solve it.

 

[Ralston18]

You may be able to learn more about what is happening by running the following commands, without quotes, via the Command Prompt (as admin) on your computer.

Start with "ipconfig /all".

Then run:

"ping 8.8.8.8"

"tracert 8.8.8.8"

"pathping 8.8.8.8"

Targeting Google at 8.8.8.8

Copy and paste the results here.

Very likely that the packets being lost are outside of your ISP's network. And thus unfixable by your ISP.

TBD.

 

[pankajpatidar]

"ipconfig /all" 

Windows IP Configuration

   Host Name . . . . . . . . . . . . : pankajpatidar
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) Ethernet Controller (3) I225-V
   Physical Address. . . . . . . . . : FC-34-97-A1-52-16
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.1.11(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Tuesday, April 2, 2024 5:56:43 PM
   Lease Expires . . . . . . . . . . : Wednesday, April 3, 2024 5:56:43 PM
   Autoconfiguration IPv4 Address. . : 169.254.205.178(Tentative)
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . : 192.168.1.1
   DHCP Server . . . . . . . . . . . : 192.168.1.1
   DNS Servers . . . . . . . . . . . : 8.8.8.8
                                          8.8.4.4
   NetBIOS over Tcpip. . . . . . . . : Enabled

"ping 8.8.8.8"
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=15ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=15ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116

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

"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.1.1
  2    10 ms    10 ms    10 ms  10.235.0.1
  3     9 ms     9 ms     9 ms  169.254.0.6
  4     8 ms     8 ms     8 ms  150.107.189.189
  5    10 ms    10 ms    10 ms  150.107.189.185
  6    14 ms    17 ms    14 ms  43.224.1.13
  7    16 ms    16 ms    16 ms  72.14.198.180
  8    15 ms    16 ms    16 ms  142.251.66.169
  9    15 ms    15 ms    15 ms  142.251.52.229
 10    15 ms    14 ms    14 ms  dns.google [8.8.8.8]

Trace complete.

"pathping 8.8.8.8"

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:
  0  pankajpatidar [192.168.1.11]
  1  192.168.1.1
  2  10.235.0.1
  3  169.254.0.6
  4  150.107.189.189
  5  150.107.189.185
  6  43.224.1.13
  7  72.14.198.180
  8  142.251.66.169
  9  142.251.52.229
 10  dns.google [8.8.8.8]

Computing statistics for 250 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           pankajpatidar [192.168.1.11]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.1
                                0/ 100 =  0%   |
  2   10ms     0/ 100 =  0%     0/ 100 =  0%  10.235.0.1
                                0/ 100 =  0%   |
  3  ---     100/ 100 =100%   100/ 100 =100%  169.254.0.6
                                0/ 100 =  0%   |
  4    8ms     0/ 100 =  0%     0/ 100 =  0%  150.107.189.189
                                0/ 100 =  0%   |
  5   10ms     0/ 100 =  0%     0/ 100 =  0%  150.107.189.185
                                0/ 100 =  0%   |
  6   14ms     1/ 100 =  1%     1/ 100 =  1%  43.224.1.13
                                0/ 100 =  0%   |
  7   16ms     0/ 100 =  0%     0/ 100 =  0%  72.14.198.180
                                0/ 100 =  0%   |
  8   15ms     0/ 100 =  0%     0/ 100 =  0%  142.251.66.169
                                0/ 100 =  0%   |
  9  ---     100/ 100 =100%   100/ 100 =100%  142.251.52.229
                                0/ 100 =  0%   |
 10   14ms     0/ 100 =  0%     0/ 100 =  0%  dns.google [8.8.8.8]

Trace complete.

 

[bill001g]

The subnet mask is strange on you lan IP but that is not your issue, a valid configuration just not commonly seen on home users.

All your testing shows nothing so the problem is all in your imagination

Your problem is likely intermittent and everything was working when you tested. Tools like path ping take a minute or so to complete but even that tool showed nothing that is not normal testing error.

What I would now try at first is open a command windows and use ping 8.8.8.8 -t. This will run constantly. Now leave this run in the background and play your game. When you see some issue in the game quickly switch over and check this windows for loss.

If this shows loss then you can do more testing to other nodes in the path. Hop 1 and hop 2 in the tracert in particular.

Problem is if it shows nothing then it gets much more complex. What this would means is there is no networking issue and it is something else that the game things is packet loss or it is a network issue but only on the part of the network going to the game company serer.

You could test things like ping and trace to the game company server but it tends to not help actually fix the issue if the network is good to google (8.8.8.8). Realistically the only things you can really get fixed network wise is the wire going to your house and issues with your router. So you kinda want to see loss in the ping going to 8.8.8.8 when your game is complaining.

 

[pankajpatidar]

ping 8.8.8.8 -t

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=15ms TTL=116
Reply from 8.8.8.8: bytes=32 time=15ms TTL=116
Reply from 8.8.8.8: bytes=32 time=15ms TTL=116
Reply from 8.8.8.8: bytes=32 time=15ms TTL=116
Reply from 8.8.8.8: bytes=32 time=15ms TTL=116
Reply from 8.8.8.8: bytes=32 time=15ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=15ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=15ms TTL=116
Reply from 8.8.8.8: bytes=32 time=15ms TTL=116
Reply from 8.8.8.8: bytes=32 time=15ms TTL=116
Reply from 8.8.8.8: bytes=32 time=15ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=15ms TTL=116
Reply from 8.8.8.8: bytes=32 time=15ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=15ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=15ms TTL=116
Reply from 8.8.8.8: bytes=32 time=15ms TTL=116
Reply from 8.8.8.8: bytes=32 time=15ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=15ms TTL=116
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=15ms TTL=116
Request timed out.
Reply from 8.8.8.8: bytes=32 time=15ms TTL=116
Reply from 8.8.8.8: bytes=32 time=15ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=15ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=15ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=15ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=15ms TTL=116
Reply from 8.8.8.8: bytes=32 time=15ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=15ms TTL=116

 

[lantis3]

In most cases there is nothing you can do.

The only option is to use VPN to change your route to the game server and see if it can solve the issue.

It will be a try and error process though. No one can tell you which VPN will work. You can only try yourself one by one.

 

[bill001g]

So now constant ping to 10.135.0.1

This should be your ISP first router. Loss here generally means there is some issue with the connection coming to your house.

You could also try 150.107.189.189 This is farther into the ISP network but sometime the first router will not respond.

If this is good then it get messy because it could be in another ISP.