Sign in with
Sign up | Sign in
Your question
Solved

I am having high latency/ping in games

Tags:
  • Latency
  • Traceroute
  • Internet Access
  • Wireless
  • Wireless Network
  • Command Prompt
Last response: in Wireless Networking
Share
October 1, 2014 2:20:21 PM

I have been miserably lagging lately in games lately. For example when i play BF4 i will have CMD pinging the server for the game while i am playing. It constantly jumps from my average of 40ms to 1500-4000ms. I am on wireless but it has never been an issue until the last month or so. Ideas please. Feel free to ask about tracerouting or my hardware and so on. I appreciate the look.

More about : high latency ping games

October 1, 2014 2:40:49 PM

What kind of environment are you in, as an example wireless at apartments can be really inconsistent as they are a lot of wireless signals going on. Also how many users/devices are using the same wireless connection.

Also its always good to check to see if there inst any malware/adware draining your internet connection.
If you don't have any tools Malwarebytes is a great free tool to just run a scan.
https://www.malwarebytes.org/
m
0
l
October 1, 2014 2:57:19 PM

AVG says im fine and i am in the country with no houses for a mile
m
0
l
Related resources
October 1, 2014 3:00:25 PM

Avg is considered a Anti virus they don't focus much on malware/adware, would highly recommend trying to run malwarebytes or any other malware remover tool.
m
1
l
October 1, 2014 3:00:58 PM

Heres my ping from the last BF4 game and no other device is on the internet right now and when i did this.



Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>ping 75.102.40.202 -t

