So Gerald, are you saying this is good, or bad? I also see
that several packets were lost (*) in this trace. They
rated very high on a list of ping times, and were several
times less expensive that the 5-6 before them (out of 50).
At this link below, you can enter any URL and on the results
page compare
the tested URL to some hosts' ping times.
http://webservices.cnet.com/ping/default.asp
They are listed #1 here out of 21.
http://webservices.cnet.com/html/aisles/Most_Popular_-_Hosti
ng_Plans.asp
I haven't been satisfied with my current hosts
(NoMonthyFees.com), so I'm looking to change. On this page
above, I pinged my site several times to see where it was on
this list, and it (as I suspected) was FORTY NINTH (49th) on
average. It's best time was 14th place (on very rare
occasions).
-Clint
http://orpheuscomputing.com
Clint Hamilton, Owner
Orpheus Audio/Video & Computing
----- Original Message -----
From: "Gerald E. Boyd" <[EMAIL PROTECTED]>
At 12:30 AM 4/7/01 -0500,
[EMAIL PROTECTED] -Clint Hamilton
wrote the following:
>Does anyone have any experience with this hosting company,
>or heard anything about them please on how they rate?
>http://www.primemaster.com/index2.html
With many web hosting sites it is nice to know how fall down
the "tree" they
are located. That is, ISP A controls ISP B which controls
ISP C which hosts
your site. You can do this by using traceroute (UNIX) or
tracert (Windows)
to a site and look at the resulting ISP list.
no2:/opt2/home3/expita>traceroute primemaster.com
traceroute to primemaster.com (205.254.240.195), 30 hops
max, 40 byte packets
1 vlan20-gw.acc.dca1.hopone.net (207.228.228.1) 1 ms 1
ms 1 ms
2 ge1-0.core2.dca1.hopone.net (207.228.224.5) 1 ms 0 ms
1 ms
3 sl-gw19-rly-6-0-TS5.sprintlink.net (160.81.221.21) 3
ms * *
4 sl-bb20-rly-8-0.sprintlink.net (144.232.7.129) 3 ms *
3 ms
5 * 144.232.9.90 (144.232.9.90) 4 ms 3 ms
6 gbr3-p50.wswdc.ip.att.net (12.123.9.50) 3 ms 4 ms 4
ms
7 gbr3-p40.sl9mo.ip.att.net (12.122.2.82) 19 ms 20 ms
20 ms
8 * gbr3-p20.sffca.ip.att.net (12.122.2.74) 65 ms *
9 gbr5-p60.sffca.ip.att.net (12.122.5.141) 65 ms 65 ms
65 ms
10 ar8-p310.sffca.ip.att.net (12.123.12.185) 66 ms 67 ms
65 ms
11 12.124.32.22 (12.124.32.22) 139 ms 193 ms 245 ms
12 e1-0.edge0.sba1.avtel.net (207.71.192.62) 79 ms 78 ms
*
13 s0-rtr1.vta.west.net (205.254.246.253) 83 ms 96 ms
101 ms
14 ns1.primemaster.net (205.254.240.195) 86 ms * 305 ms
Looking at traces 10 through 14 (in reverse order).
So Primemaster is tied to West.net which in turn is tied to
Avtel.Net which
is tied to ATT (12.124.32.22). So if you host a domain at
Primemaster, then
you would be
4th removed from a "prime mover".
NOTE: ARIN search on 12.124.32.22 (Netblock owner)
Netname: ATT
Netblock: 12.0.0.0 - 12.255.255.255
The closer you are to a "prime mover" (in internet parlance,
a MAE or NAP)
then better your service for the simple reason that there is
less to go
wrong between you and someone else.
============= PCWorks Mailing List =================
Don't see your post? Check our posting guidelines &
make sure you've followed proper posting procedures,
http://pcworkers.com/rules.htm
Contact list owner <[EMAIL PROTECTED]>
Unsubscribing and other changes: http://pcworkers.com
=====================================================
