• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

Very annoying HIGH Ping/Latency spikes, All games and devices

Status
Not open for further replies.
Joined
May 3, 2014
Messages
35 (0.01/day)
Hello everyone. Thank you for taking a look at my problem here first off, Im really at the end of my line here. I know very little of advanced computer knowledge, ( I know enough not to break things) And Ive been having this issue for more than a week now.

Basically, Ive run Diablo 3, Elder scrolls Online, and another first person shooter, obviously, same results. I'll play, then all of a sudden, BOOM, High spikes. From 100ms, to 1000? 500? It doesnt matter, point is, I lagg and rubberband everywhere, or just delays. Annoying.

Im going to call my ISP and have them send someone out, but Id still like your opinions and help to maybe pin point this damn cancer I have.

So, just tell me what to do, and I'll try and provide you guys with information to help pin point this.
 
is someone uploading on your network?
 
No one is on my network no. I am using Wifi as well, not connected with a wire. Though Ive seen high ping on my phone (Tested a ping test on my android) I really cannot think what this problem could be, Ive even tested another router, same issue.
 
No one is on my network no. I am using Wifi as well, not connected with a wire. Though Ive seen high ping on my phone (Tested a ping test on my android) I really cannot think what this problem could be, Ive even tested another router, same issue.


you're sure about nothing uploading? no smartphones syncing data/pics? no one using facebook?

wifi could be the cause alone if theres intereference, so try wired, and if thats the issue change wifi channels.
 
Postive, its late, so no one is using it but me. Also, my parents dont use the net at all barely ever, and I even disabled my wifi off phone to see if that would help, still the same. Also, the router and modem are downstairs, while this big pc is upstairs, I could try tomorrow to plug it downstairs and test to see if wired would do anything, (If wired is fine, what does this mean?)
 
Also, any other information I could give to you that would help?


theres hundreds of possible causes, so its waiting to see what you figure out, really. most common causes for ping spikes are a choked upload (user side), or packet loss (faulty hardware, could be your side or ISP)
 
So I should definitely get a tech from my comcast ISP and have them take a look at things then?
 
Any tests I should run and save to show them when they get here? (It happens in games but is there a certain IP I can ping test to show results instead of just logging into a game to show him/her?)
 
Any tests I should run and save to show them when they get here? (It happens in games but is there a certain IP I can ping test to show results instead of just logging into a game to show him/her?)

from a command prompt you can run

ping google.com -t

and it will loop the ping test over and over until you close it.
 
from a command prompt you can run

ping google.com -t

and it will loop the ping test over and over until you close it.
Also when it does start to ping high, using this will tell you where the slowdown is.
Code:
tracert google.com
Being Comcast that means the OP has cable. So if the OP has a Motorola cable modem, going to http://192.168.100.1 should bring the user to the status page for your modem which may have errors or can tell you if your signal is out of whack.
 
Also, please ensure you have your router communicating on a non congested wireless channel. You can go to the Google Play store and search for the Amped Wireless Wifi Analytics tool>download it>it will tell you the least congested channels to use as well as other tools.

You may also download the program called InSSIDer if you have a windows based laptop and it will also scan networks and provide the congestion data as well.

From there you would go to the following Router Control Panel area:
More Settings>2.4Ghz Settings>Basic Settings>Select the channel that is the least congested>Apply
Do the same for the 5Ghz band as well.
 
Also, please ensure you have your router communicating on a non congested wireless channel. You can go to the Google Play store and search for the Amped Wireless Wifi Analytics tool>download it>it will tell you the least congested channels to use as well as other tools.

You may also download the program called InSSIDer if you have a windows based laptop and it will also scan networks and provide the congestion data as well.

From there you would go to the following Router Control Panel area:
More Settings>2.4Ghz Settings>Basic Settings>Select the channel that is the least congested>Apply
Do the same for the 5Ghz band as well.
Additionally, on 5Ghz if there is no congestion at all, higher channels tend to favor higher bandwidths. So if 161 is free from interference, I would use it. In fact I do use it. :p
 
