ip_vic
join:2002-02-18
Boston, MA | reply to I dont have a name
Re: COX HSI problems, NOVA Only pease, said by I dont have a name:
I went to lg.level3.net and did traceroute from Atlanta, GA... doesn't looks like anyone's watching to solve problem.. 
What are you tracing to? That's a DNS issue. Traceroute ends within Cox. Last hop resolves to an l3.com name but I'll bet that's only because the looking glass has private address space and access to some type of internal DNS server that happens to be resolving the rfc1918 address that is on the Cox network.
regards
-V |
|
| reply to COXnightmare
I live on the border of herndon and sterling and just got switched over to cox network from rr. First thing i did was run a tracert, and I noticed ping timeouts every 4-5 hops or so. No matter where I pinged too. Has anyone else noticed this? |
|
ip_vic
join:2002-02-18
Boston, MA | said by wtwt:
I live on the border of herndon and sterling and just got switched over to cox network from rr. First thing i did was run a tracert, and I noticed ping timeouts every 4-5 hops or so. No matter where I pinged too. Has anyone else noticed this?
Can you post a sample of your results?
regards
-V |
|
| reply to COXnightmare
As you all know Oklahoma City, OK users are having similar problems.. I read some of the posts in their thread and noticed they go through level3 also... so I'm quite certain that the problem lies within Cox gateways and level3.
Anyways, here's yet another traceroute... this is getting boring I'm sure...
Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:
1 10 ms 10 ms 10 ms 192.168.2.1
2 50 ms 70 ms 20 ms ip68-100-224-1.nv.nv.cox.net [68.100.224.1]
3 70 ms 160 ms 50 ms ip68-100-0-1.nv.nv.cox.net [68.100.0.1]
4 141 ms 220 ms 80 ms ip68-100-0-149.nv.nv.cox.net [68.100.0.149]
5 70 ms 160 ms 130 ms 68.1.1.6
6 110 ms 210 ms 81 ms 68.1.1.17
7 100 ms 100 ms 320 ms nrfkbbrc01-pos0101.rd.hr.cox.net [68.1.0.24]
8 110 ms 120 ms 110 ms lkhnbbrc01-pos0102.rd.at.cox.net [68.1.0.8]
9 161 ms 230 ms 130 ms POS1-0.hsipaccess1.Atlanta1.Level3.net [209.246.
169.5]
10 100 ms 80 ms 110 ms ge-6-1-0.mp2.Atlanta1.Level3.net [64.159.3.17]
11 160 ms 120 ms 120 ms so-3-0-0.mp1.NewYork1.Level3.net [64.159.1.41]
12 220 ms 301 ms 110 ms gige6-1.ipcolo1.NewYork1.Level3.net [64.159.17.6
7]
13 220 ms 191 ms 110 ms pos11-0.hsipaccess1.Newark1.Level3.net [209.244.
12.182]
14 131 ms 100 ms 110 ms nac-level3.nac.net.156.64.in-addr.arpa [64.156.0
.6]
15 191 ms 140 ms 410 ms a9-0-0-152.msfc1.oct.nac.net [209.123.11.237]
16 170 ms 180 ms 110 ms www.dslreports.com [209.123.109.175]
Trace complete. |
|
| reply to COXnightmare
See speed test below
[text was edited by author 2002-05-30 12:27:11] |
|
| reply to wtwt
to WTWT:
I just got moved to HSI last night
My pings overall are still low and speed is good, but I have noticed similar behavior that you've described. Some hops will time out completely, others will have a temporary spike to 400ms. Most of my early hops are fine though, it doesn't seem to happen until after I'm outside the nv.nv.cox.net domain. I'm planning on doing more extensive testing later around 5pm to get a worst-case scenario and I'll post results. |
|
| reply to COXnightmare
2002-05-30 12:23:28 EST: 4811 / 7481
Your download speed : 4811647 bps, or 4811 kbps.
A 587.3 KB/sec transfer rate.
Your upload speed : 7481296 bps, or 7481 kbps.
At least this is a tad faster than 56k 
[text was edited by author 2002-05-30 12:28:59] |
|
 LiQiCE