Pinging 75.102.40.202 with 32 bytes of data:
Reply from 75.102.40.202: bytes=32 time=41ms TTL=117
Reply from 75.102.40.202: bytes=32 time=41ms TTL=117
Reply from 75.102.40.202: bytes=32 time=40ms TTL=117
Reply from 75.102.40.202: bytes=32 time=41ms TTL=117
Reply from 75.102.40.202: bytes=32 time=42ms TTL=117
Reply from 75.102.40.202: bytes=32 time=61ms TTL=117
Reply from 75.102.40.202: bytes=32 time=41ms TTL=117
Reply from 75.102.40.202: bytes=32 time=44ms TTL=117
Reply from 75.102.40.202: bytes=32 time=45ms TTL=117
Reply from 75.102.40.202: bytes=32 time=39ms TTL=117
Reply from 75.102.40.202: bytes=32 time=43ms TTL=117
Reply from 75.102.40.202: bytes=32 time=86ms TTL=117
Reply from 75.102.40.202: bytes=32 time=46ms TTL=117
Reply from 75.102.40.202: bytes=32 time=40ms TTL=117
Reply from 75.102.40.202: bytes=32 time=44ms TTL=117
Reply from 75.102.40.202: bytes=32 time=42ms TTL=117
Reply from 75.102.40.202: bytes=32 time=39ms TTL=117
Reply from 75.102.40.202: bytes=32 time=48ms TTL=117
Reply from 75.102.40.202: bytes=32 time=51ms TTL=117
Reply from 75.102.40.202: bytes=32 time=40ms TTL=117
Reply from 75.102.40.202: bytes=32 time=41ms TTL=117
Reply from 75.102.40.202: bytes=32 time=42ms TTL=117
Reply from 75.102.40.202: bytes=32 time=40ms TTL=117
Reply from 75.102.40.202: bytes=32 time=40ms TTL=117
Reply from 75.102.40.202: bytes=32 time=140ms TTL=117
Reply from 75.102.40.202: bytes=32 time=42ms TTL=117
Reply from 75.102.40.202: bytes=32 time=40ms TTL=117
Reply from 75.102.40.202: bytes=32 time=43ms TTL=117
Reply from 75.102.40.202: bytes=32 time=41ms TTL=117
Reply from 75.102.40.202: bytes=32 time=38ms TTL=117
Reply from 75.102.40.202: bytes=32 time=39ms TTL=117
Reply from 75.102.40.202: bytes=32 time=45ms TTL=117
Reply from 75.102.40.202: bytes=32 time=39ms TTL=117
Reply from 75.102.40.202: bytes=32 time=40ms TTL=117
Reply from 75.102.40.202: bytes=32 time=39ms TTL=117
Reply from 75.102.40.202: bytes=32 time=39ms TTL=117
Reply from 75.102.40.202: bytes=32 time=40ms TTL=117
Reply from 75.102.40.202: bytes=32 time=108ms TTL=117
Reply from 75.102.40.202: bytes=32 time=40ms TTL=117
Reply from 75.102.40.202: bytes=32 time=41ms TTL=117
Reply from 75.102.40.202: bytes=32 time=41ms TTL=117
Reply from 75.102.40.202: bytes=32 time=45ms TTL=117
Reply from 75.102.40.202: bytes=32 time=49ms TTL=117
Reply from 75.102.40.202: bytes=32 time=38ms TTL=117
Reply from 75.102.40.202: bytes=32 time=1250ms TTL=117
Reply from 75.102.40.202: bytes=32 time=44ms TTL=117
Reply from 75.102.40.202: bytes=32 time=55ms TTL=117
Reply from 75.102.40.202: bytes=32 time=43ms TTL=117
Reply from 75.102.40.202: bytes=32 time=40ms TTL=117
Reply from 75.102.40.202: bytes=32 time=42ms TTL=117
Reply from 75.102.40.202: bytes=32 time=40ms TTL=117
Reply from 75.102.40.202: bytes=32 time=43ms TTL=117
Reply from 75.102.40.202: bytes=32 time=41ms TTL=117
Reply from 75.102.40.202: bytes=32 time=134ms TTL=117
Reply from 75.102.40.202: bytes=32 time=41ms TTL=117
Reply from 75.102.40.202: bytes=32 time=41ms TTL=117
Reply from 75.102.40.202: bytes=32 time=45ms TTL=117
Reply from 75.102.40.202: bytes=32 time=40ms TTL=117
Reply from 75.102.40.202: bytes=32 time=43ms TTL=117
Reply from 75.102.40.202: bytes=32 time=40ms TTL=117
Reply from 75.102.40.202: bytes=32 time=40ms TTL=117
Reply from 75.102.40.202: bytes=32 time=42ms TTL=117
Reply from 75.102.40.202: bytes=32 time=43ms TTL=117
Reply from 75.102.40.202: bytes=32 time=42ms TTL=117
Reply from 75.102.40.202: bytes=32 time=50ms TTL=117
Reply from 75.102.40.202: bytes=32 time=41ms TTL=117
Reply from 75.102.40.202: bytes=32 time=42ms TTL=117
Reply from 75.102.40.202: bytes=32 time=39ms TTL=117
Reply from 75.102.40.202: bytes=32 time=39ms TTL=117
Reply from 75.102.40.202: bytes=32 time=40ms TTL=117
Reply from 75.102.40.202: bytes=32 time=39ms TTL=117
Reply from 75.102.40.202: bytes=32 time=40ms TTL=117
Reply from 75.102.40.202: bytes=32 time=114ms TTL=117
Reply from 75.102.40.202: bytes=32 time=1333ms TTL=117
Reply from 75.102.40.202: bytes=32 time=195ms TTL=117
Reply from 75.102.40.202: bytes=32 time=73ms TTL=117
Reply from 75.102.40.202: bytes=32 time=161ms TTL=117
Reply from 75.102.40.202: bytes=32 time=129ms TTL=117
Reply from 75.102.40.202: bytes=32 time=133ms TTL=117
Reply from 75.102.40.202: bytes=32 time=2047ms TTL=117
Reply from 75.102.40.202: bytes=32 time=59ms TTL=117
Reply from 75.102.40.202: bytes=32 time=53ms TTL=117
Reply from 75.102.40.202: bytes=32 time=62ms TTL=117
Reply from 75.102.40.202: bytes=32 time=79ms TTL=117
Reply from 75.102.40.202: bytes=32 time=43ms TTL=117
Reply from 75.102.40.202: bytes=32 time=76ms TTL=117
Reply from 75.102.40.202: bytes=32 time=104ms TTL=117
Reply from 75.102.40.202: bytes=32 time=193ms TTL=117
Reply from 75.102.40.202: bytes=32 time=927ms TTL=117
Reply from 75.102.40.202: bytes=32 time=53ms TTL=117
Reply from 75.102.40.202: bytes=32 time=2092ms TTL=117
Reply from 75.102.40.202: bytes=32 time=41ms TTL=117
Reply from 75.102.40.202: bytes=32 time=131ms TTL=117
Reply from 75.102.40.202: bytes=32 time=41ms TTL=117
Reply from 75.102.40.202: bytes=32 time=147ms TTL=117
Reply from 75.102.40.202: bytes=32 time=154ms TTL=117
Reply from 75.102.40.202: bytes=32 time=157ms TTL=117
Reply from 75.102.40.202: bytes=32 time=62ms TTL=117
Reply from 75.102.40.202: bytes=32 time=185ms TTL=117
Reply from 75.102.40.202: bytes=32 time=48ms TTL=117
Reply from 75.102.40.202: bytes=32 time=107ms TTL=117
Reply from 75.102.40.202: bytes=32 time=189ms TTL=117
Reply from 75.102.40.202: bytes=32 time=83ms TTL=117
Reply from 75.102.40.202: bytes=32 time=42ms TTL=117
Reply from 75.102.40.202: bytes=32 time=44ms TTL=117
Reply from 75.102.40.202: bytes=32 time=1076ms TTL=117
Reply from 75.102.40.202: bytes=32 time=466ms TTL=117
Reply from 75.102.40.202: bytes=32 time=557ms TTL=117
Reply from 75.102.40.202: bytes=32 time=267ms TTL=117
Reply from 75.102.40.202: bytes=32 time=42ms TTL=117
Reply from 75.102.40.202: bytes=32 time=43ms TTL=117
Reply from 75.102.40.202: bytes=32 time=219ms TTL=117
Reply from 75.102.40.202: bytes=32 time=113ms TTL=117
Reply from 75.102.40.202: bytes=32 time=320ms TTL=117
Reply from 75.102.40.202: bytes=32 time=62ms TTL=117
Reply from 75.102.40.202: bytes=32 time=132ms TTL=117
Reply from 75.102.40.202: bytes=32 time=43ms TTL=117
Reply from 75.102.40.202: bytes=32 time=56ms TTL=117
Reply from 75.102.40.202: bytes=32 time=42ms TTL=117
Reply from 75.102.40.202: bytes=32 time=41ms TTL=117
Reply from 75.102.40.202: bytes=32 time=87ms TTL=117
Reply from 75.102.40.202: bytes=32 time=84ms TTL=117
Reply from 75.102.40.202: bytes=32 time=115ms TTL=117
Reply from 75.102.40.202: bytes=32 time=110ms TTL=117
Reply from 75.102.40.202: bytes=32 time=85ms TTL=117
Reply from 75.102.40.202: bytes=32 time=65ms TTL=117
Reply from 75.102.40.202: bytes=32 time=105ms TTL=117
Reply from 75.102.40.202: bytes=32 time=75ms TTL=117
Reply from 75.102.40.202: bytes=32 time=551ms TTL=117
Reply from 75.102.40.202: bytes=32 time=55ms TTL=117
Reply from 75.102.40.202: bytes=32 time=80ms TTL=117
Reply from 75.102.40.202: bytes=32 time=41ms TTL=117
Reply from 75.102.40.202: bytes=32 time=634ms TTL=117
Reply from 75.102.40.202: bytes=32 time=133ms TTL=117
Reply from 75.102.40.202: bytes=32 time=286ms TTL=117
Reply from 75.102.40.202: bytes=32 time=1026ms TTL=117
Reply from 75.102.40.202: bytes=32 time=779ms TTL=117
Reply from 75.102.40.202: bytes=32 time=388ms TTL=117
Request timed out.
Reply from 75.102.40.202: bytes=32 time=84ms TTL=117
Request timed out.
Reply from 75.102.40.202: bytes=32 time=76ms TTL=117
Reply from 75.102.40.202: bytes=32 time=1401ms TTL=117
Reply from 75.102.40.202: bytes=32 time=47ms TTL=117
Reply from 75.102.40.202: bytes=32 time=41ms TTL=117
Reply from 75.102.40.202: bytes=32 time=46ms TTL=117
Reply from 75.102.40.202: bytes=32 time=48ms TTL=117
Reply from 75.102.40.202: bytes=32 time=44ms TTL=117
Reply from 75.102.40.202: bytes=32 time=1324ms TTL=117
Reply from 75.102.40.202: bytes=32 time=650ms TTL=117
Reply from 75.102.40.202: bytes=32 time=190ms TTL=117
Reply from 75.102.40.202: bytes=32 time=290ms TTL=117
Reply from 75.102.40.202: bytes=32 time=155ms TTL=117
Reply from 75.102.40.202: bytes=32 time=664ms TTL=117
Reply from 75.102.40.202: bytes=32 time=264ms TTL=117
Reply from 75.102.40.202: bytes=32 time=1024ms TTL=117
Reply from 75.102.40.202: bytes=32 time=57ms TTL=117
Reply from 75.102.40.202: bytes=32 time=214ms TTL=117
Reply from 75.102.40.202: bytes=32 time=279ms TTL=117
Reply from 75.102.40.202: bytes=32 time=722ms TTL=117
Reply from 75.102.40.202: bytes=32 time=608ms TTL=117
Reply from 75.102.40.202: bytes=32 time=69ms TTL=117
Reply from 75.102.40.202: bytes=32 time=60ms TTL=117
Reply from 75.102.40.202: bytes=32 time=41ms TTL=117
Reply from 75.102.40.202: bytes=32 time=270ms TTL=117
Reply from 75.102.40.202: bytes=32 time=51ms TTL=117
Reply from 75.102.40.202: bytes=32 time=45ms TTL=117
Reply from 75.102.40.202: bytes=32 time=162ms TTL=117
Reply from 75.102.40.202: bytes=32 time=69ms TTL=117
Reply from 75.102.40.202: bytes=32 time=56ms TTL=117
Reply from 75.102.40.202: bytes=32 time=199ms TTL=117
Reply from 75.102.40.202: bytes=32 time=534ms TTL=117
Reply from 75.102.40.202: bytes=32 time=1231ms TTL=117
Reply from 75.102.40.202: bytes=32 time=205ms TTL=117
Reply from 75.102.40.202: bytes=32 time=2147ms TTL=117
Reply from 75.102.40.202: bytes=32 time=73ms TTL=117
Request timed out.
Reply from 75.102.40.202: bytes=32 time=890ms TTL=117
Reply from 75.102.40.202: bytes=32 time=264ms TTL=117
Reply from 75.102.40.202: bytes=32 time=2364ms TTL=117
Reply from 75.102.40.202: bytes=32 time=61ms TTL=117
Reply from 75.102.40.202: bytes=32 time=96ms TTL=117
Reply from 75.102.40.202: bytes=32 time=821ms TTL=117
Reply from 75.102.40.202: bytes=32 time=39ms TTL=117
Reply from 75.102.40.202: bytes=32 time=1603ms TTL=117
Reply from 75.102.40.202: bytes=32 time=99ms TTL=117
Reply from 75.102.40.202: bytes=32 time=144ms TTL=117
Reply from 75.102.40.202: bytes=32 time=115ms TTL=117
Reply from 75.102.40.202: bytes=32 time=173ms TTL=117
Reply from 75.102.40.202: bytes=32 time=70ms TTL=117
Reply from 75.102.40.202: bytes=32 time=46ms TTL=117
Reply from 75.102.40.202: bytes=32 time=83ms TTL=117
Reply from 75.102.40.202: bytes=32 time=101ms TTL=117
Reply from 75.102.40.202: bytes=32 time=76ms TTL=117
Reply from 75.102.40.202: bytes=32 time=48ms TTL=117
Reply from 75.102.40.202: bytes=32 time=53ms TTL=117
Reply from 75.102.40.202: bytes=32 time=66ms TTL=117
Reply from 75.102.40.202: bytes=32 time=79ms TTL=117
Reply from 75.102.40.202: bytes=32 time=379ms TTL=117
Reply from 75.102.40.202: bytes=32 time=275ms TTL=117
Reply from 75.102.40.202: bytes=32 time=306ms TTL=117
Reply from 75.102.40.202: bytes=32 time=1596ms TTL=117
Reply from 75.102.40.202: bytes=32 time=760ms TTL=117
Reply from 75.102.40.202: bytes=32 time=100ms TTL=117
Reply from 75.102.40.202: bytes=32 time=1224ms TTL=117
Reply from 75.102.40.202: bytes=32 time=56ms TTL=117
Reply from 75.102.40.202: bytes=32 time=39ms TTL=117
Reply from 75.102.40.202: bytes=32 time=43ms TTL=117
Reply from 75.102.40.202: bytes=32 time=41ms TTL=117
Reply from 75.102.40.202: bytes=32 time=40ms TTL=117
Reply from 75.102.40.202: bytes=32 time=41ms TTL=117
Reply from 75.102.40.202: bytes=32 time=42ms TTL=117
Reply from 75.102.40.202: bytes=32 time=46ms TTL=117
Reply from 75.102.40.202: bytes=32 time=42ms TTL=117
Reply from 75.102.40.202: bytes=32 time=40ms TTL=117
Reply from 75.102.40.202: bytes=32 time=43ms TTL=117
Reply from 75.102.40.202: bytes=32 time=47ms TTL=117
Reply from 75.102.40.202: bytes=32 time=41ms TTL=117
Reply from 75.102.40.202: bytes=32 time=41ms TTL=117
Reply from 75.102.40.202: bytes=32 time=41ms TTL=117
Reply from 75.102.40.202: bytes=32 time=43ms TTL=117
Reply from 75.102.40.202: bytes=32 time=49ms TTL=117
Reply from 75.102.40.202: bytes=32 time=42ms TTL=117
Reply from 75.102.40.202: bytes=32 time=42ms TTL=117
Reply from 75.102.40.202: bytes=32 time=40ms TTL=117
Reply from 75.102.40.202: bytes=32 time=41ms TTL=117
Reply from 75.102.40.202: bytes=32 time=41ms TTL=117
Reply from 75.102.40.202: bytes=32 time=50ms TTL=117
Reply from 75.102.40.202: bytes=32 time=41ms TTL=117
Reply from 75.102.40.202: bytes=32 time=43ms TTL=117
Reply from 75.102.40.202: bytes=32 time=40ms TTL=117
Reply from 75.102.40.202: bytes=32 time=41ms TTL=117
m
0
l
October 1, 2014 3:02:22 PM

