Talk > Rants, Raves, and Praise > COX Fairfax, VA: The worst ISP in the nation?

reply to COXnightmare

Re: COX Fairfax, VA: The worst ISP in the nation?

said by GeneStarwind:

---

Not too bad, especially considering it's 7:20pm. Must be on one of the faster nodes right now. But I'd be foolish to think that this will last even a day.

---

reply to COXnightmare
Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:

1 220 ms 220 ms 316 ms 10.63.0.109
2 275 ms 371 ms 220 ms ffaxvamtc-gsr1-srp0-0.cox.rr.com [24.28.222.1]
3 220 ms 371 ms 220 ms ffaxvamtc-gsr2-srp0-0.cox.rr.com [24.28.222.2]
4 234 ms 233 ms 261 ms herva-rdc-gsr3-pos2-0.her.rr.com [24.30.192.141]

5 261 ms 206 ms 220 ms herva-rdc-gsr2-pos4-0.her.rr.com [24.30.192.53]

6 220 ms 247 ms 220 ms pop3-rtc-P2-0.atdn.net [66.185.140.141]
7 439 ms 247 ms 454 ms bb2-rtc-P14-0.atdn.net [66.185.140.133]
8 247 ms 247 ms 440 ms bb2-dcl-P5-0.atdn.net [66.185.153.13]
9 219 ms 220 ms 755 ms bb2-nyc-P4-0.atdn.net [66.185.153.174]
10 316 ms 220 ms 233 ms pop1-nyc-P6-0.atdn.net [66.185.142.230]
11 247 ms 220 ms 233 ms NetAccess.atdn.net [66.185.142.234]
12 234 ms 370 ms 220 ms a9-0-0-8.msfc1.oct.nac.net [209.123.11.85]
13 247 ms 233 ms 275 ms www.dslreports.com [209.123.109.175]

Trace complete.

at 2:57 AM in the morning
--
go pats

said by nepatsfan4:

---

Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:

1 220 ms 220 ms 316 ms 10.63.0.109
2 275 ms 371 ms 220 ms ffaxvamtc-gsr1-srp0-0.cox.rr.com [24.28.222.1]
3 220 ms 371 ms 220 ms ffaxvamtc-gsr2-srp0-0.cox.rr.com [24.28.222.2]
4 234 ms 233 ms 261 ms herva-rdc-gsr3-pos2-0.her.rr.com [24.30.192.141]

5 261 ms 206 ms 220 ms herva-rdc-gsr2-pos4-0.her.rr.com [24.30.192.53]

6 220 ms 247 ms 220 ms pop3-rtc-P2-0.atdn.net [66.185.140.141]
7 439 ms 247 ms 454 ms bb2-rtc-P14-0.atdn.net [66.185.140.133]
8 247 ms 247 ms 440 ms bb2-dcl-P5-0.atdn.net [66.185.153.13]
9 219 ms 220 ms 755 ms bb2-nyc-P4-0.atdn.net [66.185.153.174]
10 316 ms 220 ms 233 ms pop1-nyc-P6-0.atdn.net [66.185.142.230]
11 247 ms 220 ms 233 ms NetAccess.atdn.net [66.185.142.234]
12 234 ms 370 ms 220 ms a9-0-0-8.msfc1.oct.nac.net [209.123.11.85]
13 247 ms 233 ms 275 ms www.dslreports.com [209.123.109.175]

Trace complete.

at 2:57 AM in the morning

---

reply to COXnightmare
I did a line quality test here

»/quality/nil/702222

Apparently I have very little packet loss (with the exception of the very last hops). Any server I go on has people skipping all over the place. Isn't that a sure sign of packet loss? Hmm...
[text was edited by author 2002-03-16 17:53:47]

Yes. Your connection sux. And mine is much worse.

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

1 84 ms 201 ms 100 ms 10.63.0.109
2 131 ms 108 ms 131 ms ffaxvamtc-gsr1-srp0-0.cox.rr.com [24.28.222.1]
3 105 ms 96 ms 93 ms ffaxvamtc-gsr2-srp0-0.cox.rr.com [24.28.222.2]
4 52 ms 76 ms 126 ms herva-rdc-gsr3-pos2-0.her.rr.com [24.30.192.141]

