Time Warner Cable - Legacy → Re: Cox Fairfax: The Worst Cable ISP in the country?

Congratulations!
100% better.
You will be automatically put in Washington DC POP.
I'm using Speakeasy here at my office: I have CoxSuxRR Cable at home :-( I'm 18,700 feet away from CO. So...
You won't even experience a minor scratch (?) from your dsl connection with Speakeasy.

Damn. I envy you.

That's not as automatic as you think. Covad may say this is not in his local area and be forced unto one of the National PoPs, which is NYC being the closet.

said by Notating:

---

That's not as automatic as you think. Covad may say this is not in his local area and be forced unto one of the National PoPs, which is NYC being the closet.

---

Once you qualify for DSL (means copper is available from your home to the CO and within specs) you can choose from a number of ISPs that service that particular CO. One of those ISPs will probably have a local POP. If not a decent pipe from DC to NY isn't terrible if maintained and not oversold. Too bad my area doesnt have DSL available.

Someone also asked about "resistance" in the cable line. There are a number issues with cable broadband. If you don't have a good signal both on the downstream and upstream, you'll have a lousy connection. Upstream noise tends to be the most difficult to deal with in traditional cable broadband networks since the system was designed to push the signal to your house not vice versa. Plus the upstream channel is alot smaller than downstream so everyone in your node fights for the smaller space. So cable companies are segmenting the nodes by laying fiber lines farther out from the headend gear.

However, the most widespread problem I've seen is oversold bandwidth. It happened with dialup ISPs and its happening with cable ISPs. More so now because of the huge costs involved with laying down more fiber. Cox Fairfax needs to cut back on selling their network and concentrate on fixing it.

said by vtechgsx:

---

Once you qualify for DSL (means copper is available from your home to the CO and within specs) you can choose from a number of ISPs that service that particular CO. One of those ISPs will probably have a local POP. If not a decent pipe from DC to NY isn't terrible if maintained and not oversold. Too bad my area doesnt have DSL available.

---

Been through this process, had dsl. What makes you think these PoPs aren't oversold? It may not make too much of a difference to you personally, but for someone who is a gamer it's a big difference with pings.

quote:

---

However, the most widespread problem I've seen is oversold bandwidth. It happened with dialup ISPs and its happening with cable ISPs. More so now because of the huge costs involved with laying down more fiber. Cox Fairfax needs to cut back on selling their network and concentrate on fixing it.

---

Once again, you don't think the dsl community isn't going through the same thing? Wake up my friend, why do you think I mentioned in an earlier post that just because you're in VA, doesn't mean you'll be put on that local PoP in WDC? If Covad or SE say that it's not within his local area, he'll be routed right to a National PoP like NYC which isn't in his best interest whatsoever.

You will get similar ping and speed if you are routed to NY or DC. I know by experience. SE is good. I can't get it at home though because of the F king co distance and Verizon won't install repeaters. Damn.

N-Virginians are most likely to get DC pop. If not, it'll be still ok. Don't worry. Fu king Cox/RR.

quote:

---

Been through this process, had dsl. What makes you think these PoPs aren't oversold? It may not make too much of a difference to you personally, but for someone who is a gamer it's a big difference with pings.

---

First off when your first hop is in bad shape you're overall connection is piss poor because you always go through that bad spot. Your connection will be at least as bad as that first hop and in our case it is very bad. Second, once you get out to the cable POP (which for us in RR North Carolina) you get hit with even MORE network congestion because of the pooling of all the cable ISP traffic. You basically get hit twice. Once on the first hop, and second at the POP.

You want bad pings? look at some of the traceroutes in this thread and see how bad it is at the first hop.

The main difference is that DSL users have a choice as to who carries their traffic. Having problems with your current ISP? Switch. At least you have a choice albeit limited. With cable you're stuck with the local monopoly.

just an example of the bad first hop/gateway sorry for the spam
C:\WINDOWS>ping -n 50 10.63.0.5

Pinging 10.63.0.5 with 32 bytes of data:

