CG3000Dv2 (N450) Massive lag spikes - Wired and wireless

[Neoteric]

Hello,

Could someone take a look at these ping reports and tell me what to do next? I tested both twc and yahoo, same results. I have a Netgear N450 Modem/router combo (firmware is up to date), I have Time Warner Cable, and this has been happening consistently for months. Possibly since I bought it. It happens every couple minutes, consistently, always. At first I assumed it was just a hiccup with my playstation 4's connection when playing online, but then I started pc gaming and realized how bad this was.

I don't know if this is hardware, time warner's end, etc. Any help would be much appreciated.

C:\Users\Jason>tracert twc.com

Tracing route to twc.com [71.74.189.86]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 29 ms 30 ms 15 ms cpe-67-247-216-1.buffalo.res.rr.com [67.247.216.1]
3 106 ms 21 ms 21 ms tge0-0-0.spvlnyxx02h.northeast.rr.com [98.0.0.89]
4 20 ms 26 ms 31 ms 24.58.38.190
5 12 ms 12 ms 11 ms agg34.lncsnycd02r.northeast.rr.com [24.58.38.176]
6 12 ms 15 ms 15 ms be29.rochnyei01r.northeast.rr.com [24.58.32.62]

7 26 ms 27 ms 32 ms bu-ether25.chcgildt87w-bcr00.tbone.rr.com [107.14.19.28]
8 57 ms 55 ms 55 ms bu-ether11.chctilwc00w-bcr00.tbone.rr.com [66.109.6.21]
9 50 ms 50 ms 50 ms bu-ether5.enwdcocd02w-bar01.tbone.rr.com [66.109.1.51]
10 49 ms 53 ms 50 ms 24.161.254.58
11 1718 ms 50 ms 56 ms 71.74.189.86
12 52 ms 50 ms 50 ms 71.74.189.86

Trace complete.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Jason>ping twc.com -t

Pinging twc.com [71.74.189.86] with 32 bytes of data ;
Reply from 206.190.36.45: bytes=32 time=93ms TTL=42
Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
Reply from 206.190.36.45: bytes=32 time=124ms TTL=42
Reply from 206.190.36.45: bytes=32 time=89ms TTL=42
Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
Reply from 206.190.36.45: bytes=32 time=89ms TTL=42
Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
Reply from 206.190.36.45: bytes=32 time=93ms TTL=42
Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
Reply from 206.190.36.45: bytes=32 time=93ms TTL=42
Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
Reply from 206.190.36.45: bytes=32 time=2452ms TTL=42
Reply from 206.190.36.45: bytes=32 time=104ms TTL=42
Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
Reply from 206.190.36.45: bytes=32 time=93ms TTL=42
Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
Reply from 206.190.36.45: bytes=32 time=89ms TTL=42
Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
Reply from 206.190.36.45: bytes=32 time=93ms TTL=42
Reply from 206.190.36.45: bytes=32 time=93ms TTL=42
Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
Reply from 206.190.36.45: bytes=32 time=93ms TTL=42
Reply from 206.190.36.45: bytes=32 time=93ms TTL=42
Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
Reply from 206.190.36.45: bytes=32 time=93ms TTL=42
Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
Reply from 206.190.36.45: bytes=32 time=93ms TTL=42
Reply from 206.190.36.45: bytes=32 time=104ms TTL=42
Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
Reply from 206.190.36.45: bytes=32 time=94ms TTL=42
Reply from 206.190.36.45: bytes=32 time=93ms TTL=42
Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
Reply from 206.190.36.45: bytes=32 time=93ms TTL=42
Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
Reply from 206.190.36.45: bytes=32 time=93ms TTL=42
Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
Reply from 206.190.36.45: bytes=32 time=93ms TTL=42
Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
Reply from 206.190.36.45: bytes=32 time=3870ms TTL=42
Reply from 206.190.36.45: bytes=32 time=100ms TTL=42
Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
Reply from 206.190.36.45: bytes=32 time=91ms TTL=42
Reply from 206.190.36.45: bytes=32 time=93ms TTL=42
Reply from 206.190.36.45: bytes=32 time=89ms TTL=42
Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
Reply from 206.190.36.45: bytes=32 time=90ms TTL=42
Reply from 206.190.36.45: bytes=32 time=93ms TTL=42
Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
Reply from 206.190.36.45: bytes=32 time=92ms TTL=42
Reply from 206.190.36.45: bytes=32 time=92ms TTL=42

Ping statistics for 206.190.36.45:
Packets: Sent = 98, Received = 98, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 89ms, Maximum = 3870ms, Average = 154ms

[Neoteric · Accepted solution]

Well, thanks to you and a bit of a lightbulb moment I figured it out. It was my PLEX media server. Apparently the DLNA settings can cause huge lag spikes. Who knew??? 

Thanks! Problem solved!

[TheEther]

Can you try running ping 67.247.216.1?  Do you still see the big spikes?

[Neoteric]

Sorry I didn't get back here sooner, yes same problem when I pinged 67.247.216.1.

Edit: I tried pinging my router, the address you suggested, and 4.2.2.2 and all had the spike simultaneously. Does that mean it's on my end?

[TheEther]

Yes, if you are seeing it with simultaneous pings to all 3 sites, where one of them is your router, then the problem is on your end.  Do you have QoS enabled on your router?  If yes, try disabling it.  Sometimes, QoS is more harmful than helpful.  What other features have you turned on in the router?

[Neoteric]

The only place I found a QoS option was for wireless multimedia, and I turned it off (didn't fixi t). I haven't messed with any of the default settings otherwise. 

[Neoteric · Accepted solution]

Well, thanks to you and a bit of a lightbulb moment I figured it out. It was my PLEX media server. Apparently the DLNA settings can cause huge lag spikes. Who knew??? 

Thanks! Problem solved!

[TheEther]

Great.  Go back and turn WMM back on.  Wireless speeds will be crippled without it.