Re: [Nolug] Request for a Cox user...

Jeremy (mailing list box) wrote:

>
> Hop 11 (nv.cox.net) refers to the Northern Virginia market (which
> supposedly became dc.cox.net)... I know the nv.cox.net name very well

ooo. good catch! found this breakdown of some of cox's naming conventions for
host/domain names.
http://www.broadbandreports.com/faq/5662:

> Also, assuming that nv.cox.net is in Nevada... There should be more
> than a 1 or 2 ms increase in latency between DFW and Nevada.
> Physics... :)

Or between Dallas and NoVA.

10 dalsbbrj01-so301.r2.dl.cox.net (68.1.0.157) 27 ms 19 ms 25 ms
11 ashbbbpc01gex0200a100.r2.nv.cox.net (68.105.30.30) 21 ms 19 ms 24 ms
12 UNKNOWN-216-115-104-111.yahoo.com (216.115.104.111) 40 ms 21 ms 20 ms

My guess is that #11 is not, in fact, in northern VA, but in a data center in
Dallas. Perhaps the "pc" in the hostname represents "peering connection" or
something similar. Perhaps the box in questin in Dallas also has a private
connection back to ashburn, VA. It seems likely that Yahoo resides at the same
data center; there's no visible intermediate hop from Cox through another
provider to Yahoo.

>
> I just wanted to see what latency I should expect... I'm guessing the
> 20ms difference won't matter that much in the general scheme of things,
> but I was just curious to see if their routing had changed and what
> expect. The route could be much, much worse and that's mainly what I
> was checking for...

-- 
Scott Harney <scotth@scottharney.com>
"Asking the wrong questions is the leading cause of wrong answers"
gpg key fingerprint=7125 0BD3 8EC4 08D7 321D CEE9 F024 7DA6 0BC7 94E5
___________________
Nolug mailing list
nolug@nolug.org