Moderately unstable powerline Ethernet connection

[Multirotor]

Hi, I am experiencing a ridiculous amount of lag spikes on a normal basis during gaming sessions. Happens on multiple games.

Connection = powerline ethernet set up in a very nice, relatively new house (2004)
Router = Cisco DPC3825
Service = Midcontinent Communications
City = Forest Lake, Minnesota

Here is what happens when I ping my router:
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=30ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64

I ping 8.8.8.8 (I am currently using Google DNS in my Windows settings):
Reply from 8.8.8.8: bytes=32 time=61ms TTL=57
Reply from 8.8.8.8: bytes=32 time=61ms TTL=57
Reply from 8.8.8.8: bytes=32 time=62ms TTL=57
Reply from 8.8.8.8: bytes=32 time=78ms TTL=57
Reply from 8.8.8.8: bytes=32 time=75ms TTL=57
Reply from 8.8.8.8: bytes=32 time=61ms TTL=57
Reply from 8.8.8.8: bytes=32 time=80ms TTL=57
Reply from 8.8.8.8: bytes=32 time=63ms TTL=57
Reply from 8.8.8.8: bytes=32 time=90ms TTL=57
Reply from 8.8.8.8: bytes=32 time=60ms TTL=57
Reply from 8.8.8.8: bytes=32 time=61ms TTL=57
Reply from 8.8.8.8: bytes=32 time=61ms TTL=57
Reply from 8.8.8.8: bytes=32 time=61ms TTL=57
Reply from 8.8.8.8: bytes=32 time=63ms TTL=57
Reply from 8.8.8.8: bytes=32 time=61ms TTL=57
Reply from 8.8.8.8: bytes=32 time=69ms TTL=57
Reply from 8.8.8.8: bytes=32 time=62ms TTL=57
Reply from 8.8.8.8: bytes=32 time=61ms TTL=57

I do a tracert to google.com: (Looks different this time... usually it is pretty normal)

Tracing route to google.com [2607:f8b0:4009:816::200e]
over a maximum of 30 hops:

1 4 ms 3 ms 3 ms 2001-48F8-704E-1198-1A59-33FF-FEF7-B2F3-dynamic.midco.net [2001:48f8:704e:1198:1a59:33ff:fef7:b2f3]
2 * * * Request timed out.
3 13 ms 13 ms 13 ms 2001-48F8-7000-0-0-0-0-1D8-static.midco.net [2001:48f8:7000::1d8]
4 17 ms 28 ms 13 ms 2001-48F8-7000-1-0-0-0-6-static.midco.net [2001:48f8:7000:1::6]
5 26 ms 31 ms 22 ms 2001-48F8-0-1-0-0-0-4C-static.midco.net [2001:48f8:0:1::4c]
6 47 ms 27 ms 23 ms 2001-48F8-0-0-0-0-0-4A-static.midco.net [2001:48f8::4a]
7 100 ms 80 ms 237 ms pr61.iad07.net.google.com [2001:504:0:2:0:1:5169:1]
8 78 ms 107 ms 66 ms 2001:4860:0:eaf::3
9 69 ms 65 ms 61 ms 2001:4860::c:4000:da1a
10 65 ms 64 ms 64 ms 2001:4860::c:4000:d5ff
11 62 ms 63 ms 63 ms 2001:4860::1:4000:d31c
12 * * * Request timed out.
13 60 ms 79 ms 62 ms 2001:4860:0:1::2169
14 80 ms 64 ms 63 ms ord38s09-in-x0e.1e100.net [2607:f8b0:4009:816::200e]

Specs:
ASUS G11CD-US009T Pre-built desktop computer
Intel i5-6400 quad core
GTX 960 2GB
8GB DDR4-2133 RAM
150-ish GB hybrid drive
1TB HDD
Windows 10 Home 64-Bit

Please help me with these issues, I suspect it is something with my Netgear Powerline 1000 (PL1000) but I'm not completely sure.
Thanks in advance.
>rotor

 

[dshort01]

I had considered a powerline network at one time for my daughters house. However, the reviews were very mixed. When I ping my gateway it is always 1 ms in comparison so the powerline network if definitely using overhead. Pinging 8.8.8.8 is is consistently 11 to 13 ms. I would try plugging directly into your modem directly to compare. That should definitely tell you whether it is your service provider, your powerline network or a combination of both. You should be able to isolate the problem that way.

 

[dshort01]

BTW.... I am not using powerline. But a wired network except for my phones and Alexa