gravesg
join:2006-12-21
Norfolk, VA
| [VA] ping times Terrible
ok so im playing at my favorite counter-strike server where i normally get pings of 25ms or lower, when last night i noticed i was at 70 and 80.
the server is hosted in NJ (new jersey) on the choopa network. i get there by level 3 from cox.
now im wondering why do i have to goto Okland,CA to get back to chicago then to new jersey.
to add to that nonsense that makes, this happens when i try to get to any site dealing with Level3.
im guessing theres something going on with peering arrangements or whatever.
my original routing went from Hr.cox.net to As.cox.net (as meaning ashburn,va) then to level 3 chicago now what its doing now is plain crazy. PLZ help me guys |
|
jsimmons
Premium,MVM
join:2000-04-24
Falls Church, VA
| I think you'll need to take this up with Cox. As I see it, assumng the "ok.cox.net" means Oklahoma, your packets are now being routed Norfolk to Oklahoma on cox, then, onto Level3 via chicago, then back to Washington, then Newark.That is one helluva round about way to get there. And aside from the packet loss at hop 8 (which could just be ICMP deprioritization), the pings look OK for that wild "trip".
--
"Everything should be made as simple as possible, but not one bit simpler."- Albert Einstein |
|
gravesg
join:2006-12-21
Norfolk, VA
1 edit | the pings look ok is what i thought as well. also cox has some nice fiber lol, but when im in game the feel of it starts feeling sluggish and packet loss occours when im gaming. its not too often but makes it hard to play the game with people skipping around on the screen.
i talked to cox last night and asked for tier 2 support and the tier one said he didn't see a problem on his side, he said it looks all good, it felt like i had a better understanding of the network then he did. thats why i asked for tier 2, but bahh i had hoped the problem would go away with time but nothing yet.
who do i talk to to get this problem solved? my routing insted of OK should be in Ashburn then chi town. |
|
NoVA_CoxUser
Stand back from the cage -- The RF bites
Premium
join:2004-07-06
Alexandria, VA
 ·Cox HSI
