When I ping www.google.com -t for a while, I get scary results:
Reply from 74.125.95.104: bytes=32 time=66ms TTL=239
Reply from 74.125.95.104: bytes=32 time=64ms TTL=239
Request timed out.
Reply from 74.125.95.104: bytes=32 time=69ms TTL=239
Reply from 74.125.95.104: bytes=32 time=69ms TTL=239
Reply from 74.125.95.104: bytes=32 time=75ms TTL=239
Reply from 74.125.95.104: bytes=32 time=67ms TTL=239
Reply from 74.125.95.104: bytes=32 time=64ms TTL=239
Request timed out.
Request timed out.
Request timed out.
Reply from 74.125.95.104: bytes=32 time=65ms TTL=239
Reply from 74.125.95.104: bytes=32 time=66ms TTL=239
Request timed out.
Request timed out.
Request timed out.
Reply from 74.125.95.104: bytes=32 time=65ms TTL=239
Reply from 74.125.95.104: bytes=32 time=64ms TTL=239
Request timed out.
Request timed out.
Reply from 74.125.95.104: bytes=32 time=67ms TTL=239
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 74.125.95.104: bytes=32 time=75ms TTL=239
Reply from 74.125.95.104: bytes=32 time=68ms TTL=239
Reply from 74.125.95.104: bytes=32 time=65ms TTL=239
Reply from 74.125.95.104: bytes=32 time=66ms TTL=239
That's a lot of timing out. And, it's been worse.
Nearly every other click, website, download, or IM is hesitated up to 2 minutes depending on the application and how hey implemented network errors.
I'm paying extra for the pro-package. My connection speed 3 months ago was registering on speedtest.net at 14mb. My average download was 500-600k/sec down and 300k/sec up, I'm starting to get a little pissed that I cant download anything from a respectable server faster than 40k/sec. Not to mention, it takes forever to just navigate around a website.
I have heard that somewhere between Bakersfield and LA is a broken connection and is therefore contributing to this mess, true or not, this sounds feasible. I have various friends all over Bakersfield who have the same issues. In the time it has taken me to write this blog, here are my pings:
Reply from 74.125.95.104: bytes=32 time=68ms TTL=239
Reply from 74.125.95.104: bytes=32 time=68ms TTL=239
Reply from 74.125.95.104: bytes=32 time=65ms TTL=239
Reply from 74.125.95.104: bytes=32 time=64ms TTL=239
Reply from 74.125.95.104: bytes=32 time=65ms TTL=239
Reply from 74.125.95.104: bytes=32 time=66ms TTL=239
Reply from 74.125.95.104: bytes=32 time=68ms TTL=239
Reply from 74.125.95.104: bytes=32 time=63ms TTL=239
Reply from 74.125.95.104: bytes=32 time=70ms TTL=239
Reply from 74.125.95.104: bytes=32 time=67ms TTL=239
Reply from 74.125.95.104: bytes=32 time=67ms TTL=239
Reply from 74.125.95.104: bytes=32 time=68ms TTL=239
Reply from 74.125.95.104: bytes=32 time=64ms TTL=239
Reply from 74.125.95.104: bytes=32 time=70ms TTL=239
Reply from 74.125.95.104: bytes=32 time=69ms TTL=239
Reply from 74.125.95.104: bytes=32 time=69ms TTL=239
Reply from 74.125.95.104: bytes=32 time=65ms TTL=239
Reply from 74.125.95.104: bytes=32 time=64ms TTL=239
Reply from 74.125.95.104: bytes=32 time=69ms TTL=239
Reply from 74.125.95.104: bytes=32 time=68ms TTL=239
Reply from 74.125.95.104: bytes=32 time=181ms TTL=239
Reply from 74.125.95.104: bytes=32 time=64ms TTL=239
Reply from 74.125.95.104: bytes=32 time=75ms TTL=239
Reply from 74.125.95.104: bytes=32 time=74ms TTL=239
Reply from 74.125.95.104: bytes=32 time=69ms TTL=239
Reply from 74.125.95.104: bytes=32 time=68ms TTL=239
Request timed out.
Reply from 74.125.95.104: bytes=32 time=71ms TTL=239
Reply from 74.125.95.104: bytes=32 time=73ms TTL=239
Reply from 74.125.95.104: bytes=32 time=65ms TTL=239
Reply from 74.125.95.104: bytes=32 time=66ms TTL=239
Magically all better, WTF??? Any why am I still averaging 67ms to google.com ???
This is the kind of crap this is bugging the hell out of me. As a programmer I make a lot of FTP uploads and navigate the web quite often. It's pretty annyong chatting on yahoo about how google.com won't load. It's irritating.. existing connections work somewhat ok, but making NEW connections is iffy...
Bright House needs to get their shit together because I for one am tired of this crappy service. I was at a friends business and a Bright House employee came in to 'inspect the modem' and was greeted with "So, here to fix my internet?" his responce was "Well, I can't guarantee that"
So, could Bright House be sending out employees to keep people thinking it's their faulty equiptment? You decide.
If you are having issues with Bright House, please leave a comment and a sample of your pings by using ping www.google.com -t in cmd
5 comments:
Brighthouse sucks this month!
Tell me about it, my business class at work goes down very frequently XD
I remember having the problem so I have no intention of defending the time warner armada. That said, I have heard things like that from angry customers plenty. That's why I want to work on redesigning these systems and improving them where improvement is needed.
We must take over and change the paradigm, today we are four, but tomorrow?
Who can say?
We can reverse engineer the world and make it better as the united human race, hack the planet and let the new take root
I had a similar issue with Charter about a month ago following a day long cable outage. It took about 4 phone calls and 2 technicians coming out to convince them there was something wrong with their lines. I don't know how wide spread the issue was, but at least mine got resolved after about 2 weeks. We managed to get a credit for the lousy service, so I'd call up Bright House and demand a credit as well, they'll likely try and do something about their service if you do.
I just Switched from BrightHouse in Bakersfield to AT&T Uverse 18KBsec down 1.5KBsec UP, works great no problems! Customer service is great, Tech gave me his cell phone, call day or night if there are any issues.
Post a Comment