5 45 ms 46 ms 43 ms herva-rdc-gsr2-pos4-0.her.rr.com [24.30.192.53]

6 110 ms 227 ms 73 ms herva-rdc-gsr1-pos1-0.her.rr.com [24.30.192.26]

7 36 ms 142 ms 77 ms iar2-sonet2-3-0-0.Restonrst.cw.net [208.173.155.
89]
8 151 ms 93 ms 141 ms acr1-loopback.Restonrst.cw.net [206.24.178.61]
9 * 156 ms 63 ms exodus-communications.Restonrst.cw.net [206.24.1
79.134]
10 244 ms 99 ms 125 ms dcr04-g6-0.stng01.exodus.net [216.33.99.84]
11 53 ms 25 ms 135 ms csr22-ve241.stng01.exodus.net [216.33.98.19]
12 150 ms 55 ms 63 ms 216.35.210.126
13 131 ms 71 ms 101 ms www.yahoo.akadns.net [64.58.76.222]

Trace complete.

It was good for a few days, but it looks like it's back to normal now. I love it how all of these slow-downs are so punctual: always at 11:30am during weekends, and 4:10pm during weekdays. I just wish cox was as punctual with their upgrades.

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

1 155 ms 179 ms 108 ms 10.63.0.109
2 195 ms 168 ms 207 ms ffaxvamtc-gsr2-srp0-0.cox.rr.com [24.28.222.2]
3 116 ms 199 ms 193 ms herva-rdc-gsr3-pos2-0.her.rr.com [24.30.192.141]

4 251 ms 153 ms 122 ms herva-rdc-gsr2-pos4-0.her.rr.com [24.30.192.53]

5 200 ms 170 ms 212 ms herva-rdc-gsr1-pos1-0.her.rr.com [24.30.192.26]

6 118 ms 198 ms 123 ms iar2-sonet2-3-0-0.Restonrst.cw.net [208.173.155.
89]
7 153 ms 166 ms 179 ms acr1-loopback.Restonrst.cw.net [206.24.178.61]
8 187 ms 213 ms 173 ms exodus-communications.Restonrst.cw.net [206.24.1
79.134]
9 177 ms 236 ms 103 ms dcr04-g9-0.stng01.exodus.net [216.33.96.146]
10 125 ms 218 ms 186 ms csr22-ve241.stng01.exodus.net [216.33.98.19]
11 375 ms 99 ms 211 ms 216.35.210.126
12 235 ms 201 ms 128 ms www.yahoo.akadns.net [64.58.76.178]

Trace complete.

HAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHA

reply to COXnightmare

reply to GeneStarwind

reply to COXnightmare
Vamp, you should take the time to do a line quality test. Even though I am now pinging low on servers, it doesn't help that the screen "skips" and "warps" often, a sure sign of packet loss. Damn, if it ain't ass ping, then it's sucky ass packet loss.

reply to COXnightmare
At least you're getting low pings; I still get 170ms latencies after 10:00am weekends/4:00pm weekdays.

Ntgreat: I'm sure you already know this, but don't expect to be seeing those good pings for long. It's happened dozens of times; good connection for a few days, followed by even worse-than-before latency/speed. But for the time being, I suggest lowering your RWIN to fix your packet loss issue, so you can get the most out this temporary speed boost.

reply to ntgreat
I have a fucking CL_FlushEntityPacket warning when I play CS or Date of Defeat as well. I cannot play. It stops there and won't move and get kicked off. This COX is just pure shit. It's unbearable. I can't stand anymore! Ahrrrr...Sigh...

reply to COXnightmare
Live in Fairfax? Want a good internet connection? Want something easier to install than DSL? Out of range of DSL? MOVE!!

reply to COXnightmare
Hey,

I just set up a DLink router & now have 3 PCs using the cable modem signal -- does that typically cause each PC to lose a little bandwith and run slower?

Just curious, it does not seem to be any worse than when I just had the one PC running off the cable modem.