Starting malwarebytes now. It'll be a while with my 1.5 Tb of files.
m
0
l
October 1, 2014 3:09:01 PM

Also if it helps eliminate causes. I am 10 feet from the 802.11n router through 2 walls made of drywall.
m
0
l
October 2, 2014 3:10:56 PM

Hello Ken blank!

That sudden lag spike might be either caused a) by the ISP, b) by your router, or c) by your computer network card.

Can you tell me if the modem/router is provided by your ISP and if it's a modem and router combination.

Thanks! :) 
m
0
l
October 2, 2014 3:22:38 PM

The modem was provided by Time Warner, and no they are seperate.
m
0
l
October 2, 2014 3:23:46 PM

Also ask any questions you like. ☻
m
0
l
October 2, 2014 6:39:56 PM

Malwarebytes Result. Sorry for the wait i let it run overnight and we had a brownout.

Malwarebytes Anti-Malware
www.malwarebytes.org

Scan Date: 10/2/2014
Scan Time: 6:29:20 PM
Logfile: l.txt
Administrator: Yes

Version: 2.00.2.1012
Malware Database: v2014.10.02.10
Rootkit Database: v2014.09.19.01
License: Trial
Malware Protection: Enabled
Malicious Website Protection: Enabled
Self-protection: Disabled

