Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

Question

My computer is the only one with PING SPIKES!

Mar 12, 2017 3:01PM PDT

Some months ago I got some ping issues with my computer and i assumed it was because of my USB adapter.

I bought a new ASUS network card with big antennas and there is literally no difference whatsoever. My friend can bring his laptop and he will have 1-3 ping with no interuption, but I will get these 100+ ping connection to servers and sudden lagspikes.

I have scanned my pc with Malware bytes and multiple other programs, but they didnt show anything.
I have also reset my network settings but it didnt help.

I have Windows 10 and I dont know if its a program running in the background or if God doesnt like me, but I seriously have zero clue what the problem may be.

I pinged google.com and it showed exactly what I mean with the lag spikes, but the only thing it doesnt show is that I always have 100ms.

Reply from 216.58.209.142: bytes=32 time=1684ms TTL=55
Reply from 216.58.209.142: bytes=32 time=11ms TTL=55
Reply from 216.58.209.142: bytes=32 time=1081ms TTL=55
Reply from 216.58.209.142: bytes=32 time=11ms TTL=55
Reply from 216.58.209.142: bytes=32 time=11ms TTL=55
Reply from 216.58.209.142: bytes=32 time=12ms TTL=55
Reply from 216.58.209.142: bytes=32 time=11ms TTL=55
Reply from 216.58.209.142: bytes=32 time=11ms TTL=55
Reply from 216.58.209.142: bytes=32 time=11ms TTL=55
Reply from 216.58.209.142: bytes=32 time=11ms TTL=55
Reply from 216.58.209.142: bytes=32 time=11ms TTL=55
Reply from 216.58.209.142: bytes=32 time=11ms TTL=55
Reply from 216.58.209.142: bytes=32 time=11ms TTL=55
Reply from 216.58.209.142: bytes=32 time=11ms TTL=55
Reply from 216.58.209.142: bytes=32 time=84ms TTL=55
Reply from 216.58.209.142: bytes=32 time=11ms TTL=55
Reply from 216.58.209.142: bytes=32 time=11ms TTL=55
Reply from 216.58.209.142: bytes=32 time=12ms TTL=55
Reply from 216.58.209.142: bytes=32 time=11ms TTL=55
Reply from 216.58.209.142: bytes=32 time=11ms TTL=55
Reply from 216.58.209.142: bytes=32 time=11ms TTL=55
Reply from 216.58.209.142: bytes=32 time=11ms TTL=55
Reply from 216.58.209.142: bytes=32 time=11ms TTL=55
Reply from 216.58.209.142: bytes=32 time=11ms TTL=55
Reply from 216.58.209.142: bytes=32 time=14ms TTL=55
Reply from 216.58.209.142: bytes=32 time=11ms TTL=55
Reply from 216.58.209.142: bytes=32 time=78ms TTL=55
Reply from 216.58.209.142: bytes=32 time=11ms TTL=55
Reply from 216.58.209.142: bytes=32 time=11ms TTL=55
Reply from 216.58.209.142: bytes=32 time=11ms TTL=55
Reply from 216.58.209.142: bytes=32 time=11ms TTL=55
Reply from 216.58.209.142: bytes=32 time=11ms TTL=55
Reply from 216.58.209.142: bytes=32 time=13ms TTL=55
Reply from 216.58.209.142: bytes=32 time=12ms TTL=55
Reply from 216.58.209.142: bytes=32 time=11ms TTL=55
Reply from 216.58.209.142: bytes=32 time=11ms TTL=55
Reply from 216.58.209.142: bytes=32 time=11ms TTL=55
Reply from 216.58.209.142: bytes=32 time=11ms TTL=55
Reply from 216.58.209.142: bytes=32 time=62ms TTL=55
Reply from 216.58.209.142: bytes=32 time=123ms TTL=55
Reply from 216.58.209.142: bytes=32 time=11ms TTL=55

Discussion is locked

- Collapse -
Clarification Request
Now test it wired.
Mar 12, 2017 3:04PM PDT

That's the only way to see if it's the usual.

Remember, due to how WiFi works, ONLY IN A LAB will it be perfect. Also, ONLY IN A LAB where the server is not over the internet.

- Collapse -
Not to leave you without hope.
Mar 12, 2017 3:30PM PDT

Be sure to keep the router in line of sight at 3 meters. DO NOT SHARE WIFI during the test and shut down all other connections within 33 meters.

Now configure the router's WiFi to match your client device. If your PC's WiFi is 802.11 with a 20MHz channel, then be sure it's same on the router. Also, check channels on the router. If 1 or over 11, check region setting or hard set it to 6 and re-test.