Archive for the ‘Charter Pipeline’ Category

60/5 Megabit Service

Monday, January 11th, 2010

I’m excited to try Charter’s new Docsis 3.0 60 mbit service in St. Louis. Pricing was $30 more than what I’m currently paying for 20/2.

My Charter 16Mbit Speed Test

Friday, May 2nd, 2008

I had to call Charter back the next day – the first provisioning wasn’t performed correctly and now I’m seeing increased performance:


Not 16 mbits, but I like the almost 2 mbit up.

Charter Now Offers 16mbit/2mbit in St. Louis

Thursday, May 1st, 2008

Just called and I’m set up for 16/2.  The pricing is the same as the old 10/1 price.

Charter To Offer 16MB /2 MB in St. Louis

Friday, April 18th, 2008

Not available yet but this link implies that Charter will offer this in St. Louis at some point:

Charter Thread

Charter and Google Fixed in St. Louis?

Monday, April 7th, 2008

I haven’t change my DNS back to Charter’s servers but a post in this thread seems to indicate that the problem has been resolved.

OpenDNS seems to be working well for me and I must might leave it set up for a few days to see if I continue to like it.

Google and Charter – DNS Issues in St. Louis – Is it Charter’s DNS or Routing?

Monday, April 7th, 2008

Over the last week I’ve had trouble hitting Google with the address  The following is what I see:


I decided to use OpenDNS as indicated below. It seemed to work at first but then an hour later I’m having the problem again – the following solution actually may not work. Upon reviewing the thread below, it seems the issue is routing of some sort and pointing at OpenDNS may not fix the problem. At this point the only fix seems to be to use the one of Google’s numeric IP address such as

It appears to be a problem with Charter’s DNS as seen in this thread:

Google and Charter DNS Thread – Broadband Reports

Hitting the IP address seems to work fine.  Some solutions:

Use a host table entry for to the IP or point your DNS to Open DNS:

It is definitely annoying and others have reported that Charter support does not accept responsibility for this issue.