| reply to COXnightmare
Re: COX HSI problems, NOVA Only pease, I just cannot watch the same streaming video from my COX connection as I do with no problem from my Speakeasy.net connection at work.
The COX with a 1.5m download speed even cannot stream voice where a 384k Speakeasy.net streams voice with video without interruption.
COX is simply not an internet ISP for broadband experiences.
There should be more to the quality than this shitty packet loss:
 |
|
|
|
| Yeah  I bet satellite is better than Cox in terms of network stability... |
|
| said by I dont have a name:
Yeah I bet satellite is better than Cox in terms of network stability...
Precisely... |
|
jmr50
join:2000-05-14
New York, NY | reply to COXnightmare
Anyone know the ISP-side IP address ranges for cox.net (68.*) people> |
|
| reply to COXnightmare
»/quality/nil/765850 I've had pings like this and last two days. This is just horrible. A guy is coming over friday. |
|
| reply to COXnightmare
More of the same crap from Cox.
2002-05-23 21:23:31 EST: 205 / 103
Your download speed : 205673 bps, or 205 kbps.
A 25.1 KB/sec transfer rate.
Your upload speed : 103896 bps, or 103 kbps.
2 359 ms 522 ms 719 ms 68.100.224.1
3 1021 ms 415 ms 108 ms 68.100.0.1
4 450 ms 384 ms 417 ms 68.100.0.137
5 785 ms 847 ms 681 ms 68.1.1.4
6 655 ms 826 ms 807 ms 68.1.1.3
7 884 ms 918 ms 868 ms 68.1.1.17
8 961 ms 1234 ms 999 ms 68.1.0.24
9 967 ms 763 ms 744 ms 68.1.0.23
10 697 ms 664 ms 883 ms 12.124.234.77
11 1181 ms 915 ms 1267 ms 12.123.9.58
12 1185 ms 1011 ms 350 ms 12.122.11.185
13 326 ms 201 ms 181 ms 12.122.11.238
14 237 ms 298 ms 440 ms 216.32.173.185
15 1386 ms 1143 ms 672 ms 216.33.96.162
16 355 ms 579 ms 1287 ms 216.33.98.19
17 2173 ms 2920 ms 1167 ms 216.35.210.126
18 116 ms 140 ms 152 ms 64.58.76.229
Trace complete. |
|
tsigo
join:2001-10-11
Mclean, VA | reply to COXnightmare
Ok screw this - I've seen better traceroutes on dial-up
code:
(root@tsinix) tsigo $ traceroute dslreports.com
traceroute to dslreports.com (209.123.109.175), 30 hops max, 40 byte packets
1 tsiroute (192.168.0.1) 1.349 ms 1.314 ms 1.317 ms
2 ip68-100-88-1.nv.nv.cox.net (68.100.88.1) 126.442 ms 130.675 ms 118.938 ms
3 ip68-100-88-1.nv.nv.cox.net (68.100.88.1) 301.502 ms ip68-100-0-1.nv.nv.cox.net (68.100.0.1) 134.354 ms 160.616 ms
4 ip68-100-0-137.nv.nv.cox.net (68.100.0.137) 102.280 ms 77.821 ms 205.479 ms
5 68.1.1.4 (68.1.1.4) 91.971 ms 95.153 ms 152.007 ms
6 68.1.1.3 (68.1.1.3) 76.375 ms 122.242 ms 80.061 ms
7 68.1.1.17 (68.1.1.17) 91.429 ms 126.809 ms 97.532 ms
8 nrfkbbrc01-pos0101.rd.hr.cox.net (68.1.0.24) 361.701 ms 131.044 ms 199.437 ms
9 lkhnbbrc01-pos0102.rd.at.cox.net (68.1.0.8) 116.098 ms 148.307 ms 132.876 ms
10 POS1-0.hsipaccess1.Atlanta1.Level3.net (209.246.169.5) 190.620 ms 241.757 ms 177.279 ms
11 ge-6-2-0.mp2.Atlanta1.level3.net (64.159.3.77) 227.416 ms 223.325 ms 252.706 ms
12 so-3-0-0.mp1.NewYork1.Level3.net (64.159.1.41) 205.545 ms 258.031 ms 233.391 ms
13 gige6-1.ipcolo1.NewYork1.Level3.net (64.159.17.67) 264.508 ms 293.720 ms 227.002 ms
14 pos11-0.hsipaccess1.Newark1.Level3.net (209.244.12.182) 232.436 ms 214.974 ms 224.604 ms
15 nac-level3.nac.net.156.64.in-addr.arpa (64.156.0.6) 203.220 ms 171.894 ms 198.275 ms
16 a9-0-0-152.msfc1.oct.nac.net (209.123.11.237) 208.551 ms 233.214 ms 196.688 ms
17 www.dslreports.com (209.123.109.175) 159.891 ms 273.232 ms 193.783 ms
|
|
ntgreat
join:2001-08-24
Springfield, VA | reply to COXnightmare
Yikes! I got the conversion "package" about 2 weeks ago and I'm hesitent to switch over. From what I've been reading, I'll basically have the same quality connection as on RR. Is that true? It has been semi-solid for a little bit, but I'm worried that it'll go down the crapper once I "convert". Hmm... |
|
| Your conversion has to do only with email, web space and local info. That's it. Your network will be still there with the same RR until COX switch you to COX.net whatever that means. |
|
tsigo
join:2001-10-11
Mclean, VA | reply to COXnightmare
Trust me, I'd give anything to go back to RR. |
|
| reply to COXnightmare
Tracing route to www.yahoo.akadns.net [66.218.71.87]
over a maximum of 30 hops:
1 10 ms 10 ms 10 ms 192.168.2.1
2 20 ms 20 ms 40 ms ip68-100-224-1.nv.nv.cox.net [68.100.224.1]
3 20 ms 20 ms 40 ms ip68-100-0-1.nv.nv.cox.net [68.100.0.1]
4 60 ms 30 ms 30 ms ip68-100-0-137.nv.nv.cox.net [68.100.0.137]
5 40 ms 20 ms 30 ms 68.1.1.6
6 70 ms 50 ms 60 ms 68.1.1.17
7 30 ms 30 ms 50 ms nrfkbbrc01-pos0101.rd.hr.cox.net [68.1.0.24]
8 71 ms 60 ms 40 ms lkhnbbrc01-pos0102.rd.at.cox.net [68.1.0.8]
9 100 ms 60 ms 60 ms POS1-0.hsipaccess1.Atlanta1.Level3.net [209.246.
169.5]
10 50 ms 50 ms 40 ms POS-10.hsipaccess1.Atlanta1.Level3.net [209.246.169.5]
11 * ip68-100-224-1.nv.nv.cox.net [68.100.224.1] reports: Destination net unreachable.
Trace complete.
Tracing route to www.google.com [216.239.51.101]
over a maximum of 30 hops:
1 10 ms 10 ms 10 ms 192.168.2.1
2 40 ms 30 ms 50 ms ip68-100-224-1.nv.nv.cox.net [68.100.224.1]
3 70 ms 20 ms 40 ms ip68-100-0-1.nv.nv.cox.net [68.100.0.1]
4 80 ms 60 ms 120 ms ip68-100-0-137.nv.nv.cox.net [68.100.0.137]
5 21 ms 40 ms 20 ms 68.1.1.4
6 30 ms 90 ms 30 ms 68.1.1.3
7 40 ms 20 ms 20 ms 68.1.1.17
8 ip68-100-224-1.nv.nv.cox.net [68.100.224.1] reports: Destination net unreachable.
Trace complete.
It's around 1:20AM ... looks like Cox messed up even worse... |
|
tsigo
join:2001-10-11
Mclean, VA | reply to COXnightmare
»/quality/nil/766361
What the hell is the deal with the last 3 hops? |
|
| reply to COXnightmare
said by tsigo:
»/quality/nil/766361
What the hell is the deal with the last 3 hops?
That looks terrible, man. I forgot to post my ping plotter results from last night. It was horrible too. I'll do it tonight because it's gonna be terrible tonight too:( |
|
| reply to COXnightmare
It's no surprise to most of you NoVA Cox users out there.. but Cox seems to be getting worse by everyday. They seem
to play around with their so-called Cox HSI... to mess it up.
Tracing route to www.google.com [216.239.51.101]
over a maximum of 30 hops:
1 140 ms 90 ms 90 ms ip68-100-224-1.nv.nv.cox.net [68.100.224.1]
2 120 ms 70 ms 51 ms ip68-100-0-1.nv.nv.cox.net [68.100.0.1]
3 50 ms 50 ms 90 ms ip68-100-0-137.nv.nv.cox.net [68.100.0.137]
4 70 ms 40 ms 50 ms 68.1.1.4
5 60 ms 50 ms 90 ms 68.1.1.3
6 70 ms 90 ms 100 ms 68.1.1.17
7 80 ms 90 ms 50 ms nrfkbbrc01-pos0101.rd.hr.cox.net [68.1.0.24]
8 70 ms 30 ms 41 ms nrfkbbrc02-pos0100.rd.hr.cox.net [68.1.0.23]
9 50 ms 120 ms 100 ms 12.124.234.77
10 50 ms 40 ms 60 ms gbr5-p80.wswdc.ip.att.net [12.123.9.58]
11 60 ms 70 ms 80 ms tbr2-p013401.wswdc.ip.att.net [12.122.11.185]
12 50 ms 40 ms 60 ms ggr1-p3100.wswdc.ip.att.net [12.122.11.238]
13 50 ms 60 ms 61 ms ibr01-p5-0.stng01.exodus.net [216.32.173.185]
14 20 ms 51 ms 50 ms bbr02-g8-0.stng01.exodus.net [216.33.99.82]
15 60 ms 60 ms 40 ms bbr02-p4-0.stng02.exodus.net [209.185.9.2]
16 50 ms 70 ms 100 ms dcr02-g2-0.stng02.exodus.net [216.109.66.2]
17 30 ms 60 ms 30 ms csr11-ve242.stng02.exodus.net [216.109.66.99]
18 30 ms 70 ms 50 ms 216.109.88.218
19 30 ms 30 ms 40 ms vani1-2-2.net.google.com [216.239.47.65]
20 50 ms 40 ms 80 ms core2-1-1.iad.net.google.com [216.239.48.149]
21 60 ms 50 ms 80 ms core1-3-4.iad.net.google.com [216.239.48.218]
22 60 ms 30 ms 50 ms abni2-1-1.net.google.com [216.239.47.82]
23 * ip68-100-224-1.nv.nv.cox.net [68.100.224.1] reports: Destination net unreachable.
Trace complete.
"reasonable" ping.. bad packet loss.. slow download/upload.. reroutes to gateway(?)... well now not only is it impossible to play games online, it's almost impossible to surf websites. Websites timeout/takes a few seconds to few minutes to load up. Good job Cox! |
|
| ...impossible to surf websites. Websites timeout/takes a few seconds to few minutes to load up. Good job Cox!:(.....
I think that COX should try to focus on more messing up their network. That might work reversely.lol
|
|
| reply to COXnightmare
the cox guy that came today said that my speed problem was just because of their ongoing fiber upgrage. But now my speed seems to be really good.
Tracing route to www.google.com [216.239.51.100]
over a maximum of 30 hops:
1 31 ms 22 ms 15 ms ip68-100-88-xxx.nv.nv.cox.net [68.100.88.xxx]
2 53 ms 53 ms 38 ms ip68-100-0-1.nv.nv.cox.net [68.100.0.1]
3 74 ms 43 ms 71 ms ip68-100-0-137.nv.nv.cox.net [68.100.0.137]
4 22 ms 18 ms 27 ms 68.1.1.4
5 20 ms 15 ms 30 ms 68.1.1.3
6 18 ms 32 ms 19 ms 68.1.1.17
7 33 ms 33 ms 60 ms nrfkbbrc01-pos0101.rd.hr.cox.net [68.1.0.24]
8 51 ms 46 ms 41 ms nrfkbbrc02-pos0100.rd.hr.cox.net [68.1.0.23]
9 41 ms 45 ms 26 ms 12.124.234.77
10 24 ms 37 ms 34 ms gbr5-p80.wswdc.ip.att.net [12.123.9.58]
11 39 ms 64 ms 49 ms tbr2-p013401.wswdc.ip.att.net [12.122.11.185]
12 32 ms 23 ms 52 ms ggr1-p3100.wswdc.ip.att.net [12.122.11.238]
13 35 ms 34 ms 64 ms ibr01-p5-0.stng01.exodus.net [216.32.173.185]
14 33 ms 47 ms 36 ms bbr01-g3-0.stng01.exodus.net [216.33.96.147]
15 39 ms 37 ms 27 ms bbr01-p4-0.stng02.exodus.net [209.1.169.198]
16 39 ms 43 ms 70 ms dcr02-g6-0.stng02.exodus.net [216.109.66.18]
17 40 ms 29 ms 25 ms csr11-ve242.stng02.exodus.net [216.109.66.99]
18 29 ms 47 ms 28 ms 216.109.88.218
19 56 ms 40 ms 26 ms vani1-2-2.net.google.com [216.239.47.65]
20 53 ms 29 ms 54 ms core2-1-1.iad.net.google.com [216.239.48.149]
21 30 ms 27 ms 104 ms core1-3-4.iad.net.google.com [216.239.48.218]
22 27 ms 30 ms 48 ms abni2-1-1.net.google.com [216.239.47.82]
23 47 ms 37 ms 42 ms abbi1-1-1.net.google.com [216.239.47.102]
24 56 ms 39 ms 29 ms www.google.com [216.239.51.100]
Trace complete.
WOW , they fixed somthing yesterday. |
|
| reply to COXnightmare
What the f... is this packet loss thing?
COX just cannot keep everything in harmony. If you got a good ping, you got a terrible packet loss. If you got a good download, you have a terrible ping. Or if you have a special bonus from work, you have a terrible ping, slow download and severe packet loss. Either way you are just screwed with COX. OK. I'm not out of mind. Here is my packet loss (Please, analyze this if there is anyone from COX):
 |
|
ntgreat
join:2001-08-24
Springfield, VA | reply to COXnightmare
Damn nice ping though. Too bad packet loss will kill ya in multiplay. Sigh... |
|
| reply to COXnightmare
4 of the 6 hops that are experiencing Packet Loss are out of Cox's control. |
|
| said by BillRoland:
4 of the 6 hops that are experiencing Packet Loss are out of Cox's control.
Then COX has this peering problems. COX and this atdn (and level3) are competing for packet loss. |
|