OS: Windows 8.1
CPU: x64
File System: NTFS

Scan Type: Custom Scan
Result: Completed
Objects Scanned: 670228
Time Elapsed: 3 hr, 7 min, 2 sec

Memory: Enabled
Startup: Enabled
Filesystem: Enabled
Archives: Enabled
Rootkits: Enabled
Heuristics: Enabled
PUP: Enabled
PUM: Enabled

Processes: 0
(No malicious items detected)

Modules: 0
(No malicious items detected)

Registry Keys: 0
(No malicious items detected)

Registry Values: 0
(No malicious items detected)

Registry Data: 0
(No malicious items detected)

Folders: 1
PUP.Optional.WeatherAlerts, C:\Users\Kenny\AppData\Local\WeatherAlerts, Quarantined, [4243c12efb80f244b3fa0dd5d1317a86],

Files: 0
(No malicious items detected)

Physical Sectors: 0
(No malicious items detected)


(end)
m
0
l
October 2, 2014 6:40:31 PM

ill run it again too
m
0
l
October 2, 2014 6:45:44 PM

Also im very comfortable with technology. I simply dont know where to start on this subject. So ask what you wish. And again thanks for your time!
m
0
l
October 2, 2014 7:08:21 PM

Alright!

The modem is provided by your ISP, how about your router? Did you buy it yourself? Is it a good one? Model #?
m
0
l
October 2, 2014 7:46:16 PM

