Anyone who knows care to share? Just curious.

This site always seems to have lots of online visitors on at the same time -- and is very quick and responsive to me here in the Midwest.

Any other details (OS & other software) that could be shared would be nice to know.

This is one of the most consistently responsive sites I regularly visit.

Thanks,

Louis

I forget what it is running on, etc. Moving it here so that someone who remembers can reply.

Last time I know, it was running on a Dual P3/500Mhz with 512MB of memory and 9GB SCSI drive(s). The server/bandwith is provided by voxel.net at their above.net (NYC) datacenter. Although I have been wonderring why traceroute to webhostingtalk.com resolves on it being on Above.net San Jose, CA.

cheers,
:beer:

Hey!

It's probably not in CA, since I get a 6ms ping time to www.webhostingtalk.com from NY.

Unless, of course, Above.Net/MFN are keeping some sort of faster-than-light fiber technology a secret. :D

Perhaps Visual Traceroute (or the client you're using) is getting CA from the whois address for the IP block:

Abovenet Communications, Inc. (NETBLK-ABOVENET-4)
50 W. San Fernando St., Suite 1010
San Jose, CA 95113
US


Jason

Software:

Linux (duh!)
Apache 1.3.24
PHP 4.1.2

Hardware:

I dunno

Network:

Abovenet Communications

Originally posted by JayPee
Perhaps Visual Traceroute (or the client you're using) is getting CA from the whois address for the IP block:


No it does not. Usually when this happens, you can recognize it by seeing that the last hop make a sudden jump from, say, NYC to CA and the color of the last hop is purple, not blue.
But try to traceroute webhostingtalk.com from visualroute.visualware.com, it did go through Dallas then San Jose, not even one hop spent in NYC.

cheers,
:beer:

Tracing from NAC to www.webhostingtalk.com:

1 fa0-0.core1.pwebtech.com (209.123.152.1) 0.471 ms
2 pegasus.customer.nac.net (207.99.8.197) 1.907 ms
3 a9-0-1118.msfc1.nyc.nac.net (209.123.11.9) 2.963 ms
4 ny-iix.above.net (198.32.160.22) 3.498 ms
5 so-3-0-1.cr1.lga3.us.mfnx.net (208.185.0.181) 2.557 ms
6 so-5-2-0.cr1.lga1.us.mfnx.net (64.125.30.17) 2.957 ms
7 pos0-0.er1a.lga1.us.mfnx.net (216.200.127.190) 2.593 ms
8 panther.webhostingtalk.com (209.249.55.203) 3.558 ms

Hops 1-3 are Pwebtech/NAC
Hop 4 is NAC to NYIIX
Hop 5 is an MFN core router at Telehouse NY
Hop 6 is an MFN core router at their ISX 111 8th Ave NY
Hop 7 is an MFN edge router at their ISX 111 8th Ave NY
Hop 8 is www.webhostingtalk.com

So, I humbly submit that WHT is hosted at AboveNet/MFN's facility at 111 8th Ave NY. And to get there in 3 milliseconds from NJ? Can't hosted on the west coast (unless of course they are running a second machine out there).

MFN's network info describing their network IDs and locations is at:

http://www.mfn.com/network/ip_networkstatus.shtm


Jason

and here is what I got (Traceroute from VDI):


traceroute to webhostingtalk.com (209.249.55.203), 64 hops max, 40 byte packets
3 pos.core1.nwk.vdi.net (66.78.63.245) 1.831 ms 1.726 ms 1.783 ms
4 f5.ba01.b002894-1.jfk01.atlas.cogentco.com (66.250.4.117) 3.034 ms 2.271 ms 1.961 ms
5 g12-6.core01.jfk01.atlas.cogentco.com (66.28.65.145) 3.208 ms 2.823 ms 2.535 ms
6 p13-0.core02.jfk02.atlas.cogentco.com (66.28.4.121) 2.255 ms 2.199 ms 2.215 ms
7 p14-0.core02.ord01.atlas.cogentco.com (66.28.4.86) 28.884 ms 28.159 ms 28.104 ms
8 p15-0.core01.ord01.atlas.cogentco.com (66.28.4.61) 28.343 ms 28.128 ms 28.247 ms
9 p5-0.core01.sfo01.atlas.cogentco.com (66.28.4.42) 74.102 ms 73.816 ms 73.899 ms
10 p15-0.core02.sfo01.atlas.cogentco.com (66.28.4.70) 74.932 ms 73.893 ms 73.947 ms
11 p6-0.tr1.sfr1.netrail.net (66.28.28.58) 74.317 ms 74.294 ms 74.372 ms
12 ge-2-2-0--0.pr1.SanFrancisco1.CA.us.netrail.net (205.215.12.2) 74.356 ms 74.451 ms 74.425 ms
13 Abovenet1.pr1.SanFancisco1.CA.us.netrail.net (205.215.1.50) 75.062 ms 74.546 ms 74.658 ms
14 so-4-1-0.mpr4.sjc2.us.mfnx.net (208.185.175.161) 74.821 ms 74.621 ms 74.946 ms
15 pos7-0.mpr1.iad1.us.mfnx.net (216.200.127.25) 74.743 ms 74.792 ms 74.978 ms
16 so-2-0-0.cr2.iad1.us.mfnx.net (208.185.0.146) 74.989 ms 75.187 ms 74.668 ms
17 so-2-0-0.cr2.lga1.us.mfnx.net (208.184.233.66) 74.763 ms 75.101 ms 74.722 ms
18 pos1-0.er1a.lga1.us.mfnx.net (216.200.127.198) 74.824 ms 77.198 ms 74.771 ms
19 panther.webhostingtalk.com (209.249.55.203) 75.016 ms 75.056 ms 74.848 ms


It does say lga1 being in NYC ... interesting ... my traceroute goes all around the states :) hm ... more interestingly ... seems like VDI is pushing outgoing bandwith via cogentco only! hm ...

BTW, the MFN network page does look very impressive/imformative ... too bad, such a good network like it is going down financially ... Thank you for the confirmation that WHT is indeed in Above.net NY.

cheers,
:beer:

It is hosted at Above.net in New York, courtesy of Voxel, I believe they have colocated cages directly in the data center. The connection is great in my opinion, always blazingly fast (never a delayed character on ssh) and extremely reliable, I can't remember a time when there has been a problem with the network (although of course wht server has had a few problems.)

The server is a VA Linux Dual P3 700 or 750mhz (I think its the latter), 512MB SDRAM, 9GB SCSI, Red Hat Linux.

note to dektong: maybe you get bounced around the states because cogent can only jump onto the above.net at one place (probably becauses its free peering) rather than paid transit.

Originally posted by dektong

BTW, the MFN network page does look very impressive/imformative ... too bad, such a good network like it is going down financially ...



Yes, I agree. But I guess (hope?) whoever ends up buying them (if it comes to that) will keep up the service. And yes, that page rocks! And yes, core routers turn me on. :D

I see a lot of Cogent going to the west coast, then hopping onto a Tier 1 backbone via NetRail, then heading to wherever the destination might be. The traceroute you posted, for instance, shows you going from Newark to San Francisco on Cogent, then from San Fran back to NY on MFN. I would imagine that with Cogent's purchase of PSINet that these coast-to-coast crossings will become less frequent...

I'm still not sure where VisualRoute gets its Location info from, though. :D

Jason

dektong,

the lga part in the last traceroute is in new york. lga is actually la guardia airport (one of the 'big three' airports in the new york metro area).

airports are, in a _lot_ of cases, the designated code in traceroutes. for example, you might see jfk (john f kennedy airport), ewr (newark international) and lga (la guardia) as well as iad (dulles international in washington). these are all places MFN has datacenters/pops in (lets not get into that argument again lol :)

as a pilot, i take perhaps a higher interest in learning the airport codes :)