join:2001-05-31
Herndon, VA | reply to COXnightmare
I was working fine for a week or so at around 1500/192 until yesterday ... Since then I have been completely dead. The cable status light on my modem is solid red, which according to the manual means "Locked downstream channel", but I never get a green light which means the modem has synched. I hope I can figure out this problem soon ... Otherwise I'm stuck on Dialup! :-( Any help would be appreciated. (I have an "unsupported" 3Com OfficeConnect DOCSIS modem that was working on Cox HSI for about a week after being switched). |
|
| reply to COXnightmare
I miss RR
The timeout problem i was experiencing stopped occuring day 2 of cox hsi. As u can see, by this tracert which was done at 12:09 am, the speeds are hardly equal to rr: C:\>tracert www.yahoo.com
Tracing route to www.yahoo.akadns.net [66.218.71.84]
over a maximum of 30 hops:
1 79 ms 62 ms 105 ms ip68-100-176-1.nv.nv.cox.net [68.100.176.1]
2 237 ms 38 ms 166 ms ip68-100-1-34.nv.nv.cox.net [68.100.1.34]
3 202 ms 18 ms 62 ms ip68-100-0-137.nv.nv.cox.net [68.100.0.137]
4 27 ms 53 ms 119 ms 68.1.1.4
5 51 ms 35 ms 41 ms 68.1.1.3
6 59 ms 103 ms 71 ms 68.1.1.17
7 82 ms 56 ms 32 ms nrfkbbrc01-pos0101.rd.hr.cox.net [68.1.0.24]
8 64 ms 47 ms 73 ms lkhnbbrc01-pos0102.rd.at.cox.net [68.1.0.8]
9 102 ms 89 ms 49 ms POS1-0.hsipaccess1.Atlanta1.Level3.net [209.246.
169.5]
10 67 ms 101 ms 86 ms ge-6-1-0.mp1.Atlanta1.level3.net [64.159.3.5]
11 240 ms 115 ms 194 ms so-3-0-0.mp2.SanJose1.Level3.net [64.159.1.130]
12 127 ms 122 ms 149 ms gige10-0.ipcolo4.SanJose1.Level3.net [64.159.2.4
2]
13 174 ms * 168 ms cust-int.level3.net [64.152.81.62]
14 259 ms 125 ms 121 ms ge-3-3-0.msr1.pao.yahoo.com [216.115.101.42]
15 161 ms 130 ms 155 ms vl16.bas1.scd.yahoo.com [66.218.64.146]
16 141 ms 131 ms 187 ms w5.scd.yahoo.com [66.218.71.84]
Trace complete.
C:\>
Crap service + Rate increase != Happy customer |
|
sense
join:1999-08-13
Burke, VA | Anyone of you guys know of gaming center around Northern Virginia that will give some low pings? I cant seem to find one after Game Domain closed. |
|
| reply to COXnightmare
Gaming Center? Hmmmm....sorry I never heard of that. |
|
sense
join:1999-08-13
Burke, VA | here is an example of one »www.extranetcafe.com/ but its all the way in Fredricksburg. |
|
| reply to COXnightmare
There used to be one called conquer this over by the watchtower plaza in sterling... u could basically go there they had like 12 computers lined up and play ppl or go online.. think it went out of business tho not sure |
|
ntgreat
join:2001-08-24
Springfield, VA | reply to COXnightmare
Saw the tail end of a channel news 8 story about Cox. Apparently, they have missed the fairfax county board deadline of substantially upgrading the NOVA cable system. Cox sent a letter to the board about the failure and is now waiting for a response.
»www.newschannel8.net/
I couldn't find the story at their website. Maybe someone can find it and post the link here. |
|
ntgreat
join:2001-08-24
Springfield, VA | reply to COXnightmare
Wow, nice packetloss Cox. And it's only 7:34pm. You guys amaze me more and more each day. |
|
| reply to COXnightmare
U think u got it bad? heh. |
|
| reply to sense
There's a place called Music House around the area of Fairfax Circle, and another called Blackout, which is closer to Fairfax city. |
|
|
|
| reply to COXnightmare
1 * * * Request timed out.
2 224 ms 97 ms 90 ms ip68-100-0-1.nv.nv.cox.net [68.100.0.1]
3 277 ms 105 ms 88 ms ip68-100-0-137.nv.nv.cox.net [68.100.0.137]
4 139 ms 147 ms 107 ms 68.1.1.4
5 113 ms 65 ms 137 ms 68.1.1.3
6 135 ms 56 ms 66 ms 68.1.1.17
7 117 ms 138 ms 214 ms nrfkbbrc01-pos0101.rd.hr.cox.net [68.1.0.24]
8 155 ms 151 ms 135 ms lkhnbbrc01-pos0102.rd.at.cox.net [68.1.0.8]
9 142 ms 149 ms 147 ms POS1-0.hsipaccess1.Atlanta1.Level3.net [209.246.
169.5]
10 153 ms 143 ms 152 ms ge-6-1-0.mp2.Atlanta1.Level3.net [64.159.3.17]
11 161 ms 130 ms 166 ms so-3-0-0.mp1.NewYork1.Level3.net [64.159.1.41]
12 121 ms 137 ms 150 ms gige6-1.ipcolo1.NewYork1.Level3.net [64.159.17.6
7]
13 160 ms 168 ms 147 ms pos11-0.hsipaccess1.Newark1.Level3.net [209.244.
12.182]
14 136 ms 136 ms 182 ms nac-level3.nac.net.156.64.in-addr.arpa [64.156.0
.6]
15 156 ms 108 ms 360 ms a9-0-0-152.msfc1.oct.nac.net [209.123.11.237]
16 173 ms 109 ms 114 ms dslreports.com [209.123.109.175]
Trace complete.
And I recall getting pings in the 40-50s all wednesday and thursday night on hl servers. I don't see how I can be getting such abysmal service 1:20pm on a saturday, when I would expect the same amount, or perhaps even a greater amount traffic on a thursday night. So what could possibly explain this? Do they pick random days during the week where they allow customers to benefit from only 30% of their network capacity? I simply can't fabricate an explanation for this complete randomness in network performance.
[text was edited by author 2002-06-01 17:10:39] |
|
| reply to ntgreat
you seem to still have a Road Runner IP. At least your pings are decent. But that packet loss is pretty bad i must say. |
|
| reply to COXnightmare
Actually, I am on Cox HSI, although I wish I were still on RR. |
|
