[SOLVED] Ping substantially higher than it used to be.

Sep 9, 2021
3
0
10
Hello! This is my first post on here so forgive me if I'm not up to par with some of the formatting preferences.
About a week or two weeks ago my ping to everything seemed to jump up substantially. My download speed is fine and has not changed but my ping to even some of the closest servers to me is around 100, where generally it would be in the 20-30 range. Even all the servers that I can see to connect to the ping has risen about 40-60 for each server. It is still somewhat playable and the ping is constant but I'm trying to figure out what may have caused it to just jump like that.
Specs: Router: Netgear Nighthawk (R) X4S R7800
Modem: Netgear LB1120
MoBo: MSI X390 Gaming Plus
Power supply: Corsair RM650X
OS; Windows 10 v 21H1
ISP: BlazingHog, connected via ethernet
95% percent of the time my desktop is the only thing connected to the router.
I have tried:
Uninstalling/reinstalling network drivers on my PC.
Checking all connections to insure everything is in properly.
Reset modem/router.
Fac reset modem
Checking to see if I have the same ping issues when I connect wireless via my phone- I do.
Thanks in advance to anyone who reads and tries to help!
 
Solution
Run tracert to 8.8.8.8 or some other common IP.

What you want to see is the hop you get the very large jump.

In most cases hop 1 is your router and hop 2 is the ISP.

You can only really fix things i these 2 hops. If they are farther into the network it is likely out of your control. Could be a cut fiber between 2 ISP and you data is not on a alternate path. If it is in hop 1 which is very unlikely then it is either your computer or your router. If it is in hop 2 then I would call the ISP and have them check your line but most ISP do not care about ping time they only partially promise download rates.
Run tracert to 8.8.8.8 or some other common IP.

What you want to see is the hop you get the very large jump.

In most cases hop 1 is your router and hop 2 is the ISP.

You can only really fix things i these 2 hops. If they are farther into the network it is likely out of your control. Could be a cut fiber between 2 ISP and you data is not on a alternate path. If it is in hop 1 which is very unlikely then it is either your computer or your router. If it is in hop 2 then I would call the ISP and have them check your line but most ISP do not care about ping time they only partially promise download rates.
 
Solution
Run tracert to 8.8.8.8 or some other common IP.

What you want to see is the hop you get the very large jump.

In most cases hop 1 is your router and hop 2 is the ISP.

You can only really fix things i these 2 hops. If they are farther into the network it is likely out of your control. Could be a cut fiber between 2 ISP and you data is not on a alternate path. If it is in hop 1 which is very unlikely then it is either your computer or your router. If it is in hop 2 then I would call the ISP and have them check your line but most ISP do not care about ping time they only partially promise download rates.

alright then, which of the pings shown in each hop is relevant to me? Or are all of three pings in each hop relevant?
 
I forget but I think it is just the results of 3 packets. In general you want them to be about the same on each line but because of how the testing is done you can get random variations that you can ignore. You want to run the tracert command multiple times to try to see if stuff like this reoccurs.

What is most important is between what hops this occurs. You are looking for large changes.

In your case it is going to be harder because you do not have a trace from before to compare. A 100ms can be very normal latency to a server in another country.

It is even more difficult if the ping/tracert time to a ip like 8.8.8.8 does not show the high latency. If for example you get good times to 8.8.8.8 but high ping time to game company servers it means there is some issue between your ISP and the game company ISP.
 
I forget but I think it is just the results of 3 packets. In general you want them to be about the same on each line but because of how the testing is done you can get random variations that you can ignore. You want to run the tracert command multiple times to try to see if stuff like this reoccurs.

What is most important is between what hops this occurs. You are looking for large changes.

In your case it is going to be harder because you do not have a trace from before to compare. A 100ms can be very normal latency to a server in another country.

It is even more difficult if the ping/tracert time to a ip like 8.8.8.8 does not show the high latency. If for example you get good times to 8.8.8.8 but high ping time to game company servers it means there is some issue between your ISP and the game company ISP.
Roughly 50% percent of the times I try no matter what I try to ping, the first packet of the first hop is between 70-80, which seems crazy high if thats just meant to be from my pc to my router, the other half of the time its all 1-2ms and the 80-90 doesn't start until the 3rd hop, which in that case I believe you've said there is nothing that I can do about it. And this does affect my ping to all servers, be it discord, games or just ping servers on speedtest.net all have unusually high ms.
 
Sometimes you get a slight delay on the very first ping packet there might be some kind of overhead but it is testing error

I would use a actual ping command and run a constant ping to some of the hops you see in the trace. This should give you more consistent results.

Figuring out what is going on past the first 2 hops is rather hard because it is inside the ISP network and they don't tell much. Sometimes you can get a idea where the router is by the name. it is very common for ISP to use things like airport codes or other methods to include the city name in the router name.

I would call your ISP and see if they can explain why the 3rd hop goes to 80ms. Note if the 4th hop and past are less than the 3rd hop this is a testing issue and not a actual problem. Routers are designed to use their CPU first to pass traffic and if they have extra time they will respond to ping and tracert