| reply to COXnightmare
Re: COX HSI problems, NOVA Only pease, "COX and this atdn (and level3) are competing for packet loss."
I gotta give the gold medal to Cox for their superbly high latency and packet loss rate.  It's also possible that Cox is just being greedy and not paying enough to have more backbone bandwidth. |
|
| reply to COXnightmare
atdn.net would be the Aol Timewarner Data Network, hence, ATDN. You're on Road Runner, peering isn't Cox's problem, its Road Runner's. On Cox.net, it is an entirely different story, because it is Cox's responsibility to provide decent peering.
--
"Do your duty in all things. You cannot do more. You should never wish to do less." Robert E. Lee |
|
| reply to COXnightmare
Precisely why we are getting such mediocre service. |
|
|
|
| reply to COXnightmare
Well if you are getting mediocre service on Cox.net, then that's Cox's problem. If Road Runner was giving you mediocre service (as the Ping Plots show), then that really is Time Warner's problem, at least as it pertains to atdn.net (and in reality, anything that doesn't have a cox.rr.com in it).
--
"Do your duty in all things. You cannot do more. You should never wish to do less." Robert E. Lee |
|
| reply to COXnightmare
The service was already quite mediocre with Roadrunner, but it was significantly better than Cox HSI. |
|
| said by GeneStarwind:
The service was already quite mediocre with Roadrunner, but it was significantly better than Cox HSI.
LOL! |
|
| reply to GeneStarwind
Tracing route to www.google.com [216.239.39.101]
over a maximum of 30 hops:
1 80 ms 100 ms 90 ms ip68-100-224-1.nv.nv.cox.net [68.100.224.1]
2 100 ms 130 ms 100 ms ip68-100-0-1.nv.nv.cox.net [68.100.0.1]
3 110 ms 190 ms 90 ms ip68-100-0-137.nv.nv.cox.net [68.100.0.137]
4 100 ms 160 ms 130 ms 68.1.1.4
5 150 ms 50 ms 70 ms 68.1.1.3
6 140 ms 111 ms 90 ms 68.1.1.17
7 80 ms 90 ms 80 ms nrfkbbrc01-pos0101.rd.hr.cox.net [68.1.0.24]
8 71 ms 120 ms 80 ms nrfkbbrc02-pos0100.rd.hr.cox.net [68.1.0.23]
9 90 ms 81 ms 60 ms 12.124.234.77
10 40 ms 50 ms 50 ms gbr5-p80.wswdc.ip.att.net [12.123.9.58]
11 70 ms 50 ms 61 ms tbr2-p013401.wswdc.ip.att.net [12.122.11.185]
12 30 ms 60 ms 160 ms ggr1-p3100.wswdc.ip.att.net [12.122.11.238]
13 120 ms 70 ms 90 ms ibr01-p5-0.stng01.exodus.net [216.32.173.185]
14 60 ms 50 ms 30 ms bbr01-g9-0.stng01.exodus.net [216.33.99.97]
15 190 ms 80 ms 80 ms bbr01-p4-0.stng02.exodus.net [209.1.169.198]
16 70 ms 101 ms 80 ms dcr01-g2-0.stng02.exodus.net [216.109.66.1]
17 70 ms 90 ms 201 ms csr11-ve242.stng02.exodus.net [216.109.66.99]
18 90 ms 50 ms 50 ms 216.109.88.218
19 40 ms 61 ms 50 ms dcbi2-1-1.net.google.com [216.239.47.54]
21 110 ms 40 ms 40 ms www.google.com [216.239.39.101]
Trace complete.
Tracing route to www.yahoo.akadns.net [66.218.71.81]
over a maximum of 30 hops:
1 10 ms 50 ms 20 ms ip68-100-224-1.nv.nv.cox.net [68.100.224.1]
2 30 ms 60 ms 20 ms ip68-100-0-1.nv.nv.cox.net [68.100.0.1]
3 10 ms 30 ms 30 ms ip68-100-0-137.nv.nv.cox.net [68.100.0.137]
4 30 ms 50 ms 70 ms 68.1.1.4
5 80 ms 121 ms 40 ms 68.1.1.3
6 50 ms 40 ms 60 ms 68.1.1.17
7 30 ms 60 ms 60 ms nrfkbbrc01-pos0101.rd.hr.cox.net [68.1.0.24]
8 110 ms 80 ms 61 ms lkhnbbrc01-pos0102.rd.at.cox.net [68.1.0.8]
9 80 ms 60 ms 40 ms POS1-0.hsipaccess1.Atlanta1.Level3.net [209.246.
169.5]
10 80 ms 60 ms 70 ms ge-6-2-0.mp1.Atlanta1.level3.net [64.159.3.69]
11 111 ms 160 ms 130 ms so-2-0-0.mp1.SanJose1.Level3.net [209.247.9.114]
12 90 ms 171 ms 110 ms gige9-0.ipcolo4.SanJose1.Level3.net [64.159.2.10
]
13 180 ms 191 ms 120 ms cust-int.level3.net [64.152.69.18]
14 171 ms 400 ms 221 ms ge-1-3-0.msr1.pao.yahoo.com [216.115.100.150]
15 160 ms 160 ms 140 ms vl16.bas1.scd.yahoo.com [66.218.64.146]
16 220 ms 130 ms 121 ms w2.scd.yahoo.com [66.218.71.81]
Trace complete.
Looks like Cox gateway and Level3 (Cox's backbone provider?) are the source of one of many problems... |
|
| reply to COXnightmare
Hehehehehe...the record broken!!! The ping to my first hop went over10,000ms!!! WOW!!! But, unfortunately I couldn't record. Sorry not to show it to you. And it took two hours to post this message. Hehehehehe...I think I'm going grazy now hehehehehehehehehehehehehehe...
 |
|
| My traceroute from earlier post shows about average ping.. when there's no packet loss. anyways.. Ouch! I thought my pings were bad...I usually get from 80ms to over 300ms to dslreports.com. If I can remember right... Cox said it would offer similar service as RoadRunner and take about a month from May 1st to complete transtion of RoadRunner customers over to them... now it's few days away from June, I don't see any improvement or at least same/similar level of service quality, but it looks like other NoVA Cox HSI users and I are getting THE WORST internet service. |
|
| reply to COXnightmare
I've only seen a significant decline in both service and tech support. The other day I was asking them about the latency issue with gaming (200ms avg, 2000ms ping spikes every 10 minutes), and I was told something like "Well, Cox does not support online gaming. But if you are having any problems with latency during web surfing, we can help you on that." I don't think there's even a need to point out the blatant contradiction in that. They really should concentrate more on the quality of the tech support, rather than quantity, and start realizing that not all of us are solely web surfers. |
|
| reply to COXnightmare
Getting good pings now though, but I usually begin to see tripple-digit latency at around 10:00-10:30 |
|
| Not sure about others, but I get intermittent high ping/lag spikes. For a few minutes I get reasoably ok ping then I get high ping. It seemed like constant (after 10-20minutes of good ping then high ping) at first, but it now varies time to time. I called Cox about this many times, but they just won't buy it because "everything looks good" from them. So it looks like Cox will never be able to fix problems since they don't know/want to track down the source(s) of problems... |
|
ntgreat
join:2001-08-24
Springfield, VA | reply to COXnightmare
What is that command to ping a site like 50 times and it calculates the amount of packet loss? NE1? |
|
| said by ntgreat:
What is that command to ping a site like 50 times and it calculates the amount of packet loss? NE1?
ping xxx.xxx.xxx.xxx -n 50 |
|
 PyrionLiquid Metal Nanomorph
join:2001-12-01
Poway, CA
kudos:1 | Add "-l 1500" to that to get a more reasonable idea of packet loss and pings. 32-byte packets don't fairly judge the quality of the network involved, especially when it comes to gaming where you're sending packets with much larger amounts of information.
--
Computer science is like sewer repair -- It pays so well because nobody wants to do it. |
|
tsigo
join:2001-10-11
Mclean, VA | reply to COXnightmare
code:
(root@tsinix) tsigo $ traceroute www.dslreports.com
traceroute to dslreports.com (209.123.109.175), 30 hops max, 40 byte packets
1 tsiroute (192.168.0.1) 39.564 ms 1.385 ms 1.318 ms
2 ip68-100-88-1.nv.nv.cox.net (68.100.88.1) 196.429 ms 100.817 ms 99.580 ms
3 ip68-100-0-1.nv.nv.cox.net (68.100.0.1) 100.549 ms 86.512 ms 89.197 ms
4 ip68-100-0-137.nv.nv.cox.net (68.100.0.137) 93.788 ms 125.288 ms 91.590 ms
5 68.1.1.4 (68.1.1.4) 89.599 ms 107.281 ms 113.012 ms
6 68.1.1.3 (68.1.1.3) 115.684 ms 135.803 ms 164.798 ms
7 68.1.1.17 (68.1.1.17) 133.030 ms 184.581 ms 92.247 ms
8 nrfkbbrc01-pos0101.rd.hr.cox.net (68.1.0.24) 82.992 ms 98.382 ms 148.946 ms
9 lkhnbbrc01-pos0102.rd.at.cox.net (68.1.0.8) 121.613 ms 93.249 ms 168.553 ms
10 POS1-0.hsipaccess1.Atlanta1.Level3.net (209.246.169.5) 424.209 ms 148.453 ms 122.883 ms
11 ge-6-2-0.mp2.Atlanta1.level3.net (64.159.3.77) 110.735 ms 206.894 ms 132.449 ms
12 so-3-0-0.mp1.NewYork1.Level3.net (64.159.1.41) 155.960 ms 131.991 ms 142.695 ms
13 gige6-1.ipcolo1.NewYork1.Level3.net (64.159.17.67) 94.171 ms 167.089 ms 175.835 ms
14 pos11-0.hsipaccess1.Newark1.Level3.net (209.244.12.182) 130.175 ms 152.332 ms 194.989 ms
15 nac-level3.nac.net.156.64.in-addr.arpa (64.156.0.6) 100.936 ms 128.674 ms 135.152 ms
16 a9-0-0-152.msfc1.oct.nac.net (209.123.11.237) 164.351 ms 112.010 ms 87.846 ms
17 www.dslreports.com (209.123.109.175) 86.997 ms 114.035 ms 146.693 ms
Cox pings aren't great, but once it hits Level3 it goes to hell. |
|
ntgreat
join:2001-08-24
Springfield, VA | reply to COXnightmare
As we can see, Cox get's horrible in the evenings. Sigh... gaming is not an option with Cox. |
|
ip_vic
join:2002-02-18
Boston, MA | reply to tsigo
said by tsigo:
Cox pings aren't great, but once it hits Level3 it goes to hell.
Went to lg.level3.net. Noticed that the return path back to Cox from level3 in atl1 is asymetric. Level3 sends the traffic back to Cox through ATT in wdc. ??
I wonder if that's on purpose.
Tracing the route to ip68-100-88-1.nv.nv.cox.net (68.100.88.1)
1 so-4-0-0.mp2.Atlanta1.Level3.net (64.159.3.66) 0 msec 0 msec 0 msec
2 so-3-0-0.mp1.Washington1.Level3.net (64.159.0.229) 16 msec 12 msec 16 msec
3 gigabitethernet7-1.core1.Washington1.Level3.net (64.159.18.69) 12 msec 16 msec 12 msec
4 ggr1-p360.wswdc.ip.att.net (209.244.219.158) 20 msec 12 msec 12 msec
5 tbr2-p012701.wswdc.ip.att.net (12.122.11.237) 24 msec 40 msec 16 msec
6 gbr5-p40.wswdc.ip.att.net (12.122.11.186) 16 msec 12 msec 16 msec
7 gar2-p360.wswdc.ip.att.net (12.123.9.57) 16 msec 12 msec 16 msec
8 12.124.234.78 20 msec 20 msec 16 msec
9 nrfkbbrc01-pos0100.rd.hr.cox.net (68.1.0.22) [AS 22773 {}] 16 msec 20 msec 16 msec
10 nrfkdsrc01-pos0901.rd.hr.cox.net (68.1.0.25) [AS 22773 {}] 16 msec 20 msec 16 msec
11 68.1.1.16 [AS 22773 {}] 20 msec 24 msec 20 msec
12 68.1.1.7 [AS 22773 {}] 24 msec 20 msec 24 msec
13 ip68-100-0-150.nv.nv.cox.net (68.100.0.150) [AS 22773 {}] 20 msec 24 msec 24 msec
14 ip68-100-88-1.nv.nv.cox.net (68.100.88.1) [AS 22773 {}] 24 msec 24 msec 24 msec
I would guess that during the traceroute there was an issue on the peering link from level3-att or something else along that return path causing the higher RTTs. Looks clear now.
regards
-V |
|
ip_vic
join:2002-02-18
Boston, MA | ...as a matter of fact. The routing has switched. Traffic now going over local level3-cox interface:
Tracing the route to ip68-100-88-1.nv.nv.cox.net (68.100.88.1)
1 so-4-0-0.mp1.Atlanta1.Level3.net (64.159.3.62) 0 msec
so-4-0-0.mp2.Atlanta1.Level3.net (64.159.3.66) 0 msec
so-4-0-0.mp1.Atlanta1.Level3.net (64.159.3.62) 0 msec
2 gigabitethernet11-1.hsipaccess1.Atlanta1.Level3.net (64.159.3.18) 4 msec
gigabitethernet10-2.hsipaccess1.Atlanta1.Level3.net (64.159.3.70) 0 msec
gigabitethernet11-1.hsipaccess1.Atlanta1.Level3.net (64.159.3.18) 0 msec
3 unknown.Level3.net (209.246.169.6) 4 msec 0 msec 0 msec
4 nrfkbbrc01-pos0102.rd.hr.cox.net (68.1.0.9) [AS 22773 {}] 16 msec 16 msec 12 msec
5 nrfkdsrc01-pos0901.rd.hr.cox.net (68.1.0.25) [AS 22773 {}] 16 msec 12 msec 16 msec
6 68.1.1.16 [AS 22773 {}] 16 msec 20 msec 16 msec
7 68.1.1.7 [AS 22773 {}] 16 msec 20 msec 16 msec
8 ip68-100-0-150.nv.nv.cox.net (68.100.0.150) [AS 22773 {}] 16 msec 20 msec 20 msec
9 ip68-100-88-1.nv.nv.cox.net (68.100.88.1) [AS 22773 {}] 20 msec 20 msec 20 msec
...maybe someone is watching. :)
regards
-V |
|
| I went to lg.level3.net and did traceroute from Atlanta, GA... doesn't looks like anyone's watching to solve problem..
Tracing the route to ip68-100-231-*.nv.nv.cox.net (68.100.231.*)
1 so-4-0-0.mp1.Atlanta1.Level3.net (64.159.3.62) 0 msec 0 msec 0 msec
2 gigabitethernet10-2.hsipaccess1.Atlanta1.Level3.net (64.159.3.70) 0 msec 0 msec 0 msec
3 unknown.Level3.net (209.246.169.6) 4 msec 4 msec 0 msec
4 nrfkbbrc01-pos0102.rd.hr.cox.net (68.1.0.9) [AS 22773 {}] 16 msec 12 msec 12 msec
5 nrfkdsrc01-pos0901.rd.hr.cox.net (68.1.0.25) [AS 22773 {}] 12 msec 12 msec 16 msec
6 68.1.1.16 [AS 22773 {}] 16 msec 20 msec 16 msec
7 68.1.1.7 [AS 22773 {}] 16 msec 16 msec 16 msec
8 ip68-100-0-150.nv.nv.cox.net (68.100.0.150) [AS 22773 {}] 20 msec 20 msec 16 msec
9 vlan31.l3nahqdcmsf05.l3.com (10.1.0.1) 20 msec 20 msec 20 msec
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * * |
|
