High ping (more info found)

kraftiumyt

Prominent
Jun 21, 2018
11
0
510
- Generally happens from noon-8 pm, but can change

- Sometimes, ping is fine for 10 mins or so during the lag times and then starts lagging again

- In CMD, when i ping my gateway, i get perfect ping, while when i ping any dns or IP, (usually on the second reply) it is 400 ms. I tried 1.1.1.1 and this is true, when it lagged, I had 400 ms on the second reply, but when didnt lag, it was about 15 on all replies

-Happens on every game

-When it is lagging, i get about 1 mbps, when it isn't i get 5-7

-Not a problem with too many people on wifi, when there are no others on wifi, it can still happen

-In a Discord voice chat by myself, when it lags, it is about 400 ms, but sometimes for some reason it drops to 20 ms for maybe 2 seconds then goes straight back up. Sometimes when it goes straight back up it goes down again, then back up, but sometimes it it stable at 400 ms. Sometimes, it consistently stays at 400 ms for 10 seconds, drops to 20 ms for about 5 seconds, then repeats itself. https://ibb.co/hf1qro link for this pattern.
 
Solution
Sounds like a coax cable. It looks like the ISP has some major issue in their network. Hopefully they will do something about this.

Be very sure when you talk to them you do not show them only tracert. Make sure you have a capture of 2 windows 1 with a ping to your router and a another to the IP on the second hop in the trace.

This should prove to them that it is fine to your router but not to their system. This way they can not blame your pc or router (its good to hop 1) and not try to claim it is the server you are pinging (it is THEIR router)
Generally when it is time of day based it is because your ISP has sold internet to more customers than their network can handle. They will never admit that because they don't want to spend the money to upgrade.

You need to run tracert to some IP address. Then you want to ping the various hops in the trace to see if you can find the one that is causing the large delay. The second hop is generally the connection between your house and the ISP. This one is the easiest to get a ISP to fix. If this is a DSL connection that part of the line is dedicated to you so it should not have issues. Cable type systems the connection between the house and the ISP is shared with your neighbors.

If the second hop is fine and the problem is farther into the network you can see what you ISP says. Some times it is between ISP which is even harder to get corrected.
 

kraftiumyt

Prominent
Jun 21, 2018
11
0
510


This is what I got when using tracert.
So yes, it starts at the second hop and lags after, which i assume is due to the second hop?
1 2 ms 3 ms 3 ms
2 245 ms 358 ms 378 ms
3 418 ms 438 ms 404 ms
4 362 ms 370 ms 369 ms
5 372 ms 408 ms 423 ms
6 390 ms 359 ms 367 ms
7 391 ms 381 ms 412 ms
8 413 ms 425 ms 439 ms
9 306 ms 357 ms 382 ms
10 421 ms 434 ms 385 ms
11 350 ms 354 ms 347 ms
12 396 ms 395 ms 398 ms
 
If you have dsl call the ISP and see if they can fix this. Problems with the line can cause this.

If it is a cable type of connection this is harder because it can be a neighbor causing the problem. Most newer cable systems have so much bandwidth this is not a issue but older system still suffer from over sold links.

In either case you want to show the ISP the tracert or ping your hop 1 ip and the hop 2 ip. This should also show them the problem is in the connection between your house and the ISP.

I will assume you do not have vpn on your router because that also can cause this.
 

kraftiumyt

Prominent
Jun 21, 2018
11
0
510


I use Xfinity and I use one of the newer systems, and it has a thick cable type cord with the bolt (or whatever it is called), so i think I have a cable type connection.
 
Sounds like a coax cable. It looks like the ISP has some major issue in their network. Hopefully they will do something about this.

Be very sure when you talk to them you do not show them only tracert. Make sure you have a capture of 2 windows 1 with a ping to your router and a another to the IP on the second hop in the trace.

This should prove to them that it is fine to your router but not to their system. This way they can not blame your pc or router (its good to hop 1) and not try to claim it is the server you are pinging (it is THEIR router)
 
Solution