| [HSI] Connection is weak/unstable I'm having an issue with my connection staying... well connected. It doesn't shut down itself, but I guess its too weak to hold the game up. It started on Sunday 01/22/2012 at 5:00pm CST.
I play LoL, WoW, and SWTOR and I started getting HUGE lag, latency spikes and DC. I can still surf the internet but I keep getting kicked from the game server or map while I'm playing. There are some DCs from the internet where the computer diagnostics says there was an issue with the DNS. The speed is fine but the connection drops every minute or two. It makes gaming impossible.
I have a Motorola SURFboard SB6121. All of the lights are green except the receive light and the link light. The link light is a stable orange and the receive light is a stable blue light. The Motorola is a new modem that I just got on 01/26/2012. I used to have the Ubee D 3.0. On that one the Downstream light was orange and all the other lights were green.
I have also bypassed the Netgear router and got the same results so I know that's not the issue.
I have Charter Cable Internet, I called them up and all they tell me is to power-cycle the modem and whatnot. I've reset the modem a million times and cant listen to the same stuff over and over. They say there is nothing wrong with the service and there are no outages in the area.
I just want to know if it's on my end or theirs. If its on mine I'd like to know how to fix it.
»www.speedtest.net/result/1733489004.png
»www.pingtest.net/result/55513624.png
»www.pingtest.net/result/55513680.png
»www.pingtest.net/result/55513720.png
I can do a traceroute if you need as well. |
|
 BF69Premium
join:2004-07-28
Camden, TN | your pings aren't that bad. I get 35 ms on a good day, typically around 45 ms. |
|
| Here is a ping traceroute. I hope this helps.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Tom>ping google.com -t
Pinging google.com [74.125.225.18] with 32 bytes of data:
Reply from 74.125.225.18: bytes=32 time=18ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=16ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=16ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=16ms TTL=55
Reply from 74.125.225.18: bytes=32 time=16ms TTL=55
Reply from 74.125.225.18: bytes=32 time=16ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=16ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=22ms TTL=55
Reply from 74.125.225.18: bytes=32 time=18ms TTL=55
Reply from 74.125.225.18: bytes=32 time=16ms TTL=55
Reply from 74.125.225.18: bytes=32 time=16ms TTL=55
Reply from 74.125.225.18: bytes=32 time=18ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=18ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=19ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Request timed out.
Request timed out.
Request timed out.
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=16ms TTL=55
Reply from 74.125.225.18: bytes=32 time=16ms TTL=55
Reply from 74.125.225.18: bytes=32 time=18ms TTL=55
Reply from 74.125.225.18: bytes=32 time=23ms TTL=55
Reply from 74.125.225.18: bytes=32 time=15ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=19ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=16ms TTL=55
Reply from 74.125.225.18: bytes=32 time=16ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=16ms TTL=55
Reply from 74.125.225.18: bytes=32 time=16ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=15ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=18ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=16ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=20ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=15ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=16ms TTL=55
Reply from 74.125.225.18: bytes=32 time=16ms TTL=55
Reply from 74.125.225.18: bytes=32 time=16ms TTL=55
Reply from 74.125.225.18: bytes=32 time=20ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=20ms TTL=55
Reply from 74.125.225.18: bytes=32 time=16ms TTL=55
Reply from 74.125.225.18: bytes=32 time=20ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=18ms TTL=55
Reply from 74.125.225.18: bytes=32 time=15ms TTL=55
Reply from 74.125.225.18: bytes=32 time=16ms TTL=55
Reply from 74.125.225.18: bytes=32 time=16ms TTL=55
Reply from 74.125.225.18: bytes=32 time=15ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=16ms TTL=55
Reply from 74.125.225.18: bytes=32 time=19ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=21ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=16ms TTL=55
Reply from 74.125.225.18: bytes=32 time=16ms TTL=55
Reply from 74.125.225.18: bytes=32 time=16ms TTL=55
Reply from 74.125.225.18: bytes=32 time=16ms TTL=55
Reply from 74.125.225.18: bytes=32 time=16ms TTL=55
Reply from 74.125.225.18: bytes=32 time=16ms TTL=55
Reply from 74.125.225.18: bytes=32 time=16ms TTL=55
Request timed out.
Reply from 74.125.225.18: bytes=32 time=18ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=18ms TTL=55
Request timed out.
Request timed out.
Request timed out.
Reply from 74.125.225.18: bytes=32 time=16ms TTL=55
Reply from 74.125.225.18: bytes=32 time=24ms TTL=55
Reply from 74.125.225.18: bytes=32 time=19ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=19ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=16ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Request timed out.
Reply from 74.125.225.18: bytes=32 time=21ms TTL=55
Reply from 74.125.225.18: bytes=32 time=20ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Request timed out.
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=18ms TTL=55
Reply from 74.125.225.18: bytes=32 time=16ms TTL=55
Reply from 74.125.225.18: bytes=32 time=18ms TTL=55
Reply from 74.125.225.18: bytes=32 time=16ms TTL=55
Reply from 74.125.225.18: bytes=32 time=20ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Reply from 74.125.225.18: bytes=32 time=17ms TTL=55
Ping statistics for 74.125.225.18:
Packets: Sent = 134, Received = 125, Lost = 9 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 24ms, Average = 17ms
Control-C
^C
C:\Users\Tom> |
|
 DoggPremium
join:2003-06-11
Belleville, IL
 ·Charter
| reply to Tom1232
Definetly an issue there. Have you created a topic in Charter Direct?
>>> » Charter Direct
--
Google is your Friend |
|
| I don't have a premium account. It wont let me post there.  |
|
bdnhsv
join:2012-01-20
Huntsville, AL | 6% packet loss is significant. It could be caused by a number of things. You'll need to get past the Tier1 helpdesk type people and speak with some T2 or 3 engineers to get to the root of this problem I suspect. |
|
| Yeah, I'm not sure how to do that though. The last time I talked to somebody they gave me that "Service Maintenance" deal that should only take a couple hours... 6 days ago. lol |
|
bdnhsv
join:2012-01-20
Huntsville, AL | Have you tried their direct forum on here? Have you asked for the tech-ops mgr in your local town? Have you threatened to disconnect if they didn't connect you with an engineer? Have you gone to your local office and demanded to speak with an engineer? etc, etc... |
|
| reply to Tom1232
If I were a gambling man, Id put my money on noise being your problem |
|
| reply to Tom1232
I recently bought the charter highspeed wirless service too. ever since i switched to that instead of my mobile hotspot... i get these short but frequent bursts of lag on my WoW. if anyone knows how to fix let us know  |
|
|
|
| reply to Tom1232
I have had intermittent drops for the past 2 months.
For years, I have had the best stable Charter internet and then my area got hit hard with winds in Southern California. My problems started soon after.
Sometimes (more often in the day), my internet also intermittently drops for a minute or less and then comes back online. I have had a technician come out about 4 times, and changed my modem to the netgear docsis 3.0 but the problem is still there. They have put in amplifiers as well because the signal used to be spiking.
They were originally noticing drops which is why they sent technicians/supervisors. It seemed to work for a few days. Then, the problem happened again but this time they said the connection going to my modem was fine. Google Chrome says I have DNS issues. My modem lights don't cycle on/off like they used to, but the online blinking light changes. Ethernet light sometimes stays solid amber instead of blinking. Online green light sometimes blinks instead of stay stable. Router lights seem stable. I reset both my Netgear router and modem and it works again...
Will post more info if problems persist. Last Charter rep said it was my router. |
|
