Renton Wa Internet Speed Test?

I have had two tech visits to the house and they tell me everything is fine. The last tech insulted all my hardware but could not tell me how to fix the problem. He ran a speed test with my CM1000 modem and got 700mbps using his little Raspberry PI.  This issue I see is slow speed test (average 200mbps) and more importantly wildly random pings. The tech would only go by his speed test that showed and average of 30ms and sure if I run the speed test it will show a onetime ping of 19ms. But if you start a ping in a command window (ping -t www.comcast.net) you can watch how the pings bounce up and down like crazy. My neighbor has very flat pings. My friends around they area have very flat pings. (ping-test.net).

 

The real mystery is how is the tech getting 700mbps using my modem and my network cable on his little toy computer when every scale of computer device I have tried from my gamming monster desktop, work laptop, touch screen all in ones, to even a s9 cell phone with a usb gig adapter only shows half that speed at best.

It is true you can't get gig speeds out of a 100Mb NIC card or like my brother who had computers so old they had IDE drives in them..... the "pipe" needs to have the “capacity“ and the “pump” needs to be able to generate enough “pressure”. All my network connections are GIG LAN and I have tested the throughput of my home network at GIG speeds. 

 

I am still seeing my pings jump up and down but my neighbors are flat (as they should be)

 

Tested my modem on my neighbor line (no change)

Replaced my Modem (no change)

Tech came out and replaced my drop and sees the issue at the poll (no change)

Use Comcast modem (no change)

Reduced my plan down to 100Mbps because that is all I can get. (no change)

 

ping -t speedtest.xfinity.com

 

Pinging cdn.speedtest-prod.xcr.comcast.net [69.241.76.106] with 32 bytes of data:

Reply from 69.241.76.106: bytes=32 time=81ms TTL=56

Reply from 69.241.76.106: bytes=32 time=86ms TTL=56

Reply from 69.241.76.106: bytes=32 time=117ms TTL=56

Reply from 69.241.76.106: bytes=32 time=33ms TTL=56

Reply from 69.241.76.106: bytes=32 time=153ms TTL=56

Request timed out.

Reply from 69.241.76.106: bytes=32 time=218ms TTL=56

Reply from 69.241.76.106: bytes=32 time=236ms TTL=56

Reply from 69.241.76.106: bytes=32 time=36ms TTL=56

Reply from 69.241.76.106: bytes=32 time=80ms TTL=56

Reply from 69.241.76.106: bytes=32 time=215ms TTL=56

Reply from 69.241.76.106: bytes=32 time=121ms TTL=56

Reply from 69.241.76.106: bytes=32 time=76ms TTL=56

Reply from 69.241.76.106: bytes=32 time=110ms TTL=56

Reply from 69.241.76.106: bytes=32 time=21ms TTL=56

Reply from 69.241.76.106: bytes=32 time=47ms TTL=56

Reply from 69.241.76.106: bytes=32 time=195ms TTL=56

Request timed out.

Reply from 69.241.76.106: bytes=32 time=236ms TTL=56

Reply from 69.241.76.106: bytes=32 time=95ms TTL=56

Reply from 69.241.76.106: bytes=32 time=49ms TTL=56

 

Ping statistics for 69.241.76.106:

    Packets: Sent = 21, Received = 19, Lost = 2 (9% loss),

Approximate round trip times in milli-seconds:

    Minimum = 21ms, Maximum = 236ms, Average = 116ms