I'm having a repeated issue that's been going on for about six months now and I can't seem to get anyone at Mediacom to actually believe me.
My downstream is fine, and the rated speed is great. Upstream is where I hit problems. This problem is always present, but gets worse towards evening (maybe 4PM-next morning).
While a speedtest shows a 20mbps upstream, it struggles to get up there and I'm seeing extreme variance in the ping as well as packet loss.
I have a 20MB ping log from last month using the free hrPING program (so I could timestamp the log), and here's an example of the results to Yahoo:
2017-09-01 16:14:44.311: From 98.138.253.109: bytes=60 seq=0388 TTL=45 ID=9670 time=78.055ms
2017-09-01 16:14:45.299: From 98.138.253.109: bytes=60 seq=0389 TTL=45 ID=bd8b time=66.894ms
2017-09-01 16:14:46.347: From 98.138.253.109: bytes=60 seq=038a TTL=45 ID=e648 time=115.072ms
2017-09-01 16:14:47.299: From 98.138.253.109: bytes=60 seq=038b TTL=45 ID=0ddb time=65.604ms
2017-09-01 16:14:48.421: From 98.138.253.109: bytes=60 seq=038c TTL=45 ID=3f90 time=188.895ms
2017-09-01 16:14:49.306: From 98.138.253.109: bytes=60 seq=038d TTL=45 ID=62d2 time=73.314ms
2017-09-01 16:14:50.299: From 98.138.253.109: bytes=60 seq=038e TTL=45 ID=8c5e time=66.802ms
2017-09-01 16:14:51.308: From 98.138.253.109: bytes=60 seq=038f TTL=45 ID=b42e time=75.337ms
2017-09-01 16:14:52.299: From 98.138.253.109: bytes=60 seq=0390 TTL=45 ID=d8b0 time=65.536ms
2017-09-01 16:14:53.367: From 98.138.253.109: bytes=60 seq=0391 TTL=45 ID=04c8 time=134.565ms
2017-09-01 16:14:54.299: From 98.138.253.109: bytes=60 seq=0392 TTL=45 ID=29ef time=66.324ms
2017-09-01 16:14:55.312: From 98.138.253.109: bytes=60 seq=0393 TTL=45 ID=5424 time=79.152ms
2017-09-01 16:14:56.302: From 98.138.253.109: bytes=60 seq=0394 TTL=45 ID=7b8b time=70.276ms
2017-09-01 16:14:57.315: From 98.138.253.109: bytes=60 seq=0395 TTL=45 ID=a1cc time=81.714ms
2017-09-01 16:14:58.315: From 98.138.253.109: bytes=60 seq=0396 TTL=45 ID=cb22 time=82.911ms
2017-09-01 16:14:59.299: From 98.138.253.109: bytes=60 seq=0397 TTL=45 ID=f5de time=66.201ms
2017-09-01 16:15:00.620: From 98.138.253.109: bytes=60 seq=0398 TTL=45 ID=3ece time=387.054ms
2017-09-01 16:15:01.298: From 98.138.253.109: bytes=60 seq=0399 TTL=45 ID=5cd2 time=66.436ms
2017-09-01 16:15:02.301: From 98.138.253.109: bytes=60 seq=039a TTL=45 ID=86ec time=68.527ms
2017-09-01 16:15:03.299: From 98.138.253.109: bytes=60 seq=039b TTL=45 ID=b0f7 time=67.010ms
2017-09-01 16:15:04.359: From 98.138.253.109: bytes=60 seq=039c TTL=45 ID=dd07 time=126.955ms
It spikes fairly frequently like this, and I've seen spikes as high as 1600ms. I've already been charged once for having a technician out because he insists there's nothing wrong with my connection. I can validate this result across multiple computers when hooked up either directly to the modem or my router.
The connection is almost unusable for anything more than basic browsing at night.
What do I need to do? I've been a fan of Mediacom's service for years, but this is making me want to switch to DSL in the hopes of stability!
Additional info:
Speed test: http://www.dslreports.com/speedtest/23176555
Line test (results not in at the time of posting): https://www.dslreports.com/testhistory/1960712/fb901
↧