The router is mine Linksys WRT160Nv2

also sorry for the slow reply i got that 2 hours after you posted that even with refreshing
m
0
l
October 2, 2014 7:48:22 PM

also i would run pingtest.net for you but it crashes my browsers!
m
0
l
October 2, 2014 8:04:10 PM

Also if it helps





Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>tracert google.com

Tracing route to google.com [74.125.228.8]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 22 ms 29 ms 30 ms cpe-98-30-185-1.woh.res.rr.com [98.30.185.1]
3 11 ms 10 ms 11 ms 98.30.200.66
4 10 ms 11 ms 11 ms tge8-1.rcfroh0201h.midwest.rr.com [24.33.162.98]

5 21 ms 23 ms 24 ms 24.33.162.102
6 21 ms 18 ms 23 ms 65.29.1.34
7 31 ms 31 ms 30 ms bu-ether15.atlngamq47w-bcr01.tbone.rr.com [107.14.19.36]
8 30 ms 30 ms 30 ms ae-1-0.pr0.chi10.tbone.rr.com [66.109.6.155]
9 28 ms 30 ms 30 ms ix-17-0.tcore1.CT8-Chicago.as6453.net [63.243.129.21]
10 30 ms 30 ms 30 ms fg-out-1718.google.com [72.14.220.158]
11 40 ms 30 ms 42 ms 209.85.244.3
12 29 ms 30 ms 32 ms 209.85.254.240
13 43 ms 41 ms 42 ms 72.14.232.70
14 46 ms 39 ms 55 ms 72.14.236.149
15 39 ms 39 ms 41 ms 72.14.238.173
16 42 ms 42 ms 41 ms iad23s05-in-f8.1e100.net [74.125.228.8]