raj

I know that Cogent has a connection to MFN in Atlanta... but I think that is paid transit, not peering... that's probably why it went out to their peering that was acquired from Netrail on the west coast.

This may be a dumb question, but why didn't Rackshack move WHT to thier datacenter?

Actually a very good question and I can probably answer it, but I'll let Robert tell you (for obvious reasons).

VDI does not force traffic over Cogent, It is chosen by BGP.
.

Heres is a trace to MFN

Tracing route to mfn.com [208.184.219.213]
over a maximum of 30 hops:

1 <10 ms <10 ms <10 ms corp.local [192.168.0.1]
2 <10 ms <10 ms <10 ms vlan1.edge1.cftnnj.inet.vdi.net [66.78.63.254]
3 <10 ms <10 ms <10 ms ge.core2.cft.vdi.net [66.78.63.249]
4 <10 ms <10 ms <10 ms pos.core1.nwk.vdi.net [66.78.63.245]
5 <10 ms <10 ms <10 ms 12.119.140.49
6 <10 ms <10 ms <10 ms gar3-p3100.n54ny.ip.att.net [12.123.214.186]
7 <10 ms <10 ms <10 ms gbr6-p90.n54ny.ip.att.net [12.123.1.190]
8 <10 ms <10 ms <10 ms gbr4-p90.n54ny.ip.att.net [12.122.5.118]
9 <10 ms <10 ms <10 ms ggr1-p370.n54ny.ip.att.net [12.123.1.125]
10 <10 ms <10 ms <10 ms pos5-3.pr1.lga1.us.mfnx.net [64.125.12.21]
11 <10 ms <10 ms <10 ms so-3-0-0.cr1.lga1.us.mfnx.net [208.185.0.237]
12 <10 ms 10 ms 10 ms so-1-0-0.cr1.iad1.us.mfnx.net [208.184.233.61]
13 <10 ms 10 ms 10 ms pos2-0.mpr1.iad1.us.mfnx.net [208.185.0.137]
14 71 ms 70 ms 70 ms so-6-1-0.mpr4.sjc2.us.mfnx.net [216.200.127.26]

