for the last week or so since I started to take notice I've been experiencing sudden, short lasting (a couple seconds) lag spikes and noticable trace route fails to google.com. It's a bizarre problem because 99% of the time my speed tests are fine, normal download, normal upload. I stream a lot of video like Twitch or You tube and notice nothing major.
The problem comes from online gaming where a steady and quick connection is required (such as Call of Duty, Battlefield, Counter Strike) I run two monitors so I'm able to run the ping cmd and monitor the spikes which also translate into "rubberbanding" in the game. Now its never long enough to be disconnected for timeouts or anything like that, just a sudden burst of a lag spike which will occasionaly time out in cmd prompt, but is usually indicated by a jump in milliseconds from 125 up to 500 ms return time.
I have a very standard setup, mediacom modem into a TP Link router, one desktop and one laptop. I've cycled the power on everything, enabled defaults on my router. I've tried hooking directly from the modem into both PC's, both do the same thing. Both PCs will also show the spike at the same time so its not a pc hardware issue.
Modem is a Technicolor (provided by Mediacom tech)Model TC8715. I've always been a fan of the Thompson modems but was told he didn't have any available.
I'm also unable to log in to my modem and report the signals. It asks for a login and leaving it blank does not work.
https://www.dslreports.com/testhistory/1873647/f92b2 for the line test which again, shows ok I suppose.
Both Pcs are running windows 10 with the latest updates.
This problem happens at all times and naturally gets worse around "peak times"
I've messaged Chad a few days ago and didn't receive any reply yet (i know hes busy) so im posting to see if anyone else is experiencing a similar issue.
Here is an example of what I'm seeing running a ping test.
Note: There are no downloads or background applications running any updates.
Reply from 172.217.1.132: bytes=32 time=36ms TTL=53
Reply from 172.217.1.132: bytes=32 time=34ms TTL=53
Reply from 172.217.1.132: bytes=32 time=44ms TTL=53
Reply from 172.217.1.132: bytes=32 time=64ms TTL=53
Reply from 172.217.1.132: bytes=32 time=34ms TTL=53
Reply from 172.217.1.132: bytes=32 time=38ms TTL=53
Reply from 172.217.1.132: bytes=32 time=41ms TTL=53
Reply from 172.217.1.132: bytes=32 time=47ms TTL=53
Reply from 172.217.1.132: bytes=32 time=39ms TTL=53
Reply from 172.217.1.132: bytes=32 time=35ms TTL=53
Reply from 172.217.1.132: bytes=32 time=57ms TTL=53
Reply from 172.217.1.132: bytes=32 time=46ms TTL=53
Reply from 172.217.1.132: bytes=32 time=73ms TTL=53
Reply from 172.217.1.132: bytes=32 time=45ms TTL=53
Reply from 172.217.1.132: bytes=32 time=100ms TTL=53
Reply from 172.217.1.132: bytes=32 time=141ms TTL=53
Reply from 172.217.1.132: bytes=32 time=58ms TTL=53
Reply from 172.217.1.132: bytes=32 time=212ms TTL=53
Request timed out.
Reply from 172.217.1.132: bytes=32 time=62ms TTL=53
Reply from 172.217.1.132: bytes=32 time=56ms TTL=53
Reply from 172.217.1.132: bytes=32 time=68ms TTL=53
Reply from 172.217.1.132: bytes=32 time=36ms TTL=53
Reply from 172.217.1.132: bytes=32 time=38ms TTL=53
Reply from 172.217.1.132: bytes=32 time=60ms TTL=53
↧