Trace complete.





C:\WINDOWS\system32>tracert yahoo.com

Tracing route to yahoo.com [206.190.36.45]
over a maximum of 30 hops:

1 1 ms 2 ms 1 ms 192.168.1.1
2 35 ms 27 ms 29 ms cpe-98-30-185-1.woh.res.rr.com [98.30.185.1]
3 11 ms 11 ms 11 ms 98.30.200.66
4 10 ms 11 ms 11 ms tge8-1.rcfroh0201h.midwest.rr.com [24.33.162.98]

5 22 ms 23 ms 19 ms 24.33.162.102
6 20 ms 19 ms 18 ms 65.29.1.34
7 31 ms 31 ms 30 ms bu-ether35.cr0.chi30.tbone.rr.com [107.14.19.60]

8 44 ms 30 ms 28 ms 107.14.17.147
9 29 ms 32 ms 30 ms 216.1.123.17
10 92 ms 95 ms 95 ms 207.88.14.193.ptr.us.xo.net [207.88.14.193]
11 94 ms 95 ms 94 ms te-4-1-0.rar3.denver-co.us.xo.net [207.88.12.22]

12 93 ms 95 ms 94 ms te-3-0-0.rar3.seattle-wa.us.xo.net [207.88.12.81]
13 * 103 ms 104 ms ae0d0.cir1.seattle7-wa.us.xo.net [207.88.13.141]

14 93 ms 92 ms 92 ms 216.156.100.54.ptr.us.xo.net [216.156.100.54]
15 131 ms 97 ms 96 ms ae-5.pat2.gqb.yahoo.com [216.115.101.197]
16 106 ms 97 ms 107 ms ae-0.msr1.gq1.yahoo.com [66.196.67.1]
17 96 ms 97 ms 111 ms UNKNOWN-67-195-1-X.yahoo.com [67.195.1.197]
18 109 ms 108 ms 108 ms et-18-25.fab2-1-gdc.gq1.yahoo.com [98.137.31.170]
19 113 ms 109 ms 110 ms po-10.bas1-7-prd.gq1.yahoo.com [206.190.32.15]
20 104 ms 96 ms 97 ms ir1.fp.vip.gq1.yahoo.com [206.190.36.45]

Trace complete.





C:\WINDOWS\system32>tracert youtube.com

Tracing route to youtube.com [74.125.225.78]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 21 ms 28 ms 19 ms cpe-98-30-185-1.woh.res.rr.com [98.30.185.1]
3 11 ms 10 ms 11 ms 98.30.200.66
4 9 ms 11 ms 11 ms tge8-2.rcfroh0201h.midwest.rr.com [24.33.162.100]
5 22 ms 19 ms 22 ms 24.33.162.104
6 24 ms 22 ms 23 ms 65.29.1.34
7 35 ms 30 ms 31 ms bu-ether15.atlngamq47w-bcr01.tbone.rr.com [107.14.19.36]
8 30 ms 29 ms 30 ms ae-2-0.a0.buf00.tbone.rr.com [66.109.1.42]
9 28 ms 27 ms 28 ms ix-17-0.tcore1.CT8-Chicago.as6453.net [63.243.129.21]
10 28 ms 30 ms 32 ms fg-out-1718.google.com [72.14.220.158]
11 30 ms 36 ms 31 ms 209.85.244.3
12 29 ms 30 ms 30 ms 209.85.250.30
13 29 ms 33 ms 30 ms ord08s07-in-f14.1e100.net [74.125.225.78]

