dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
4803
share rss forum feed

Suncoast

join:2013-03-13
Largo, FL

What's going on with Pinellas County Wow! Knology?

What's going on with Pinellas County Knology? Seems like a lot of changes to the Internet lately. I'm not exactly seeing improvements. Been a customer since it was called Americast. Before this year I called for support twice. So far this year I have called or emailed several times. Lots of "Looks good from here." I was averaging 15Mbps in 2009. Then last year it went to 8Mbps. Now....



I'm reading in other posts that changes are taking place to the network. So I would really like to know... Is it time to jump ship? Or are changes underway that I should sit tight for?

wowcoder

join:2010-03-04
Curious as to what you get on their speed test site? »speedtest.wowway.com

Suncoast

join:2013-03-13
Largo, FL
2 to 3.6 down 1.1 up. If I unplug the cable modem all day, I'll get a higher rate for a short time.


zpm

join:2009-03-23
Columbus, GA
Could be they are over populated on that hub... not enough cmts cards at the head end....

Suncoast

join:2013-03-13
Largo, FL
reply to Suncoast


Things are looking up a little!

The first response (2-3.6 Mbps up) from a couple of days ago was from using the Pinellas Knology speed test server. Following are the results I get now that the Knology speed test is being resolved to the new Wowway server
Last Result:
Download Speed: 7992 kbps (999 KB/sec transfer rate)
Upload Speed: 1002 kbps (125.3 KB/sec transfer rate)
Latency: 86 ms
Saturday, March 16, 2013 7:25:49 PM


WOW_Dan
Premium
join:2011-03-24
Naperville, IL
kudos:35
I know from the CMTS side, that there is a lot of extra bandwidth available now than there was before. I was actually in Pinellas County doing a lot of hardware upgrades a couple of months ago to get you guys up to speed. Not to say there couldn't be a node issue or anything because it's possible, but I know that your available bandwidth is plentiful, and still growing as we upgrade.

I recommend using our speed test site because it's the only one that we can control. If you speed test off our network, there's no telling where that server is, or how many people are trying to use it at that time. Our servers are on our network, so there's not internet latency involved, and it should give you a more accurate result. You can however, if our speed test server shows poor, try another internet server, in case there is an issue with our speed test server, but so far I've not run into issues when using ours over the years.

If you still experience issues, feel free to shoot me a private message here on the forums with your information. Modem MAC address, address, phone number, and the name on the account are all good things to provide. I don't have access to the billing system that Knology used previously, and we continue to use currently in those markets, so I'm only able to find customers through the different back-end systems.
--
Dan Della Terza
WOW! Internet, Cable & Phone
CMTS Operations Engineer

Suncoast

join:2013-03-13
Largo, FL
Thank you Dan. Private message sent.

Suncoast

join:2013-03-13
Largo, FL
reply to Suncoast
Well, so much for Dan. Sent 2 private messages, nothing.

Since I keep having to unplug my cable modem for hours at a time to get online at all, I've decided to describe my issues to see if others are having similar problems.

Seems like every time I get on YouTube or Hulu it starts acting up. Maybe I'm just being a little paranoid....

Yesterday it was working great. But then I clicked on a time lapse image link from Spaceweather.com which unfortunately took me to YouTube. The HD video loaded about 30 seconds out of a 4 minute video and refused to budge any further. After that, my connectivity was shot for the day.

Sysinternals tcpview will show plenty of
Syn Sent connection attempts.

Usually it's back to normal in the morning... Except for my day off, Mondays. I'm barely staying online now with lots of errors.

Pinging my DHCP assigned Gateway IP
Summaries:

