US Cable Support > Cox HSI > COX HSI Problems NOVA - Part 2

COX HSI Problems NOVA - Part 2

reply to Hank
For reference, The followings are the links about COX service in Northern Virginia which consist about 70 pages with about 1,500 comments:

It all started with this excellent thread.

And the above thread led to this baby.

This is the third thread dealing with NOVA COX problems.

reply to Hank
I have problem:

Don't know if you have noticed or not, but I have been looking at 68.1.1.17. Your plot also indicates that maybe there is a problem at this address. CoxEngr any comment on this?

reply to Hank
Pinging nyc.speakeasy.net [216.254.95.2] with 32 bytes of data:

Reply from 216.254.95.2: bytes=32 time=62ms TTL=239
Reply from 216.254.95.2: bytes=32 time=57ms TTL=239
Reply from 216.254.95.2: bytes=32 time=40ms TTL=239
Reply from 216.254.95.2: bytes=32 time=43ms TTL=239

I've been looking for that first thread for a while. I think for most people it's improved at least somewhat since then. But it shows how long people had to (and how a lot of them still do) put up with Cox's BS. For a few days now, excluding a few minor jolts of high latency, I've been getting great service. But as it has happened many times previously, I'm doubtful of a long duration of this.

reply to Hank

reply to Hank
You managed good pings without packet loss for a little while though. What happened?

reply to Hank
Gene, not sure if you're talking to me or not, but actually, things aren't all that bad. I'm still breaking my cap and things are fairly consistent. Still have that problem where I lose my connection when I'm d/l anything, but it reconnects after 5 seconds. I think it has something to do with the modem issue currently listed on Cox's support page for fairfax. I'm not sure. I guess once they clear that up and if I still have the issue, then I'll know it's not related to that.

However, that one router Hank mentioned is consistently screwy.

reply to Hank
I'm not feeling too good to do this because it is copying. But I just couldn't help do so because this comment is worth letting other Virginians know (The change I made to the original comment BMW22003 made was just breaking into phrases):

BMW22033 said:

I've seen a couple of people already mention this but how many people have filed a complaint about these problems with the Fairfax county Cable & Consumer Affairs department? If you have done so, what kind of response did you get?

After dealing with Cox "technical support" for the past two months now, I can't help but feel disgusted with what I would consider their overwhelmingly apathetic approach in dealing with this situation. I can't even begin to count the number of technical support reps, supervisors and technicians that I've spoken to. I've uploaded traceroute after traceroute to them. They've sent out four technicians to my home and neighborhood to check signal levels, etc. In fact, it was nearly a month after I first began reporting these problems that ANYONE would even acknowledge that this might be a problem with their network.

I've heard every kind of excuse imaginable about the source of the problem including the fact that the hub I'm on (hub 13) will have to be upgraded to digital before these problems go away. And when I asked how long that was going to be I was told "I don't really know for certain but probably within four to six months. It's not our fault, though. We're having problems getting the necessary permits from VDOT."

The system status page at status.cox.net was finally updated about a week ago to reflect this problem but they indicate that it began on or around 6/27/02. In my opinion, it began two months earlier than that.

Lastly, in light of this problem which Cox has now finally acknowledged, they have decided to go ahead with a $5 - $10 a month price increase for this service!?! Call me naive, but that's completely mindboggling to me. When I called to ask how they could possibly justify this increase right now, the tech support rep said "Well, the increase is mainly due to the fact that we ended our relationship with Road Runner in order to create the new Cox network that provides you with so many more benefits." Benefits?!?!? Like packet loss, high latency and dropped connections?

From what I've been told by a number of tech support reps and field techs, there are a large number of people in Northern Virginia being affected by these problems. It's obvious that many people here are more than familiar with the problems that I'm talking about. I know that Fairfax county "reprimanded" Cox a number of times in recent years for different things (primarily cable TV service I imagine?).

If you've complained to the county about the problems that have been occuring for the past 30 - 60 days, what kind of response have you gotten from them? Or from Cox? Would it be worth trying to put together a petition or, for lack of a better term, a "class action" complaint? I'd certainly like to hear your thoughts on the matter.

reply to ntgreat
My bad, I tend to forget the presence of the "reply to this post" feature.

reply to ntgreat
NTGreat - I have sent you an instant message. Should be flashing icon at top of your screen. Double click to read.
Thanks

Bah i dont think that that forum counts as a rant or a rave...... just a continual update on how crappy cox is. But it was going to get to be like the other forum where you had to reply to specific people instead of the forum itself because its so old. Also i find ping plotter to be somewhat unreliable if you start out with over a 100 ping...... it just goes up and up to about 500. so i guess if u start out with over a 100 ping you should use a normal traceroute to get your traces. I mean its only a 20 ms difference from my node to dslreports, but i start out with a 90 ping, so on pingplotter it ends up in the 500's. just wanted to point that out.
--
"We own the night." -Ding Chavez (Ninja)

reply to Hank
True. What's the bitsize of the ping packets it sends to each hop?

reply to Hank
Now my problem is not with latency, but usually about a minute after joining a game server, my connection will fail. I'll start to get cl_flushentitypacket and "Connection Problem" errors. This seems to happen a lot more often during online gaming, but even just during normal use, this will randomly occur several times within an hour. Every so often my cable light goes out also. Can Cox ever abstain from having network problems? I wouldn't be surprised if I started getting bad latency again once they fix this problem.

reply to COXnightmare

said by COXnightmare:

---

BMW22033 said:
...Lastly, in light of this problem which Cox has now finally acknowledged, they have decided to go ahead with a $5 - $10 a month price increase for this service!?! Call me naive, but that's completely mindboggling to me. When I called to ask how they could possibly justify this increase right now, the tech support rep said "Well, the increase is mainly due to the fact that we ended our relationship with Road Runner in order to create the new Cox network that provides you with so many more benefits." Benefits?!?!? Like packet loss, high latency and dropped connections?...

---

reply to i87

said by i87:

---

Bah i dont think that that forum counts as a rant or a rave...... just a continual update on how crappy cox is. But it was going to get to be like the other forum where you had to reply to specific people instead of the forum itself because its so old. Also i find ping plotter to be somewhat unreliable if you start out with over a 100 ping...... it just goes up and up to about 500. so i guess if u start out with over a 100 ping you should use a normal traceroute to get your traces. I mean its only a 20 ms difference from my node to dslreports, but i start out with a 90 ping, so on pingplotter it ends up in the 500's. just wanted to point that out.

---

reply to i87
yeah hene that happened to me too today. i was playing CS and suddenly i get cl_flush.... that was strange cause i havent gotten that in over 2 months. seconds later i get kicked with the message i87 has overflowed, and find out everything else i have been running has been disconnected. i open winipcfg to release and renew my ip, and it comes up with the default. then i look at my modem and all the lights except power are off. so i power cycle it and renew my ip and im all set. it only happen once to me today, but i have no doubt it has happened more.
--
"We own the night." -Ding Chavez (Ninja)

reply to Hank
It's happened to me a lot today. As I said, I have, and still am getting great pings, but out of nowhere my modem will cease to receive data, and the cable light will go dark for about 5 minutes. It just happened now as I was about to post this.

reply to Hank
It's happened to me a lot today. As I said, I have, and still am getting great pings, but out of nowhere my modem will cease to receive data, and the cable light will go dark for about 5 minutes. It just happened 3 times in a row as I was about to post this.