reply to GeneStarwind
»www.speedguide.net/Cable_modems/···es.shtml

Has anyone used these registry patches and tweeks -- do they really help? or make a difference?

As far as backing up your registry INI file, can I just copy & rename the copy reg_backup or something & then apply the patch -- if something goes wrong then just rename the backup back to 'registry.ini' & it will be the same as before?

That is a silly question I know, but nothing worse than messing up your whole sys trying something new.
-
-

According to a few people's tracerts above, I did a tracert to there 1st hop (not 10.x.x.x ip) at 9pm
Tracing route to 24.28.222.2 over a maximum of 30 hops

1 23 ms 32 ms 39 ms 10.41.128.1
2 56 ms 15 ms 14 ms 24.29.98.141
3 30 ms 59 ms 43 ms 24.29.98.9
4 73 ms 63 ms 52 ms 24.29.98.225
5 62 ms 54 ms 62 ms 66.185.137.9
6 15 ms 12 ms 23 ms 66.185.137.1
7 23 ms 48 ms 86 ms 66.185.152.97
8 58 ms 23 ms 66 ms 66.185.152.106
9 64 ms 47 ms 75 ms 66.185.140.130
10 25 ms 65 ms 28 ms 66.185.140.142
11 20 ms 17 ms 52 ms 24.30.192.54
12 22 ms 70 ms 36 ms 24.28.222.2

Tracing route to 24.28.222.1 over a maximum of 30 hops

1 48 ms 18 ms 11 ms 10.41.128.1
2 11 ms 27 ms 10 ms 24.29.98.141
3 23 ms 24 ms 46 ms 24.29.98.9
4 12 ms 60 ms 42 ms 24.29.98.225
5 62 ms 59 ms 32 ms 66.185.137.9
6 69 ms 104 ms 23 ms 66.185.137.1
7 25 ms 39 ms 62 ms 66.185.152.97
8 20 ms 38 ms 39 ms 66.185.152.106
9 75 ms 40 ms 96 ms 66.185.140.130
10 63 ms 61 ms 48 ms 66.185.140.142
11 16 ms 40 ms 21 ms 24.30.192.54
12 19 ms 26 ms 29 ms 24.30.192.142
13 15 ms 73 ms 49 ms 24.28.222.1

Tracing route to 24.28.223.38 over a maximum of 30 hops

1 56 ms 53 ms 36 ms 10.41.128.1
2 12 ms 19 ms 20 ms 24.29.98.141
3 44 ms 56 ms 39 ms 24.29.98.9
4 9 ms 58 ms 15 ms 24.29.98.225
5 52 ms 12 ms 17 ms 66.185.137.9
6 49 ms 10 ms 54 ms 66.185.137.1
7 19 ms 26 ms 56 ms 66.185.152.97
8 15 ms 71 ms 31 ms 66.185.152.106
9 49 ms 63 ms 66 ms 66.185.140.130
10 19 ms 89 ms 25 ms 66.185.140.142
11 17 ms 34 ms 33 ms 24.30.192.54
12 71 ms 27 ms 32 ms 24.30.192.142
13 65 ms 92 ms 63 ms 24.28.222.8
14 97 ms 16 ms 49 ms 24.28.223.66
15 69 ms 70 ms 48 ms 24.28.223.38

Geez and with these pings I thought I got pissed off, looking at yours, I would have been on DSL in a heartbeat.

reply to COXnightmare
Yeah Gene, I know what you're talking about. Cox does this often by screwing around with ya and giving you a small taste of what a low ping can do. Then they give you ass service again. At least we don't have 6-7 hour outages anymore! Always look on the bright side of life, eh?

Well thing is, I think your connections are bad cause when I ping your servers, there good.

reply to COXnightmare
lafiro86, I'm not sure exactly what you're trying to say. Especially since you decided to omit the node in your traces. Try pinging 10.63.0.109 during the afternoon. All your traces tell me is that everything is fast UP UNTILL our nodes; and well, it just doesn't matter if cox's internal backbone is fast if our connection to it is slow.