Ping statistics for 216.186.194.1:
Packets: Sent = 50, Received = 15, Lost = 35 (70% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 34ms, Average = 16ms

The current date is: Sun 03/24/2013
The current time is: 23:29:23.86
Ping statistics for 216.186.194.1:
Packets: Sent = 500, Received = 243, Lost = 257 (51% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 93ms, Average = 22ms

The current date is: Mon 03/25/2013
The current time is: 7:41:03.02
Ping statistics for 216.186.194.1:
Packets: Sent = 150, Received = 150, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 119ms, Average = 22ms

The current date is: Mon 03/25/2013
The current time is: 8:40:19.39
Ping statistics for 216.186.194.1:
Packets: Sent = 500, Received = 304, Lost = 196 (39% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 109ms, Average = 21ms


Seems like an interesting pattern to me...
(Only a Partial)

Reply from 216.186.194.1: bytes=1200 time=17ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=17ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=20ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=21ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=18ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=17ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=17ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=19ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=20ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=20ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=20ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=17ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=20ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=20ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=20ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=20ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=16ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=20ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=20ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=17ms TTL=253
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 216.186.194.1: bytes=1200 time=19ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=20ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=19ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=16ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=16ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=19ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=19ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=23ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=17ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=18ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=19ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=19ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=18ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=19ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=19ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=20ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=20ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=20ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=17ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=18ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=19ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=20ms TTL=253
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 216.186.194.1: bytes=1200 time=18ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=19ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=20ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=17ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=20ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=20ms TTL=253
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 216.186.194.1: bytes=1200 time=18ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=18ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=18ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=18ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=19ms TTL=253
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 216.186.194.1: bytes=1200 time=19ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=19ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=19ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=18ms TTL=253
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 216.186.194.1: bytes=1200 time=33ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=18ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=18ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=19ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=19ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=19ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=19ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=20ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=18ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=18ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=19ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=24ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=87ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=42ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=46ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=18ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=20ms TTL=253
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 216.186.194.1: bytes=1200 time=102ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=61ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=80ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=20ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=18ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=20ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=19ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=19ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=19ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=39ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=17ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=17ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=18ms TTL=253
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 216.186.194.1: bytes=1200 time=31ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=18ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=17ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=20ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=18ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=18ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=22ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=16ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=20ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=20ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=17ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=18ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=21ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=18ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=18ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=22ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=19ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=19ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=22ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=17ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=17ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=20ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=20ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=17ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=18ms TTL=253
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 216.186.194.1: bytes=1200 time=31ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=22ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=19ms TTL=253
Reply from 216.186.194.1: bytes=1200 time=20ms TTL=253


WOW_Dan
Premium
join:2011-03-24
Naperville, IL
kudos:35
said by Suncoast:

Well, so much for Dan. Sent 2 private messages, nothing.

Since I keep having to unplug my cable modem for hours at a time to get online at all, I've decided to describe my issues to see if others are having similar problems.

Seems like every time I get on YouTube or Hulu it starts acting up. Maybe I'm just being a little paranoid....

Yesterday it was working great. But then I clicked on a time lapse image link from Spaceweather.com which unfortunately took me to YouTube. The HD video loaded about 30 seconds out of a 4 minute video and refused to budge any further. After that, my connectivity was shot for the day.

Sysinternals tcpview will show plenty of
Syn Sent connection attempts.

Usually it's back to normal in the morning... Except for my day off, Mondays. I'm barely staying online now with lots of errors.

I just replied to your private message with the issue I found and what I did to hopefully resolve it. Please be patient when contacting me on this forum. I'm not always able to check in here on a daily basis, so it could take me a few days to respond. My presence here on this forums is not part of my position with the company. I'm here in my spare time to help people when I can.
--
Dan Della Terza
WOW! Internet, Cable & Phone
CMTS Operations Engineer

Suncoast

join:2013-03-13
Largo, FL
Thanks. Hopefully you're still nearby, as my ... lets say my reliability is 0/255. I just responded to your IM. Thanks.

Suncoast

join:2013-03-13
Largo, FL
reply to WOW_Dan
A public Thanks Dan! I just sent you another IM.

For anyone else following this, Dan has been able to get me back online as well as pointing out an issue with my own equipment that needs to be resolved.