tok3r
join:2009-09-21
Montgomery, AL
1 edit | Need help getting Knology to fix internet.
As you guys know Knology has been sucking as of late. I'm in the Montgomery AL area and it's slow as hell. I don't understand why there isn't more people complaining to Knology, so they can fix this already. They're probably still running on docsis 1.0 in my area I believe, some are running on docsis 1.1.
Somebody from Knology needs to read this.
Trouble Shooting Slow Performance In Cable Modem Network
»www.cisco.com/en/US/tech/tk86/tk···3c.shtml
See I don't want them to send tech after tech to my house. It's really annoying, and the problem isn't on my end. If I was a network technician, I would go down to Knology and fix this my damn self, but I'm not. Obviously they have technicians that don't know a damn thing or it would've been fixed by now.
What I want to know is... what can I do to help Knology fix this internet issue. Can I do some test here at my place? Send them the link to the line quality test here at dslreports.com? Maybe that tracert result? I really don't want to go back to Charter. I really don't mind the slow bandwidth either, its the slow page load and packet lost that I'm getting. It's ridiculous.... Which corporate cock do I have to suck to get something fixed!
Here's my line test result.
»/linequality/nil/2567635
What is this hop thing? Are those nodes or hub? It seems to me that hop number 16 and 17 is what they need to fix. Can someone clarify this?
Anybody that can help me, help Knology, please do so, and we can all be happy 
Thanks for reading. |
|
zpm
join:2009-03-23
Columbus, GA
 ·Knology