15 70 ms 71 ms 80 ms pos5-0.er2a.sjc2.us.mfnx.net [208.184.102.238]
16 70 ms 80 ms 70 ms vlan2.cs2.sjc2.abov.sitesmith.com [208.184.169.7
1]
17 70 ms 80 ms 70 ms www2.sitesmith.com [208.184.219.213]

Trace complete.


Originally posted by dektong
and here is what I got (Traceroute from VDI):


traceroute to webhostingtalk.com (209.249.55.203), 64 hops max, 40 byte packets
3 pos.core1.nwk.vdi.net (66.78.63.245) 1.831 ms 1.726 ms 1.783 ms
4 f5.ba01.b002894-1.jfk01.atlas.cogentco.com (66.250.4.117) 3.034 ms 2.271 ms 1.961 ms
5 g12-6.core01.jfk01.atlas.cogentco.com (66.28.65.145) 3.208 ms 2.823 ms 2.535 ms
6 p13-0.core02.jfk02.atlas.cogentco.com (66.28.4.121) 2.255 ms 2.199 ms 2.215 ms
7 p14-0.core02.ord01.atlas.cogentco.com (66.28.4.86) 28.884 ms 28.159 ms 28.104 ms
8 p15-0.core01.ord01.atlas.cogentco.com (66.28.4.61) 28.343 ms 28.128 ms 28.247 ms
9 p5-0.core01.sfo01.atlas.cogentco.com (66.28.4.42) 74.102 ms 73.816 ms 73.899 ms
10 p15-0.core02.sfo01.atlas.cogentco.com (66.28.4.70) 74.932 ms 73.893 ms 73.947 ms
11 p6-0.tr1.sfr1.netrail.net (66.28.28.58) 74.317 ms 74.294 ms 74.372 ms
12 ge-2-2-0--0.pr1.SanFrancisco1.CA.us.netrail.net (205.215.12.2) 74.356 ms 74.451 ms 74.425 ms
13 Abovenet1.pr1.SanFancisco1.CA.us.netrail.net (205.215.1.50) 75.062 ms 74.546 ms 74.658 ms
14 so-4-1-0.mpr4.sjc2.us.mfnx.net (208.185.175.161) 74.821 ms 74.621 ms 74.946 ms
15 pos7-0.mpr1.iad1.us.mfnx.net (216.200.127.25) 74.743 ms 74.792 ms 74.978 ms
16 so-2-0-0.cr2.iad1.us.mfnx.net (208.185.0.146) 74.989 ms 75.187 ms 74.668 ms
17 so-2-0-0.cr2.lga1.us.mfnx.net (208.184.233.66) 74.763 ms 75.101 ms 74.722 ms
18 pos1-0.er1a.lga1.us.mfnx.net (216.200.127.198) 74.824 ms 77.198 ms 74.771 ms
19 panther.webhostingtalk.com (209.249.55.203) 75.016 ms 75.056 ms 74.848 ms


It does say lga1 being in NYC ... interesting ... my traceroute goes all around the states :) hm ... more interestingly ... seems like VDI is pushing outgoing bandwith via cogentco only! hm ...

BTW, the MFN network page does look very impressive/imformative ... too bad, such a good network like it is going down financially ... Thank you for the confirmation that WHT is indeed in Above.net NY.

cheers,
:beer: