Ping Problems

[xshyguyx]

I have Time Warner Broadband Internet and for the past two weeks (since I bought my new computer) I have been having ping issues on both it and another computer in the house. The problem is the same for both. One is connected to a router with an ethernet cable and the other via wireless. Normal ping for the computers is between 80-100ms

here is a ping test I just took:
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

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

Pinging google.com [64.233.187.99] with 32 bytes of data:
Reply from 64.233.187.99: bytes=32 time=88ms TTL=242
Reply from 64.233.187.99: bytes=32 time=83ms TTL=242
Reply from 64.233.187.99: bytes=32 time=83ms TTL=242
Reply from 64.233.187.99: bytes=32 time=83ms TTL=242
Reply from 64.233.187.99: bytes=32 time=83ms TTL=242
Reply from 64.233.187.99: bytes=32 time=82ms TTL=242
Reply from 64.233.187.99: bytes=32 time=86ms TTL=242
Reply from 64.233.187.99: bytes=32 time=83ms TTL=242
Reply from 64.233.187.99: bytes=32 time=83ms TTL=242
Reply from 64.233.187.99: bytes=32 time=83ms TTL=242
Reply from 64.233.187.99: bytes=32 time=83ms TTL=242
Reply from 64.233.187.99: bytes=32 time=122ms TTL=242
Reply from 64.233.187.99: bytes=32 time=324ms TTL=242
Reply from 64.233.187.99: bytes=32 time=347ms TTL=242
Reply from 64.233.187.99: bytes=32 time=349ms TTL=242
Reply from 64.233.187.99: bytes=32 time=221ms TTL=242
Reply from 64.233.187.99: bytes=32 time=312ms TTL=242
Reply from 64.233.187.99: bytes=32 time=272ms TTL=242
Reply from 64.233.187.99: bytes=32 time=251ms TTL=242
Reply from 64.233.187.99: bytes=32 time=1029ms TTL=242
Reply from 64.233.187.99: bytes=32 time=1041ms TTL=242
Reply from 64.233.187.99: bytes=32 time=1018ms TTL=242
Reply from 64.233.187.99: bytes=32 time=1208ms TTL=242
Reply from 64.233.187.99: bytes=32 time=1345ms TTL=242
Reply from 64.233.187.99: bytes=32 time=1500ms TTL=242
Reply from 64.233.187.99: bytes=32 time=1585ms TTL=242
Reply from 64.233.187.99: bytes=32 time=1647ms TTL=242
Reply from 64.233.187.99: bytes=32 time=1451ms TTL=242
Reply from 64.233.187.99: bytes=32 time=227ms TTL=242
Reply from 64.233.187.99: bytes=32 time=83ms TTL=242
Reply from 64.233.187.99: bytes=32 time=83ms TTL=242
Reply from 64.233.187.99: bytes=32 time=83ms TTL=242
Reply from 64.233.187.99: bytes=32 time=80ms TTL=242
Reply from 64.233.187.99: bytes=32 time=83ms TTL=242
Reply from 64.233.187.99: bytes=32 time=83ms TTL=242
Reply from 64.233.187.99: bytes=32 time=83ms TTL=242
Reply from 64.233.187.99: bytes=32 time=85ms TTL=242
Reply from 64.233.187.99: bytes=32 time=83ms TTL=242
Reply from 64.233.187.99: bytes=32 time=80ms TTL=242
Reply from 64.233.187.99: bytes=32 time=460ms TTL=242
Request timed out.
Reply from 64.233.187.99: bytes=32 time=565ms TTL=242
Reply from 64.233.187.99: bytes=32 time=171ms TTL=242
Reply from 64.233.187.99: bytes=32 time=88ms TTL=242
Reply from 64.233.187.99: bytes=32 time=120ms TTL=242
Reply from 64.233.187.99: bytes=32 time=276ms TTL=242
Reply from 64.233.187.99: bytes=32 time=107ms TTL=242
Reply from 64.233.187.99: bytes=32 time=198ms TTL=242
Reply from 64.233.187.99: bytes=32 time=300ms TTL=242
Reply from 64.233.187.99: bytes=32 time=303ms TTL=242
Reply from 64.233.187.99: bytes=32 time=414ms TTL=242
Reply from 64.233.187.99: bytes=32 time=84ms TTL=242
Reply from 64.233.187.99: bytes=32 time=296ms TTL=242
Reply from 64.233.187.99: bytes=32 time=82ms TTL=242
Reply from 64.233.187.99: bytes=32 time=297ms TTL=242
Reply from 64.233.187.99: bytes=32 time=263ms TTL=242
Reply from 64.233.187.99: bytes=32 time=265ms TTL=242
Reply from 64.233.187.99: bytes=32 time=129ms TTL=242
Reply from 64.233.187.99: bytes=32 time=302ms TTL=242
Reply from 64.233.187.99: bytes=32 time=984ms TTL=242
Reply from 64.233.187.99: bytes=32 time=1212ms TTL=242
Reply from 64.233.187.99: bytes=32 time=1166ms TTL=242
Reply from 64.233.187.99: bytes=32 time=1157ms TTL=242
Reply from 64.233.187.99: bytes=32 time=1320ms TTL=242
Reply from 64.233.187.99: bytes=32 time=1251ms TTL=242
Reply from 64.233.187.99: bytes=32 time=1395ms TTL=242
Reply from 64.233.187.99: bytes=32 time=1501ms TTL=242
Request timed out.
Reply from 64.233.187.99: bytes=32 time=82ms TTL=242
Reply from 64.233.187.99: bytes=32 time=85ms TTL=242
Reply from 64.233.187.99: bytes=32 time=82ms TTL=242
Reply from 64.233.187.99: bytes=32 time=82ms TTL=242
Reply from 64.233.187.99: bytes=32 time=82ms TTL=242
Reply from 64.233.187.99: bytes=32 time=82ms TTL=242
Reply from 64.233.187.99: bytes=32 time=81ms TTL=242
Reply from 64.233.187.99: bytes=32 time=444ms TTL=242
Reply from 64.233.187.99: bytes=32 time=85ms TTL=242
Reply from 64.233.187.99: bytes=32 time=142ms TTL=242
Reply from 64.233.187.99: bytes=32 time=83ms TTL=242
Reply from 64.233.187.99: bytes=32 time=82ms TTL=242
Reply from 64.233.187.99: bytes=32 time=85ms TTL=242
Reply from 64.233.187.99: bytes=32 time=82ms TTL=242
Reply from 64.233.187.99: bytes=32 time=83ms TTL=242
Reply from 64.233.187.99: bytes=32 time=82ms TTL=242
Reply from 64.233.187.99: bytes=32 time=83ms TTL=242
Reply from 64.233.187.99: bytes=32 time=236ms TTL=242
Reply from 64.233.187.99: bytes=32 time=83ms TTL=242
Reply from 64.233.187.99: bytes=32 time=82ms TTL=242
Reply from 64.233.187.99: bytes=32 time=101ms TTL=242
Reply from 64.233.187.99: bytes=32 time=82ms TTL=242
Reply from 64.233.187.99: bytes=32 time=82ms TTL=242
Reply from 64.233.187.99: bytes=32 time=85ms TTL=242
Reply from 64.233.187.99: bytes=32 time=82ms TTL=242
Reply from 64.233.187.99: bytes=32 time=81ms TTL=242
Reply from 64.233.187.99: bytes=32 time=81ms TTL=242
Reply from 64.233.187.99: bytes=32 time=81ms TTL=242
Reply from 64.233.187.99: bytes=32 time=81ms TTL=242
Reply from 64.233.187.99: bytes=32 time=83ms TTL=242
Reply from 64.233.187.99: bytes=32 time=540ms TTL=242
Reply from 64.233.187.99: bytes=32 time=1133ms TTL=242
Reply from 64.233.187.99: bytes=32 time=954ms TTL=242
Reply from 64.233.187.99: bytes=32 time=894ms TTL=242
Reply from 64.233.187.99: bytes=32 time=980ms TTL=242
Reply from 64.233.187.99: bytes=32 time=1228ms TTL=242
Reply from 64.233.187.99: bytes=32 time=1378ms TTL=242
Reply from 64.233.187.99: bytes=32 time=1369ms TTL=242
Reply from 64.233.187.99: bytes=32 time=1497ms TTL=242
Reply from 64.233.187.99: bytes=32 time=1339ms TTL=242
Reply from 64.233.187.99: bytes=32 time=197ms TTL=242
Reply from 64.233.187.99: bytes=32 time=97ms TTL=242
Reply from 64.233.187.99: bytes=32 time=84ms TTL=242
Reply from 64.233.187.99: bytes=32 time=84ms TTL=242
Reply from 64.233.187.99: bytes=32 time=99ms TTL=242
Reply from 64.233.187.99: bytes=32 time=87ms TTL=242
Reply from 64.233.187.99: bytes=32 time=100ms TTL=242
Reply from 64.233.187.99: bytes=32 time=83ms TTL=242
Reply from 64.233.187.99: bytes=32 time=84ms TTL=242
Reply from 64.233.187.99: bytes=32 time=83ms TTL=242
Reply from 64.233.187.99: bytes=32 time=83ms TTL=242
Reply from 64.233.187.99: bytes=32 time=80ms TTL=242
Reply from 64.233.187.99: bytes=32 time=83ms TTL=242
Reply from 64.233.187.99: bytes=32 time=84ms TTL=242
Reply from 64.233.187.99: bytes=32 time=86ms TTL=242
Reply from 64.233.187.99: bytes=32 time=83ms TTL=242
Reply from 64.233.187.99: bytes=32 time=254ms TTL=242
Reply from 64.233.187.99: bytes=32 time=104ms TTL=242
Reply from 64.233.187.99: bytes=32 time=568ms TTL=242
Reply from 64.233.187.99: bytes=32 time=533ms TTL=242
Reply from 64.233.187.99: bytes=32 time=1021ms TTL=242
Reply from 64.233.187.99: bytes=32 time=683ms TTL=242
Reply from 64.233.187.99: bytes=32 time=393ms TTL=242
Reply from 64.233.187.99: bytes=32 time=566ms TTL=242
Reply from 64.233.187.99: bytes=32 time=373ms TTL=242
Reply from 64.233.187.99: bytes=32 time=452ms TTL=242
Reply from 64.233.187.99: bytes=32 time=614ms TTL=242
Reply from 64.233.187.99: bytes=32 time=141ms TTL=242
Reply from 64.233.187.99: bytes=32 time=324ms TTL=242
Reply from 64.233.187.99: bytes=32 time=82ms TTL=242

Ping statistics for 64.233.187.99:
Packets: Sent = 138, Received = 136, Lost = 2 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 80ms, Maximum = 1647ms, Average = 387ms
Control-C
^C
C:\Users\user>

As you can see, my ping for the most part is no where near normal. This makes things like playing online games impossible. I am wondering if there is anything I can do to fix this: is this a router problem or my internet provider?

 

[ereetos]

take the new computer off the network and power cycle the modem/router

ping again, if it still is laggy, connect the modem directly to the old pc and ping again.

still laggy? probably an ISP issue

 

[gamerk316]

Gets really laggy, but its not constant. I'm leadning toward the ISP.

Try running a few tracert commands (eg: tracert www.google.com) and see if there is a particular spot where you hang. I have to use tracert alot, because it helps me figure out where our server host needs to be for best connection speeds.

 

[vaengaivenkat]

You can Please Un-Plug the model Router and Remove the Connection from Computer,then You can reconnect the all the Wire and reset the wireless modem,then You can check the PING Test here Whoisxy it will be normal...Then while Play Online games Ping differ time to time..

 

[tokencode]

Sporadic packet loss accompanied by increased latency, sounds like bandwidth being maxed out to me, either by some device within your network or or on your cable node

 

[Guest]

This topic has been moved from the section Toms Network to section Networking by Grumpy9117