[SOLVED] Ping Jumps very High

[Noah111]

My ping constantly spikes and I dont know why I have an ethernet connection I have disabled windows update I have checked drivers. I did a tracert to 8.8.8.8 and got


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

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.4]
2 <1 ms <1 ms <1 ms 192.168.155.1
3 * * * Request timed out.
4 5 ms 5 ms 4 ms 104.219.134.1
5 400 ms 242 ms 36 ms 10.30.0.254
6 214 ms 68 ms 25 ms 209.89.138.118
7 * * * Request timed out.
8 35 ms 32 ms 34 ms 74.125.50.110
9 32 ms 34 ms 35 ms 108.170.245.97
10 31 ms 30 ms 36 ms 108.170.233.123
11 37 ms 34 ms 35 ms dns.google [8.8.8.8]

Trace complete.





Where Do I go from here?

 

[bill001g]

You have to do more testing.

The tracert show no problems. Lets take a better example. Hop 3 in your trace is dropping all traffic. If this was actually true then all traffic to hop 4 -11 would also be dropped and you would not see any response. So the large ping spikes in hop 5 and hop 6 mean nothing because they do not actually increase the ping time to the end node. Routers in the path are designed to not respond to ping/trace (ie hop3) or they may delay the response if they are busying doing important work like passing actual user data.

You can try a tool like pathping but you also have to be very careful about how you interpret the results.

Most cases it is simpler in some ways to do this yourself. Open a bunch of cmd windows and leave constant ping run to a number of the hops. When you have a real problem you will see issues in all the hops at the same time.

This is all a very interesting exercise that may or may not get your problem actually fixed. Lets say the problem is in googles network and not your ISP network what can you or your ISP do to fix that. Pretty much you need to hope the problem is in the first couple of hops. I am going to bet because you latency is so low in hop 1 and hop 2 you have 2 routers in your house even though you may think one of them is only a modem.

 

[failboat]

When some of your hops have high latency inconsistently you buffered packets somewhere between you and that hop. There is no way to know where it buffered. ISP monitor their own lines for congestion and keep them clear. They might have oversold and are ignoring it though and you can't easily prove this either. To check for congestion on your side you need to monitor bandwidth usage. Check your router for a graph. Most consumer routers don't have a lot in there. It can come from either up or down being swamped.

If you call the ISP and have them come out they are going to test throughput from one pc on the modem. You should test like this, with a firewall on, before doing that or they might bill you. Congestion that you caused from swamping your link is normal. If something below the modem is not working right then it's also your issue.

 

[SgtScream]

That trace route is to one dns server. That means nothing.

 

[failboat]

How long does your increased latency last? Whats your up/down? How many people use the internet?

A large download or upload will give you max latency until it's complete.
TCP streams like youtube or netflix start and stop. so every 15sec or so a TCP starts and it might buffer briefly. It really depends on how much of your connection it's using.
google home or alexa do bursts of data when you talk to them.
if any program is routinely sending data somewhere and you don't know what service it's for it's probably not good.

 

[nigelivey]

That trace route is to one dns server. That means nothing.

Please elaborate

 

[SgtScream]

Please elaborate

Please elaborate

Please elaborate

There are many DNS servers, including your ISP. You can't possibly expect ping to be low on every hop which is out of everyone's control. Read your ISP's service level agreement. Are you statically assigned to use google's 8 .8 .8.8 server? If not why do you care what the trace route is?

 

[failboat]

There are many DNS servers, including your ISP. You can't possibly expect ping to be low on every hop which is out of everyone's control. Read your ISP's service level agreement. Are you statically assigned to use google's 8 .8 .8.8 server? If not why do you care what the trace route is?

You can and should expect it. Online gaming wouldn't exist if ISP pipes weren't clear.

 

[SgtScream]

You can and should expect it. Online gaming wouldn't exist if ISP pipes weren't clear.

Well then you have false expectations unless you have your own dedicated fiber circuit. I'm not disputing the end user is having a problem, but the internet works nothing like plumbing and there are no clogged or unclogged pipes, affecting his quality of network connectivity.

 

[failboat]

Well then you have false expectations unless you have your own dedicated fiber circuit. I'm not disputing the end user is having a problem, but the internet works nothing like plumbing and there are no clogged or unclogged pipes, affecting his quality of network connectivity.

Well then you have false expectations unless you have your own dedicated fiber circuit. I'm not disputing the end user is having a problem, but the internet works nothing like plumbing and there are no clogged or unclogged pipes, affecting his quality of network connectivity.

There is 100% a clog in his traceroute. I don't think #5 picked it's server up and moved 10,000 miles between ping 1 and 3.

 

[SgtScream]

There is 100% a clog in his traceroute. I don't think #5 picked it's server up and moved 10,000 miles between ping 1 and 3.

Again...that trace route is irrelevant. What plumbing service should he call to unclog his trace route?

 

[nigelivey]

There are many DNS servers, including your ISP. You can't possibly expect ping to be low on every hop which is out of everyone's control. Read your ISP's service level agreement. Are you statically assigned to use google's 8 .8 .8.8 server? If not why do you care what the trace route is?

Because Googles DNS servers on 8.8.8.8 and 8.8.4.4 are geo localised they are used as a standard ping addresses for testing, the OP was clearly only using this address for testing a route through their ISP.