Trace complete.





C:\WINDOWS\system32>tracert thecoolclass.com

Tracing route to thecoolclass.com [67.222.60.234]
over a maximum of 30 hops:

1 1 ms 7 ms 1 ms 192.168.1.1
2 26 ms 28 ms 28 ms cpe-98-30-185-1.woh.res.rr.com [98.30.185.1]
3 10 ms 11 ms 12 ms 98.30.200.66
4 9 ms 11 ms 11 ms tge8-2.rcfroh0201h.midwest.rr.com [24.33.162.100]
5 22 ms 19 ms 22 ms 24.33.162.104
6 21 ms 18 ms 23 ms 65.29.1.34
7 123 ms 121 ms 124 ms bu-ether15.atlngamq47w-bcr01.tbone.rr.com [107.14.19.36]
8 134 ms 133 ms 133 ms ae-0-0.cr0.chi10.tbone.rr.com [66.109.6.20]
9 143 ms 70 ms 177 ms ae1.pr1.chi10.tbone.rr.com [107.14.17.194]
10 127 ms 124 ms 128 ms v396.core1.chi1.he.net [184.105.255.29]
11 171 ms 177 ms 171 ms 10ge3-2.core1.den1.he.net [184.105.213.86]
12 169 ms 179 ms 178 ms 10ge4-2.core1.slc1.he.net [184.105.222.154]
13 86 ms 95 ms 99 ms ace-data-centers-inc.10gigabitethernet1-4.core1.slc1.he.net [66.160.133.118]
14 287 ms 103 ms 104 ms rtr-b.unifiedlayer.com [199.58.199.118]
15 87 ms 87 ms 86 ms 67-222-60-234.unifiedlayer.com [67.222.60.234]

Trace complete.





C:\WINDOWS\system32>tracert hackthissite.org

Tracing route to hackthissite.org [198.148.81.138]
over a maximum of 30 hops:

1 1 ms 3 ms 1 ms 192.168.1.1
2 141 ms 128 ms 83 ms cpe-98-30-185-1.woh.res.rr.com [98.30.185.1]
3 11 ms 10 ms 11 ms 98.30.200.66
4 12 ms 11 ms 11 ms tge8-2.rcfroh0201h.midwest.rr.com [24.33.162.100]
5 22 ms 19 ms 22 ms 24.33.162.102
6 45 ms 66 ms 45 ms 65.29.1.34
7 39 ms 43 ms 40 ms bu-ether25.cr0.chi30.tbone.rr.com [107.14.19.16]

8 125 ms 121 ms 121 ms ae-0-0.cr0.chi10.tbone.rr.com [66.109.6.20]
9 * * * Request timed out.
10 80 ms 30 ms 28 ms agg-eth-2-pe05.350ecermak.il.ibone.comcast.net [75.149.230.69]
11 33 ms 31 ms 31 ms he-2-0-0-0-cr01.350ecermak.il.ibone.comcast.net[68.86.86.33]
12 60 ms 63 ms 63 ms he-1-15-0-0-cr01.denver.co.ibone.comcast.net [68.86.85.114]
13 59 ms 59 ms 60 ms xe-0-0-0-0-pe01.910fifteenth.co.ibone.comcast.net [68.86.84.18]
14 59 ms 59 ms 59 ms edge.xe1-comfluent.den.sharktech.net [70.39.96.225]
15 59 ms 105 ms 65 ms hackthissite.org [198.148.81.138]

Trace complete.

C:\WINDOWS\system32>
m
0
l
October 2, 2014 8:55:17 PM

It's alright for the late response.

The router doesn't seem to be the problem, provided it's being programmed properly (192.168.1.1).

It's either your ISP or your computer's network card.

Can you provide me with information regarding your network card?

I would also contact the ISP and see if they have any clue why the lag spikes occur.

Good luck! :) 
m
0
l
October 2, 2014 9:11:57 PM

Lately Time Warner has been utterly useless whether it is internet issues or Cable Digitization. Also what would you like to know about my network adapter?
m
0
l
October 2, 2014 9:15:21 PM

Realtek RTL8188CE Wireless LAN 802.11n PCI-E NIC
m
0
l
October 2, 2014 9:32:05 PM

would you just want me to post my sysinfo.NFO file to view instead of asking my hardware?
m
0
l
October 2, 2014 9:37:08 PM