Reply from 10.63.0.5: bytes=32 time=665ms TTL=255
Request timed out.
Reply from 10.63.0.5: bytes=32 time=103ms TTL=255
Reply from 10.63.0.5: bytes=32 time=543ms TTL=255
Request timed out.
Request timed out.
Request timed out.
Reply from 10.63.0.5: bytes=32 time=449ms TTL=255
Reply from 10.63.0.5: bytes=32 time=440ms TTL=255
Reply from 10.63.0.5: bytes=32 time=463ms TTL=255
Reply from 10.63.0.5: bytes=32 time=910ms TTL=255
Reply from 10.63.0.5: bytes=32 time=702ms TTL=255
Reply from 10.63.0.5: bytes=32 time=219ms TTL=255
Reply from 10.63.0.5: bytes=32 time=229ms TTL=255
Reply from 10.63.0.5: bytes=32 time=723ms TTL=255
Reply from 10.63.0.5: bytes=32 time=586ms TTL=255
Reply from 10.63.0.5: bytes=32 time=433ms TTL=255
Reply from 10.63.0.5: bytes=32 time=138ms TTL=255
Reply from 10.63.0.5: bytes=32 time=127ms TTL=255
Reply from 10.63.0.5: bytes=32 time=204ms TTL=255
Reply from 10.63.0.5: bytes=32 time=797ms TTL=255
Reply from 10.63.0.5: bytes=32 time=271ms TTL=255
Reply from 10.63.0.5: bytes=32 time=439ms TTL=255
Reply from 10.63.0.5: bytes=32 time=549ms TTL=255
Reply from 10.63.0.5: bytes=32 time=234ms TTL=255
Reply from 10.63.0.5: bytes=32 time=281ms TTL=255
Reply from 10.63.0.5: bytes=32 time=80ms TTL=255
Reply from 10.63.0.5: bytes=32 time=405ms TTL=255
Reply from 10.63.0.5: bytes=32 time=286ms TTL=255
Reply from 10.63.0.5: bytes=32 time=520ms TTL=255
Reply from 10.63.0.5: bytes=32 time=853ms TTL=255
Reply from 10.63.0.5: bytes=32 time=952ms TTL=255
Request timed out.
Reply from 10.63.0.5: bytes=32 time=924ms TTL=255
Reply from 10.63.0.5: bytes=32 time=165ms TTL=255
Reply from 10.63.0.5: bytes=32 time=350ms TTL=255
Request timed out.
Request timed out.
Reply from 10.63.0.5: bytes=32 time=289ms TTL=255
Reply from 10.63.0.5: bytes=32 time=866ms TTL=255
Reply from 10.63.0.5: bytes=32 time=609ms TTL=255
Request timed out.
Reply from 10.63.0.5: bytes=32 time=199ms TTL=255
Reply from 10.63.0.5: bytes=32 time=359ms TTL=255
Request timed out.
Reply from 10.63.0.5: bytes=32 time=585ms TTL=255
Reply from 10.63.0.5: bytes=32 time=53ms TTL=255
Reply from 10.63.0.5: bytes=32 time=350ms TTL=255
Reply from 10.63.0.5: bytes=32 time=147ms TTL=255
Reply from 10.63.0.5: bytes=32 time=1075ms TTL=255

Ping statistics for 10.63.0.5:
Packets: Sent = 50, Received = 41, Lost = 9 (18% loss),
Approximate round trip times in milli-seconds:
Minimum = 53ms, Maximum = 1075ms, Average = 371ms

thats my gateway, incase you havent noticed, and id disguise it but i dont really see the point, not like anyone will be spamming my gateway to slow down my connection, besides i dont think it can go any slower, but i may be wrong. Oh btw cox is giving me half credit for both my cable tv and RR, which is nice because they both suck, not that i should be paying for either of them. That will last for three months or until my service improves, i think, but last time i asked for credit they denied it without reason and without telling me. Anyway its worse than ever right now, but with my half TV and RR it covers more than the cost RR completely by itself. Id just rather have my service fixed though.