1 edit | reply to jsimmons
said by jsimmons  :... As I see it, assuming the "ok.cox.net" means Oklahoma, your packets are now being routed Norfolk to Oklahoma on cox, then, onto Level3 via chicago, then back to Washington, then Newark.That is one helluva round about way to get there. That's what that tracert shows and it sure is one long round trip.
Of course, I-95 north of Stafford's always a problem ... 
Anyway, here's what my trace to the same target looks like:
C:\>tracert choopa.com
Tracing route to choopa.com [64.237.38.178]
over a maximum of 30 hops:
1 1 ms 2 ms 1 ms 192.168.1.1
2 10 ms 11 ms 9 ms ip68-106-96-1.dc.dc.cox.net [68.106.96.1]
3 11 ms 7 ms 7 ms ip68-100-1-145.dc.dc.cox.net [68.100.1.145]
4 17 ms 18 ms 11 ms ip68-100-0-65.dc.dc.cox.net [68.100.0.65]
5 13 ms 10 ms 10 ms mrfddsrj02-ge110.rd.dc.cox.net [68.100.0.149]
6 14 ms 10 ms 15 ms mrfddsrj01-so010.rd.dc.cox.net [68.100.0.129]
7 16 ms 9 ms 9 ms te-3-2.car1.Washington1.Level3.net [4.79.228.61]
8 29 ms 10 ms 17 ms ae-32-52.ebr2.Washington1.Level3.net [4.68.121.62]
9 21 ms 26 ms 18 ms ae-4.ebr2.Newark1.Level3.net [4.69.132.102]
10 18 ms 18 ms 15 ms ae-22-56.car2.Newark1.Level3.net [4.68.99.166]
11 20 ms 17 ms 26 ms CHOOPA-LLC.car2.Newark1.Level3.net [4.79.190.98]
12 18 ms 15 ms 27 ms 0.te1-4.cr1.ewr1.choopa.net [64.237.32.65]
13 17 ms 34 ms 20 ms choopa.com [64.237.38.178]
Trace complete.
C:\>
|
|
gravesg
join:2006-12-21
Norfolk, VA | hmm mine is still going through CA 
anyone know who i need to talk to? |
|
NoVA_CoxUser
Stand back from the cage -- The RF bites
Premium
join:2004-07-06
Alexandria, VA
1 edit | said by gravesg :... mine is still going through CA ... ??? |
|
gravesg
join:2006-12-21
Norfolk, VA
2 edits | CA (cali) lol .. ???
i don't understand why i can't take the dc route you have.
i also thought bgp4 routing made it so this type of routing was impossible.
i hate Oklahoma ....
i did a little research »en.wikipedia.org/wiki/Dynamic_Source_Routing
thats what the DSR means in the names you see in the tracert
my hop apperntly doesn't reconize any other way to get to level 3 |
|
Gamer
join:2006-12-09
Phoenix, AZ | Reaching your destination in 100ms or less is acceptable, 68ms is highly acceptable. There's absolutely nothing wrong with these pings. |
|
gravesg
join:2006-12-21
Norfolk, VA
1 edit | you apparently didn't read what i typed, so ill state it again, not to mention OK. ITS GOING TO OK not around the coner or up a few states. there is a problem with route discovery. you apparently are in denial my friend seeing this as ok. what happens if everything is routed all the way to OK and then back to me. that means other than speed cox has lost it ping edge over verizon here.
60-80ms is okay but when in game this actually feels like 150ms. switching wepons takes forever, and constant lagging.
even 150ms is okay for somethings but while in game my ping is terrible and the lag is crazy, i actaully have to aim in a timely manner in case it lags to still get my kill. |
|
NoVA_CoxUser
Stand back from the cage -- The RF bites
Premium
join:2004-07-06
Alexandria, VA
·Cox HSI
4 edits | said by gravesg : ... ITS GOING TO CA not around the coner or up a few states, my packets are going to the west coast ... Where do you "see" that?
While I do see Oklahoma and Chicago on your route from Tidewater to NJ ... which does seem a bit odd in itself ... where's CA in your OP trace?
(ok.cox.net is in Oklahoma) See »Cox HSI Router Abbreviations »What are the Cox Router Abbreviations? |
|
gravesg
join:2006-12-21
Norfolk, VA
| whoops lol wasn't sure wheather it was Oakland or Oklahoma when i said that LOL
... i sort a feel like a dumb you know what ...
thanks for the abbreviations though they really help map out a picture of the peering points  |
|
NoVA_CoxUser
Stand back from the cage -- The RF bites
Premium
join:2004-07-06
Alexandria, VA
·Cox HSI
4 edits | said by gravesg : ... thanks for the abbreviations though they really help map out a picture of the peering points ... The map on page 2 of this CBS Document might help you even more.
You can easily see how you were routed to an "alternate" peering point (this time in Chicago).
As to why your "normal" Ashburn peering site was [is] not available (keep in-mind that it could also be due to problems w/ the the "other carrier" too) ... or why NYC wasn't the "next best" option ... will likely remain a mystery at our level.
FWIW, I've occasionally seen this sort of routing from NoVA ... only in my case I was routed thru RI to get to the peering point in Chicago.
Whatever the cause of your circuitous route may be, I suspect it's only temporary and will "resolve itself" within a few days. |
|
gravesg
join:2006-12-21
Norfolk, VA
1 edit | sweet man tHANKS
hmm this pretty much answers my question of what cox's peering points are.
i take 0c-192 to OK then oc-48 to chicago ...
hopefully this is resolved in about a week
i can't get to the NY peering point because i can't get to the Ashburn one. i haveto go there first before it'll let me goto NY from my tracerts its always been that way... still though cox has laid down alot of fiber, or are they renting it ?? |
|
NoVA_CoxUser
Stand back from the cage -- The RF bites
Premium
join:2004-07-06
Alexandria, VA
·Cox HSI
4 edits | said by gravesg : ... Cox has laid down alot of fiber, or are they renting it ... I believe it's all (or nearly all) leased capacity from long-haul providers ... although it's operated as-if it were a private network. |
|
gravesg
join:2006-12-21
Norfolk, VA
| WOOT IM BACK TO NORMAL WITHOUT THE ASHBURN HOP, AWESOME
i get there under 20ms now
man cox rules, i guess they were performing network upgrades. |
|