Also how does high latency affect normal internet usage like email, YouTube, or netflix basically anything other than games?
m
0
l
a b 2 Internet access
a c 144 F Wireless
October 3, 2014 7:37:19 AM

Your issue is that you see very random and intermittent issues. It may or may not show up on the traceroutes depending on if you get lucky and there is no issues when you are running it.

Your best bet is to open multiple CMD windows. Then run continuous ping commands to the end machine causing the issue as well as the first 2 or 3 ip in the traceroute.

When you see issues errors in the ping to the end machine what you want to look for is if you see issues in the other pings at the same time and where they start.

If for example the problem was in the first hop that would be a issue between your machine and your router. It should cause issues on every hop beyond that point. The second hop represents the connection between your house and the ISP. This would generally be a cabling issue or something wrong with the wire in the street or something. Past this point it is in the ISP network but a ISP might be kind enough to check and see if they see something at that node.

I would strongly recommend you run on a wired connection for a period of time to verify it is not the wireless. Wireless causes very hard to find network issues so before you spend lots of time running lots of ping test you need to eliminate the wireless as the cause or you will be at this forever.
m
0
l
October 3, 2014 10:40:51 AM

I could only run powerline wired. Would that work for the test?
m
0
l
a b 2 Internet access
a c 144 F Wireless
October 3, 2014 10:43:33 AM

Its better than wireless and your would suspect if it shows exactly the same problem then it means the wireless is not the problem.
m
0
l
October 3, 2014 11:10:06 AM

Sad to but the ping spikes do occur going to the router. So now to see if it is my computers or the routers fault.
m
0
l
October 3, 2014 11:30:22 AM

My router runs at an average of 1ms and it jumps to 3000 in BF4
m
0
l

Best solution

a b 2 Internet access
a c 144 F Wireless
October 3, 2014 12:01:25 PM

Try to use another machine and ping the router and see if that machine also see a increase when you are seeing errors on your game machine. If it does not then it is something with the software on the pc causing issues. I have seen people say they change the video resolution settings and it magically fixes the ping times. Video resolution has nothing at all to do with the network delays but I have seen multiple people report this so there must be something. Not saying it is your issue it just that it can be pretty much anything when you are talking software on a machine causing issues.

If the problem occurs on a completely different machine then something is overloading the router. This one too is almost impossible to find because the router manufacture have few if any screens that let you see things like memory or cpu usage. In these cases it is best to try to load newer factory firmware or maybe try third party stuff like dd-wrt if your router supports it. Pretty much you are hoping to get lucky and whatever bug is causing your problem is not in other firmware.
Share
October 3, 2014 2:21:51 PM

I pinged my router from my computer and my Ipad at the same time while playing BF4. And yes they USUALLY spiked from 1ms to 3000ms together. So what does this mean...
m
0
l
a b 2 Internet access
a c 144 F Wireless
October 3, 2014 4:34:25 PM

means the router has a issue. All you can try to do is try different firmware. You of course want to disable any QoS or stuff but it tend to be almost impossible to guess when router act up.
m
0
l
October 5, 2014 8:42:10 PM

Qos is always off. Also linksys dropped support for my router completely. Sorry for the absence I wasnt home!
m
0
l
October 6, 2014 1:34:32 PM

I would suggest, if possible, to purchase a new good quality router and try if it's better.

Make sure 100% that you buy from a store that accepts returns on open merchandise, without charging a restocking fee or any kind of fee.

Routers are often sensitive, and you can never predict when they'll stop working.

Good luck! :) 
m
0
l
October 6, 2014 3:22:14 PM

any suggestions on routers preferably under $100. Also we have no AC devices so only N is needed. Lastly when in use we do have at least 15 devices connected if everyone is home.

When I was testing I was alone with 1-2 devices.
m
0
l
October 6, 2014 8:31:23 PM

Yet again thank you for your time!
m
0
l
October 7, 2014 6:16:56 AM

Can you hook up your computer directly to your internet (wired directly to the provided internet box ) and see if it eliminates the spikes ?
m
0
l
October 9, 2014 3:01:57 PM

No sadly I cannot do that.
m
0
l
October 15, 2014 9:03:17 PM

Yes I found out the router was the issue. I went out an bought an ASUS RT-AC56R router. Thank You for the time!

The old router was overloading.
m
0
l
October 16, 2014 9:19:17 PM

Congrats! :) 
m
0
l
!