
how-to block ads
|
|
Share Topic  |
 |
|
|
|
 | reply to COXnightmare
Re: COX Fairfax, VA: The worst ISP in the nation? Tracing route to www.yahoo.akadns.net [64.58.76.179] over a maximum of 30 hops:
1 132 ms 159 ms 120 ms 10.63.0.109 2 213 ms 204 ms 127 ms ffaxvamtc-gsr2-srp0-0.cox.rr.com [24.28.222.2] 3 128 ms 128 ms 72 ms herva-rdc-gsr3-pos2-0.her.rr.com [24.30.192.141]
4 88 ms 92 ms 249 ms herva-rdc-gsr2-pos4-0.her.rr.com [24.30.192.53]
5 136 ms 74 ms 150 ms herva-rdc-gsr1-pos1-0.her.rr.com [24.30.192.26]
6 25 ms 347 ms 130 ms iar2-sonet2-3-0-0.Restonrst.cw.net [208.173.155. 89] 7 98 ms 238 ms 113 ms acr1-loopback.Restonrst.cw.net [206.24.178.61] 8 136 ms 147 ms 197 ms exodus-communications.Restonrst.cw.net [206.24.1 79.134] 9 91 ms 101 ms 82 ms dcr04-g10-0.stng01.exodus.net [216.33.96.162] 10 93 ms 243 ms 182 ms csr22-ve242.stng01.exodus.net [216.33.98.10] 11 272 ms 311 ms 172 ms 216.35.210.126 12 256 ms 108 ms 200 ms www.yahoo.akadns.net [64.58.76.179]
Trace complete.
Well, from thursday through saturday, I had almost flawless service. However, today, as you can see, my pings are nothing to brag about. What I don't understand is why there are these occasional speedups. One day I'll start pinging 30ms to game servers at 8:30 in the evening, and then in 2 days, it'll suddenly get worse than it was before the speed-up. Why can't they just provide decent service without completely screwing it over after only a few days? Is it really that difficult? As for me, I probably wont be seeing ANY decent service for a while. This would definately be a perfect time for DSL. | |  | Your ping time is not good but still better than mine ( I have an average ping time of 300 ms) I don't think they have technology and capability to provide a reliable service. If DSL is available, go for it without a second thought. If you live especially in around Burke, forget COX. Move out or get DSL (Speakeasy or Earthlink). | |  | Tracing route to www.yahoo.akadns.net [64.58.76.222] over a maximum of 30 hops:
1 124 ms 162 ms 158 ms 10.63.0.109 2 21 ms 27 ms 10 ms ffaxvamtc-gsr1-srp0-0.cox.rr.com [24.28.222.1] 3 49 ms 42 ms 91 ms ffaxvamtc-gsr2-srp0-0.cox.rr.com [24.28.222.2] 4 82 ms 42 ms 27 ms herva-rdc-gsr3-pos2-0.her.rr.com [24.30.192.141]
5 111 ms 42 ms 92 ms herva-rdc-gsr2-pos4-0.her.rr.com [24.30.192.53]
6 30 ms 78 ms 32 ms herva-rdc-gsr1-pos1-0.her.rr.com [24.30.192.26]
7 20 ms 59 ms 47 ms iar2-sonet2-3-0-0.Restonrst.cw.net [208.173.155. 89] 8 15 ms 28 ms 27 ms acr1-loopback.Restonrst.cw.net [206.24.178.61] 9 30 ms 13 ms 51 ms exodus-communications.Restonrst.cw.net [206.24.1 79.134] 10 47 ms 20 ms 25 ms dcr04-g6-0.stng01.exodus.net [216.33.99.84] 11 242 ms 93 ms 187 ms csr22-ve242.stng01.exodus.net [216.33.98.10] 12 21 ms 89 ms 72 ms 216.35.210.126 13 59 ms 53 ms 75 ms w1.dcx.yahoo.com [64.58.76.222]
Trace complete.
Right now it isn't so bad (except for the 1st and 11th hops). But I should still be getting 1/3 of that ping. I also hope they do something about the speedcap when/if they finish upgrading. Not that 1500/192 is so bad, but most RR isps provide around 2500/300. In fact, I can't think of any other cable isps (except for Charter) which cap their users at 1500/192 or lower. | |
|