Hey Cox users in Fairfax County. Wondering why your internet connection sucks ass today? It's because one of Cox's main peering points (where Cox meets the rest of the internet) in Ashburn is down and has been since just after midnight.

To see for yourself fire up your DOS command prompt and type: tracert (some website)

Not all sites are affected, but many are. Look at my trace to google.com:

C:\Documents and Settings\Owner>tracert www.google.com

Tracing route to www.l.google.com [64.233.161.99]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    16 ms    11 ms    12 ms  ip68-100-78-1.dc.dc.cox.net [68.100.78.1]
  3     9 ms     9 ms    11 ms  68.100.1.113
  4    13 ms    12 ms    11 ms  ip68-100-0-65.dc.dc.cox.net [68.100.0.65]
  5    17 ms    25 ms    13 ms  mrfddsrj02gex070003.rd.dc.cox.net [68.100.0.149]
  6    10 ms    13 ms    11 ms  mrfdbbrj02-ge020.rd.dc.cox.net [68.1.1.6]
  7    16 ms    30 ms    31 ms  ashbbbrj01-pos020100.r2.as.cox.net [68.1.1.232]
  8     *        *        *     Request timed out.
  9    46 ms    13 ms     *     216.239.46.19
 10     *       17 ms    12 ms  72.14.236.200
 11     *        *       25 ms  216.239.49.214
 12    15 ms     *        *     64.233.161.99
 13    17 ms    20 ms    14 ms  64.233.161.99

Trace complete.

See right after hop #7 (ashbbbr [Ashburn]) everything starts getting shitty and unuseable?

What you can do:
CALL COX at (703) 378-3934 and say your service hasn't been working right since just after midnight last night and you WANT A REFUND. I managed to get $10 off from them. If you call the number and get a busy signal try from your cell phone. For some reason they have a very small verizon land-line switchboard that always fills up. I can almost never get through to them with my land line but with my T-Mobile cell phone I've never gotten a busy signal.

The more people call and demand refunds the less likely there will be a problem like this again.

Funny, when I call them it says "Thank you for choosing Cox Communications." I didn't choose shit. You were forced upon me and if I could get decent DSL speeds I'd be off your shitty network in a heartbeat! I'll keep praying for WiMax.

/rant

Performance on Cox has sucked all weekend. And earlier in the week it would randomly go down for a minute or two... real annoying. I am waiting on FIOS offering TV channels and then I'm giving the bird to Cox.

yes i have noticed how absoulutely god awful slow it was today, but would work once and awhile, other times not at all, and other times just sit and sit and finally time out

but the funny thing is i dont even use Cox, so it must have been effecting more then that

I work for a ISP, and router failures will happen. Just like everything else that breaks. I actually called there support when this happend and TOLD them what the problem was, but they gave me the random line of bullshit. We dont see anything in our system can you rest your modem.. blah blah

Interesting. Again there are routing problems this morning and you're right, "Cox sucks cocks", all the traffic is dieing directly after the ashburn peering point.

D:\Documents and Settings\Cary>tracert www.yahoo.com

Tracing route to www.yahoo.akadns.net [68.142.197.64]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.254
  2    15 ms    12 ms    25 ms  ip68-228-14-1.dc.dc.cox.net [68.228.14.1]
  3    11 ms    11 ms    16 ms  68.100.1.113
  4    14 ms    13 ms    11 ms  ip68-100-0-65.dc.dc.cox.net [68.100.0.65]
  5    20 ms    11 ms    15 ms  mrfddsrj01gex070003.rd.dc.cox.net [68.100.0.141]
  6    12 ms    16 ms    12 ms  mrfdbbrj01-ge020.rd.dc.cox.net [68.1.1.4]
  7    12 ms    11 ms    14 ms  mrfdbbrj02-ge030.rd.dc.cox.net [68.1.1.3]
  8    23 ms    13 ms    12 ms  ashbbbrj01-pos020100.r2.as.cox.net [68.1.1.232]
  9    13 ms    28 ms     *     68.1.0.220
 10     *       21 ms     *     68.105.30.98
 11    59 ms    44 ms     *     so-0-0-0.pat2.dax.yahoo.com [216.115.101.147]
 12    66 ms     *        *     ge-0-1-0-p100.msr1.mud.yahoo.com [216.115.104.97]
 13    44 ms     *        *     ten-8-1.bas1.mud.yahoo.com [68.142.193.25]
 14     *       44 ms     *     p1.www.mud.yahoo.com [68.142.197.64]
 15    55 ms     *        *     p1.www.mud.yahoo.com [68.142.197.64]
 16    61 ms    43 ms    53 ms  p1.www.mud.yahoo.com [68.142.197.64]

Trace complete.

I'll be sure to call them and demand my refund for the day.

djamp, I too work for a small ISP. But due to limitations in DSL technology I have to use Cox's cable network for real high-speed internet. Router failures positively happen, but usually BGP will negotiate a new route, not continue sending traffic through a link with 60% packet loss to the outside world.

Oh well, I'll call them and see what happens.

Yeah, they ruined my Sunday morning too. Someone on the Cox usenet groups suggested installing TreeWalk... I think I'm going to have to do that now because it is getting bad.

http://ntcanuck.com/

people have to start spraying a few extra letters on the Cox vans. "COX SUX COX" i think anyone would would enjoy such a thing would understand. :)


"the wisdom of the wise will perish, the intelligence of the intelligent will vanish."

I know where I like to route my cox!

I had ZERO problem routing my cox into the OP's wifes snatch. Issue is an ID10T error between the floor and the keybaord of the OP.

Cox sucks cocks harder Wrote:
-------------------------------------------------------
> I had ZERO problem routing my cox into the OP's
> wifes snatch. Issue is an ID10T error between the
> floor and the keybaord of the OP.


9 years ago. dumb ass.

BGP can't directly detect packet loss on an interface. If you happen to be crazy enough to peer over the same interface as you route, then you might indirectly detect this. Still BGP isn't very chatty and uses tcp so it can deal with a fair bit of packet less.