1 edit | run a tracert in command prompt of windows or whatever os you uses...
do a tracert to yahoo, cnn, and knology.
then copy and paste those results here..
too me, in my experience, 2-3 things cause my lag... RF tilt, node congestion, CMTS integration and adjustments.
node congestion or RF tilt maybe the cause of your troubles. |
|
tok3r
join:2009-09-21
Montgomery, AL
| reply to tok3r
Tracing route to www-real.wa1.b.yahoo.com [209.191.93.52]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 10.0.0.1
2 13 ms 9 ms 18 ms static-24-214-178-197.knology.net [24.214.178.19
7]
3 11 ms 27 ms 11 ms dynamic-76-73-147-45.knology.net [76.73.147.45]
4 23 ms * 12 ms dynamic-76-73-163-21.knology.net [76.73.163.21]
5 16 ms 18 ms 9 ms dynamic-76-73-163-17.knology.net [76.73.163.17]
6 11 ms 10 ms 10 ms dynamic-76-73-163-13.knology.net [76.73.163.13]
7 12 ms 21 ms 14 ms dynamic-76-73-163-5.knology.net [76.73.163.5]
8 31 ms 9 ms 11 ms dynamic-76-73-163-1.knology.net [76.73.163.1]
9 23 ms 10 ms 10 ms user-24-96-198-97.knology.net [24.96.198.97]
10 38 ms * 22 ms ge.1-3-1.cr-Atla.GA.US.knology.net [24.214.0.237
]
11 * 37 ms * ge.0-0-0.ar-Atla.GA.US.knology.net [24.214.0.54]
12 55 ms 73 ms 77 ms dynamic-76-73-147-202.knology.net [76.73.147.202
]
13 66 ms 78 ms * dynamic-76-73-147-222.knology.net [76.73.147.222
]
14 74 ms 69 ms 69 ms static-10.64-179-190.iw.net [64.179.190.10]
15 81 ms 68 ms 66 ms sxf-edge-02.inet.qwest.net [65.125.42.5]
16 79 ms 71 ms 68 ms sxf-core-02.inet.qwest.net [205.171.162.21]
17 66 ms 64 ms 83 ms min-core-01.inet.qwest.net [205.171.8.94]
18 * 70 ms 99 ms chp-brdr-03.inet.qwest.net [67.14.8.194]
19 68 ms 70 ms 72 ms 63.146.26.250
20 * 89 ms 89 ms Vlan5.icore2.DTX-Dallas.as6453.net [206.82.141.3
0]
21 83 ms 83 ms 85 ms if-1-0-0-32.core2.DTX-Dallas.as6453.net [206.82.
142.10]
22 90 ms 79 ms 81 ms ix-4-1.core2.DTX-Dallas.as6453.net [66.198.2.10]
23 82 ms 81 ms 79 ms ae1-p110.msr2.mud.yahoo.com [216.115.104.101]
24 93 ms 79 ms * te-8-1.bas-c2.mud.yahoo.com [68.142.193.7]
25 82 ms 79 ms 89 ms f1.www.vip.mud.yahoo.com [209.191.93.52]
Trace complete. |
|
tok3r
join:2009-09-21
Montgomery, AL
| tracert www.cnn.com
Tracing route to www.cnn.com [157.166.226.25]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 10.0.0.1
2 13 ms 13 ms 8 ms static-24-214-178-197.knology.net [24.214.178.19
7]
3 * * 15 ms dynamic-76-73-147-45.knology.net [76.73.147.45]
4 11 ms 30 ms 21 ms dynamic-76-73-163-21.knology.net [76.73.163.21]
5 * 12 ms 10 ms dynamic-76-73-163-17.knology.net [76.73.163.17]
6 21 ms 10 ms 11 ms dynamic-76-73-163-13.knology.net [76.73.163.13]
7 11 ms 13 ms * dynamic-76-73-163-5.knology.net [76.73.163.5]
8 11 ms 12 ms 10 ms dynamic-76-73-163-1.knology.net [76.73.163.1]
9 16 ms * 10 ms user-24-96-198-97.knology.net [24.96.198.97]
10 32 ms 31 ms * ge.2-3-1.cr-Atla.GA.US.knology.net [24.214.0.217
]
11 26 ms 27 ms 24 ms GigabitEthernet1-0.GW3.ATL4.ALTER.NET [157.130.7
0.253]
12 * * 30 ms 0.so-1-0-3.XT1.ATL4.ALTER.NET [152.63.87.114]
13 26 ms 29 ms * 0.so-6-0-0.BR1.ATL4.ALTER.NET [152.63.86.169]
14 32 ms 32 ms 27 ms 204.255.169.78
15 25 ms 25 ms 56 ms bb1-atm-p4-0.atdn.net [66.185.147.208]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete. |
|
tok3r
join:2009-09-21
Montgomery, AL
| tracert www.knology.net
Tracing route to www.knology.net [64.29.151.81]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 10.0.0.1
2 19 ms 14 ms 58 ms static-24-214-178-197.knology.net [24.214.178.19
7]
3 11 ms 17 ms 9 ms dynamic-76-73-147-45.knology.net [76.73.147.45]
4 10 ms 9 ms * dynamic-76-73-163-21.knology.net [76.73.163.21]
5 17 ms 13 ms 14 ms dynamic-76-73-163-17.knology.net [76.73.163.17]
6 16 ms 16 ms 14 ms dynamic-76-73-163-13.knology.net [76.73.163.13]
7 23 ms 15 ms 13 ms dynamic-76-73-163-5.knology.net [76.73.163.5]
8 10 ms 19 ms 12 ms dynamic-76-73-163-1.knology.net [76.73.163.1]
9 13 ms 18 ms 16 ms user-24-96-198-97.knology.net [24.96.198.97]
10 40 ms * 25 ms ge.1-3-1.cr-Atla.GA.US.knology.net [24.214.0.237
]
11 23 ms 23 ms 22 ms 12.90.35.5
12 43 ms 41 ms 67 ms cr82.attga.ip.att.net [12.122.117.90]
13 42 ms * 47 ms cr2.attga.ip.att.net [12.123.87.73]
14 * 41 ms 39 ms cr1.ormfl.ip.att.net [12.122.31.30]
15 46 ms 41 ms 42 ms gar2.miufl.ip.att.net [12.122.143.41]
16 * 12.116.154.46 reports: Destination net unreachable.
Trace complete.
Thanks a lot... |
|
zpm
join:2009-03-23
Columbus, GA
·Knology
1 edit | you've definitely got a packet problem, your losing a ton,
2 19 ms 14 ms 58 ms....
the problem maybe the local box, and or modem.... is their any particular time it does this odd behavior, and are you losing 2 mbps or more?
do
ping support.knology.net -t in cmd.
let it run for about 5-10 minutes at night, and if you see, low pings and pings of 40+ then their is an issue somewhere on the lines... maybe junction dis-function or modem/node troubles. |
|
tok3r
join:2009-09-21
Montgomery, AL
| It's like this all the time... it doesnt matter the time of day or weather condition... I wish there was a third company that i can get internet from. I'd be happy with 3mpbs..
They can switch the modem if they want.. I dont think it's that though.
here's the ping result
12:21AM
eply from 69.73.108.20: bytes=32 time=31ms TTL=50
Reply from 69.73.108.20: bytes=32 time=32ms TTL=50
Reply from 69.73.108.20: bytes=32 time=28ms TTL=50
Reply from 69.73.108.20: bytes=32 time=33ms TTL=50
Reply from 69.73.108.20: bytes=32 time=33ms TTL=50
Request timed out.
Reply from 69.73.108.20: bytes=32 time=30ms TTL=50
Request timed out.
Reply from 69.73.108.20: bytes=32 time=30ms TTL=50
Reply from 69.73.108.20: bytes=32 time=29ms TTL=50
Reply from 69.73.108.20: bytes=32 time=33ms TTL=50
Reply from 69.73.108.20: bytes=32 time=28ms TTL=50
Reply from 69.73.108.20: bytes=32 time=30ms TTL=50
Reply from 69.73.108.20: bytes=32 time=34ms TTL=50
Reply from 69.73.108.20: bytes=32 time=34ms TTL=50
Reply from 69.73.108.20: bytes=32 time=34ms TTL=50
Reply from 69.73.108.20: bytes=32 time=51ms TTL=50
Reply from 69.73.108.20: bytes=32 time=30ms TTL=50
Reply from 69.73.108.20: bytes=32 time=31ms TTL=50
Reply from 69.73.108.20: bytes=32 time=37ms TTL=50
Reply from 69.73.108.20: bytes=32 time=31ms TTL=50
Reply from 69.73.108.20: bytes=32 time=33ms TTL=50
Reply from 69.73.108.20: bytes=32 time=31ms TTL=50
Request timed out.
Reply from 69.73.108.20: bytes=32 time=34ms TTL=50
Reply from 69.73.108.20: bytes=32 time=30ms TTL=50
Reply from 69.73.108.20: bytes=32 time=32ms TTL=50
Reply from 69.73.108.20: bytes=32 time=29ms TTL=50
Reply from 69.73.108.20: bytes=32 time=29ms TTL=50
Reply from 69.73.108.20: bytes=32 time=33ms TTL=50
Reply from 69.73.108.20: bytes=32 time=37ms TTL=50
Reply from 69.73.108.20: bytes=32 time=32ms TTL=50
Reply from 69.73.108.20: bytes=32 time=37ms TTL=50
Reply from 69.73.108.20: bytes=32 time=31ms TTL=50
Request timed out.
Reply from 69.73.108.20: bytes=32 time=29ms TTL=50
Reply from 69.73.108.20: bytes=32 time=33ms TTL=50
Reply from 69.73.108.20: bytes=32 time=35ms TTL=50
Reply from 69.73.108.20: bytes=32 time=31ms TTL=50
Reply from 69.73.108.20: bytes=32 time=34ms TTL=50
Reply from 69.73.108.20: bytes=32 time=30ms TTL=50
Reply from 69.73.108.20: bytes=32 time=32ms TTL=50
Request timed out.
Reply from 69.73.108.20: bytes=32 time=35ms TTL=50
Reply from 69.73.108.20: bytes=32 time=32ms TTL=50
Reply from 69.73.108.20: bytes=32 time=33ms TTL=50
Reply from 69.73.108.20: bytes=32 time=30ms TTL=50
Reply from 69.73.108.20: bytes=32 time=33ms TTL=50
Request timed out.
Reply from 69.73.108.20: bytes=32 time=32ms TTL=50
Reply from 69.73.108.20: bytes=32 time=33ms TTL=50
Reply from 69.73.108.20: bytes=32 time=33ms TTL=50
Reply from 69.73.108.20: bytes=32 time=32ms TTL=50
Reply from 69.73.108.20: bytes=32 time=33ms TTL=50
Reply from 69.73.108.20: bytes=32 time=29ms TTL=50
Reply from 69.73.108.20: bytes=32 time=34ms TTL=50
Reply from 69.73.108.20: bytes=32 time=44ms TTL=50
Reply from 69.73.108.20: bytes=32 time=33ms TTL=50
Reply from 69.73.108.20: bytes=32 time=32ms TTL=50
Reply from 69.73.108.20: bytes=32 time=30ms TTL=50
Reply from 69.73.108.20: bytes=32 time=33ms TTL=50
Reply from 69.73.108.20: bytes=32 time=36ms TTL=50
Reply from 69.73.108.20: bytes=32 time=32ms TTL=50
Reply from 69.73.108.20: bytes=32 time=33ms TTL=50
Reply from 69.73.108.20: bytes=32 time=33ms TTL=50
Reply from 69.73.108.20: bytes=32 time=30ms TTL=50
Request timed out.
Reply from 69.73.108.20: bytes=32 time=55ms TTL=50
Reply from 69.73.108.20: bytes=32 time=29ms TTL=50
Reply from 69.73.108.20: bytes=32 time=33ms TTL=50
Reply from 69.73.108.20: bytes=32 time=28ms TTL=50
Reply from 69.73.108.20: bytes=32 time=32ms TTL=50
Request timed out.
Reply from 69.73.108.20: bytes=32 time=30ms TTL=50
Reply from 69.73.108.20: bytes=32 time=37ms TTL=50
Reply from 69.73.108.20: bytes=32 time=32ms TTL=50
Reply from 69.73.108.20: bytes=32 time=33ms TTL=50
Reply from 69.73.108.20: bytes=32 time=31ms TTL=50
Reply from 69.73.108.20: bytes=32 time=33ms TTL=50
Request timed out.
Reply from 69.73.108.20: bytes=32 time=39ms TTL=50
Reply from 69.73.108.20: bytes=32 time=29ms TTL=50
Reply from 69.73.108.20: bytes=32 time=37ms TTL=50
Reply from 69.73.108.20: bytes=32 time=29ms TTL=50
Reply from 69.73.108.20: bytes=32 time=40ms TTL=50
Request timed out.
Reply from 69.73.108.20: bytes=32 time=32ms TTL=50
Reply from 69.73.108.20: bytes=32 time=34ms TTL=50
Reply from 69.73.108.20: bytes=32 time=30ms TTL=50
Reply from 69.73.108.20: bytes=32 time=32ms TTL=50
Reply from 69.73.108.20: bytes=32 time=32ms TTL=50
Reply from 69.73.108.20: bytes=32 time=33ms TTL=50
Reply from 69.73.108.20: bytes=32 time=32ms TTL=50
Reply from 69.73.108.20: bytes=32 time=31ms TTL=50
Reply from 69.73.108.20: bytes=32 time=37ms TTL=50
Reply from 69.73.108.20: bytes=32 time=29ms TTL=50
Reply from 69.73.108.20: bytes=32 time=35ms TTL=50
Reply from 69.73.108.20: bytes=32 time=33ms TTL=50
Reply from 69.73.108.20: bytes=32 time=29ms TTL=50
Reply from 69.73.108.20: bytes=32 time=29ms TTL=50
Reply from 69.73.108.20: bytes=32 time=32ms TTL=50
Reply from 69.73.108.20: bytes=32 time=34ms TTL=50
Request timed out.
Reply from 69.73.108.20: bytes=32 time=28ms TTL=50
Reply from 69.73.108.20: bytes=32 time=34ms TTL=50
Reply from 69.73.108.20: bytes=32 time=29ms TTL=50
Reply from 69.73.108.20: bytes=32 time=28ms TTL=50
Reply from 69.73.108.20: bytes=32 time=30ms TTL=50
Reply from 69.73.108.20: bytes=32 time=32ms TTL=50
Reply from 69.73.108.20: bytes=32 time=29ms TTL=50
Reply from 69.73.108.20: bytes=32 time=29ms TTL=50
Reply from 69.73.108.20: bytes=32 time=32ms TTL=50
Reply from 69.73.108.20: bytes=32 time=32ms TTL=50
Request timed out.
Reply from 69.73.108.20: bytes=32 time=32ms TTL=50
Reply from 69.73.108.20: bytes=32 time=29ms TTL=50
Reply from 69.73.108.20: bytes=32 time=34ms TTL=50
Reply from 69.73.108.20: bytes=32 time=29ms TTL=50
Reply from 69.73.108.20: bytes=32 time=35ms TTL=50
Reply from 69.73.108.20: bytes=32 time=32ms TTL=50
Reply from 69.73.108.20: bytes=32 time=29ms TTL=50
Reply from 69.73.108.20: bytes=32 time=34ms TTL=50
Reply from 69.73.108.20: bytes=32 time=29ms TTL=50
Reply from 69.73.108.20: bytes=32 time=33ms TTL=50
Reply from 69.73.108.20: bytes=32 time=40ms TTL=50
Reply from 69.73.108.20: bytes=32 time=56ms TTL=50
Reply from 69.73.108.20: bytes=32 time=31ms TTL=50
Reply from 69.73.108.20: bytes=32 time=50ms TTL=50
Reply from 69.73.108.20: bytes=32 time=31ms TTL=50
Reply from 69.73.108.20: bytes=32 time=32ms TTL=50
Reply from 69.73.108.20: bytes=32 time=32ms TTL=50
Reply from 69.73.108.20: bytes=32 time=31ms TTL=50
Reply from 69.73.108.20: bytes=32 time=49ms TTL=50
Reply from 69.73.108.20: bytes=32 time=42ms TTL=50
Reply from 69.73.108.20: bytes=32 time=31ms TTL=50
Reply from 69.73.108.20: bytes=32 time=33ms TTL=50
Reply from 69.73.108.20: bytes=32 time=29ms TTL=50
Reply from 69.73.108.20: bytes=32 time=30ms TTL=50
Reply from 69.73.108.20: bytes=32 time=30ms TTL=50
Reply from 69.73.108.20: bytes=32 time=40ms TTL=50
Reply from 69.73.108.20: bytes=32 time=55ms TTL=50
Ping statistics for 69.73.108.20:
Packets: Sent = 446, Received = 403, Lost = 43 (9% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 412ms, Average = 35ms
Control-C
^C
So does knology know how to fix this...is there anyway to narrow it down for them? |
|
zpm
join:2009-03-23
Columbus, GA | i would copy that, and submit it to their web-support personnel and get a rep-or going..
you should have a low average ping than 30...it should be lower..
um, try another one and ping your node... 76.73.147.45 -t |
|
tidal
Tidal
Premium
join:2001-01-18
Madison, AL
| reply to tok3r
I'm with you on this. I get slow speeds alot and every time I call they treat it like it's the cabling or the router. I might switch back to dsl, it maybe slow but at least its reliable.
Knology speeds are way lower than comcast and mediacom too. |
|
zpm
join:2009-03-23
Columbus, GA | well, i hope 3.0 is released this year, otherwise i'll be complaining. |
|
Draggonden
join:2009-11-20
Columbus, GA
·Knology
| reply to tok3r
[From] Columbus,Muscogee,GA
[Business customer] Business customer
[Contract] $150 per month (12 month contract)
[Positives] "Honest Technician"
[Negatives] "Failure to spend money to upgrade."
[Bottom Line] "Knology Corporate feels there isn't a big enough paper trail of customer complaints to fix hardware issues."
If you do any online gaming at all this company is terrible.
One honest technician was scheduled to come to my address. Basically he said it would be a wasted trip because the problem is happening all over the Macon Rd. area.
Connectivity is terrible on West Coast servers, okay at best East Coast servers.
Connection drops out or disconnects every 3 minutes simultaneously on my computer, my girlfriend's computer, and our neighbors computer rather we are on a shared network or separate networks. Line connection or wireless.
Apparently 2 weeks ago someone ran a program that detected an issue on Knology's end. The repair is estimated at approx $40K to fix, but because there is not a big enough paper trail of customer complaints Knology has decided to do nothing except claim that the levels are stable on the ping tests. (Which they are, however the problem is with Knology's hardware.)
This information was taken directly from the service technician who said they are having to deal with this and fighting a losing battle for the customer.
If you have similar latency/connectivity issues please post on the forums and reviews. Make them give us the service we pay for! |
|
Annoyed
@knology.net | Every five minutes for about three seconds while playing games on my xbox the internet will lag and sometimes has dropped me out of the game. This is very annoying. We need the service we pay for! |
|