I really do appreciate the help guys. :) I'll try all these, also, the laptop is downstairs next to the router/modem (My pc is upstairs) Any tests I can downstairs to confirm anything? Someone said, if you ping test google, and ping test your IP, but google is spikey while IP isnt, certain things can be confirmed? I dont know. Any help on this as well?
 
One more thing to note. Yesterday, I played Diablo 3 with my buddies for hours, (Like from 1:00 to 6:00, NO spikes whatsoever, that I could see, and playing Diablo 3 you'd notice them) Yet later when I logged on, the spikes happened, it was random really. And stayed with me all night. Any thoughts on that as well, I dont know if that helps identify anything.
 
You need to rule out the wi-fi otherwise everything else is speculation.
 
Alright, how do I rule out the wifi? Any step by step instructions to follow first? Im a bit of a noob case on this
 
Additionally, on 5Ghz if there is no congestion at all, higher channels tend to favor higher bandwidths. So if 161 is free from interference, I would use it. In fact I do use it. :p
Im a little confused, mind explaining? :(
 
The easiest way would be to see if you have the same problem when you're connected with an Ethernet cable.
 
Okay, so plug the cable FROM the modem, directly INTO the laptop? And run a google ping test for like an hour? And see the results? If I see HIGH spikes, then that rules out wifi right?
 
So I JUST did the modem test STILL spikes, let me show you the results, it was for 5 minutes but you tell me if this is normal? I dont think it is.
 
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Joey>ping google.com -t

Pinging google.com [2607:f8b0:4004:803::1000] with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=13ms
Reply from 2607:f8b0:4004:803::1000: time=18ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=29ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=19ms
Reply from 2607:f8b0:4004:803::1000: time=13ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=1537ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=13ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=13ms
Reply from 2607:f8b0:4004:803::1000: time=13ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=13ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=17ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=12ms
Reply from 2607:f8b0:4004:803::1000: time=13ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=12ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=12ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=13ms
Reply from 2607:f8b0:4004:803::1000: time=13ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=13ms
Reply from 2607:f8b0:4004:803::1000: time=209ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=30ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=13ms
Reply from 2607:f8b0:4004:803::1000: time=13ms
Reply from 2607:f8b0:4004:803::1000: time=13ms
Request timed out.
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=19ms
Reply from 2607:f8b0:4004:803::1000: time=13ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=12ms
Reply from 2607:f8b0:4004:803::1000: time=13ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=13ms
Reply from 2607:f8b0:4004:803::1000: time=45ms
Reply from 2607:f8b0:4004:803::1000: time=16ms
Reply from 2607:f8b0:4004:803::1000: time=13ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=13ms
Reply from 2607:f8b0:4004:803::1000: time=16ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=28ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=13ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=13ms
Reply from 2607:f8b0:4004:803::1000: time=13ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=16ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=13ms
Reply from 2607:f8b0:4004:803::1000: time=13ms
Reply from 2607:f8b0:4004:803::1000: time=13ms
Reply from 2607:f8b0:4004:803::1000: time=13ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=13ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=19ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=28ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=16ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=13ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=13ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=14ms
Reply from 2607:f8b0:4004:803::1000: time=15ms
Reply from 2607:f8b0:4004:803::1000: time=13ms

Ping statistics for 2607:f8b0:4004:803::1000:
Packets: Sent = 169, Received = 166, Lost = 3 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 1537ms, Average = 25ms
Control-C
^C
C:\Users\Joey>
 
Last edited:
You don't need to continuously add replies, there is an edit button.

I would check the signal on the modem which varies depending on the modem.

What you could do is find the second IP that shows up from a tracert to something on the interweb. This is the first router that is outside your network. If the ping spikes still occur. If they don't, it's Comcast's network. If they do, it's increasingly likely that it may be the signal on your modem to the node your on.
Code:
tracert google.com

It might be worth while to disable ipv6, just to rule it out.
 
Status
Not open for further replies.
Back
Top