Sign in with
Sign up | Sign in
Your question

Constant Spiking

Last response: in Networking
Share
January 17, 2011 7:21:30 AM

The last couple months I've been having a problem with my ping. Normally it pings fine but just about every other day it will start acting up. Every 8th ping I will get a huge spike upwards to anywhere from 400-1000ms. It continues to do this for hours until eventually it stops, then it will start again randomly again. I've tried calling my cable company (Time Warner) and having them come check out the problem. I did this twice and both times they've come out it wasn't doing it. However the second time the person they sent was out was here for almost 2 hours investigating the problem. After he left it seemingly stopped for a couple weeks but the problem has come back.

Here is an example when I ping to Google.


Pinging www.l.google.com [72.14.204.104] with 32 bytes of data:
Reply from 72.14.204.104: bytes=32 time=27ms TTL=55
Reply from 72.14.204.104: bytes=32 time=29ms TTL=55
Reply from 72.14.204.104: bytes=32 time=28ms TTL=55
Reply from 72.14.204.104: bytes=32 time=26ms TTL=55
Reply from 72.14.204.104: bytes=32 time=30ms TTL=55
Reply from 72.14.204.104: bytes=32 time=29ms TTL=55
Reply from 72.14.204.104: bytes=32 time=29ms TTL=55
Reply from 72.14.204.104: bytes=32 time=26ms TTL=55
Reply from 72.14.204.104: bytes=32 time=29ms TTL=55
Reply from 72.14.204.104: bytes=32 time=27ms TTL=55
Reply from 72.14.204.104: bytes=32 time=945ms TTL=55
Reply from 72.14.204.104: bytes=32 time=28ms TTL=55
Reply from 72.14.204.104: bytes=32 time=29ms TTL=55
Reply from 72.14.204.104: bytes=32 time=25ms TTL=55
Reply from 72.14.204.104: bytes=32 time=28ms TTL=55
Reply from 72.14.204.104: bytes=32 time=30ms TTL=55
Reply from 72.14.204.104: bytes=32 time=29ms TTL=55
Reply from 72.14.204.104: bytes=32 time=25ms TTL=55
Reply from 72.14.204.104: bytes=32 time=957ms TTL=55
Reply from 72.14.204.104: bytes=32 time=28ms TTL=55
Reply from 72.14.204.104: bytes=32 time=26ms TTL=55
Reply from 72.14.204.104: bytes=32 time=28ms TTL=55
Reply from 72.14.204.104: bytes=32 time=26ms TTL=55
Reply from 72.14.204.104: bytes=32 time=25ms TTL=55
Reply from 72.14.204.104: bytes=32 time=29ms TTL=55
Reply from 72.14.204.104: bytes=32 time=29ms TTL=55
Reply from 72.14.204.104: bytes=32 time=958ms TTL=55
Reply from 72.14.204.104: bytes=32 time=26ms TTL=55
Reply from 72.14.204.104: bytes=32 time=26ms TTL=55
Reply from 72.14.204.104: bytes=32 time=28ms TTL=55
Reply from 72.14.204.104: bytes=32 time=25ms TTL=55
Reply from 72.14.204.104: bytes=32 time=28ms TTL=55
Reply from 72.14.204.104: bytes=32 time=29ms TTL=55
Reply from 72.14.204.104: bytes=32 time=28ms TTL=55
Reply from 72.14.204.104: bytes=32 time=945ms TTL=55
Reply from 72.14.204.104: bytes=32 time=25ms TTL=55
Reply from 72.14.204.104: bytes=32 time=26ms TTL=55
Reply from 72.14.204.104: bytes=32 time=27ms TTL=55
Reply from 72.14.204.104: bytes=32 time=29ms TTL=55
Reply from 72.14.204.104: bytes=32 time=25ms TTL=55
Reply from 72.14.204.104: bytes=32 time=25ms TTL=55
Reply from 72.14.204.104: bytes=32 time=29ms TTL=55
Reply from 72.14.204.104: bytes=32 time=939ms TTL=55
Reply from 72.14.204.104: bytes=32 time=27ms TTL=55
Reply from 72.14.204.104: bytes=32 time=28ms TTL=55
Reply from 72.14.204.104: bytes=32 time=29ms TTL=55
Reply from 72.14.204.104: bytes=32 time=28ms TTL=55
Reply from 72.14.204.104: bytes=32 time=26ms TTL=55
Reply from 72.14.204.104: bytes=32 time=25ms TTL=55
Reply from 72.14.204.104: bytes=32 time=26ms TTL=55
Reply from 72.14.204.104: bytes=32 time=940ms TTL=55
Reply from 72.14.204.104: bytes=32 time=29ms TTL=55
Reply from 72.14.204.104: bytes=32 time=28ms TTL=55
Reply from 72.14.204.104: bytes=32 time=26ms TTL=55
Reply from 72.14.204.104: bytes=32 time=26ms TTL=55
Reply from 72.14.204.104: bytes=32 time=25ms TTL=55
Reply from 72.14.204.104: bytes=32 time=25ms TTL=55
Reply from 72.14.204.104: bytes=32 time=25ms TTL=55
Reply from 72.14.204.104: bytes=32 time=928ms TTL=55
Reply from 72.14.204.104: bytes=32 time=26ms TTL=55
Reply from 72.14.204.104: bytes=32 time=25ms TTL=55
Reply from 72.14.204.104: bytes=32 time=26ms TTL=55

Sometimes it will do this almost the entire day and night then randomly stop. Lately it's been more sporadic. Sometimes it only lasts a few minutes and stops, then starts against a few minutes later. Really not sure what to do at this point. Any and all help would be much appreciated. Thanks for your time.

More about : constant spiking

January 18, 2011 1:00:37 AM

Well, service interruption is normal, but if it is consistent, it could be intermittent service connection that's so sudden and fast, it may be mistaken for a high ping. You could try resetting the modem.

If you have a router, remove it from the equation and hardwire yourself into the modem.

If you have a router and you've removed it, run this test: http://www.pingtest.net/

If you do not have a router and the issue persists, try replacing the Ethernet cable.
m
0
l
January 18, 2011 10:35:16 PM

do a tracert and do ping -t on your first internet hop

1 <1 ms <1 ms <1 ms 10.0.0.1
2 6 ms 8 ms 6 ms 10.135.160.1
3 7 ms 7 ms 7 ms x.x.x.x
4 11 ms 8 ms 8 ms x.x.x.x
5 10 ms 11 ms 14 ms x.x.x.x
6 11 ms 11 ms 12 ms x.x.x.x
7 21 ms 19 ms 19 ms bbr01chcgil-0-2-0-0.chcg.il.charter.com [96.34.0.167]
8 19 ms 19 ms 19 ms x.x.x.x
9 19 ms 19 ms 20 ms 72.14.222.48
10 18 ms 19 ms 28 ms 72.14.236.178
11 32 ms 30 ms 31 ms 72.14.232.141
12 32 ms 31 ms 30 ms 209.85.241.37
13 34 ms 35 ms 38 ms 66.249.95.138
14 31 ms 31 ms 31 ms iy-in-f105.1e100.net [209.85.225.105]

You can see that hop 2 is my local node. Watch your ping for each hop until you see the spike occurring. If the spike occurs on your first hop, then the connection to your node is bad.
m
0
l
!