• Howdy! Welcome to our community of more than 130.000 members devoted to web hosting. This is a great place to get special offers from web hosts and post your own requests or ads. To start posting sign up here. Cheers! /Peo, FreeWebSpace.net
managed wordpress hosting

valuablehost.com speed??

robin

robin

New Member
I want to host one of my domains at valuablehost (great features, implausibly low price, admin is nice guy, whatnot) ... I went to valuablehost.com today and it is really really really really slow... so are all the sites I know of that are hosted there. Is this a normal thing or is something up? eek!
 
hahahaha. never mind. check out this traceroute from my machine:

traceroute to valuablehost.com (66.54.221.131), 30 hops max, 40 byte packets
1 resnetx-xx-x.resnet.umbc.edu (xx.xx.xx.xx) 1.198 ms 0.744 ms 0.711 ms
2 * * *
3 xxx.umbc.edu (xx.xx.xx.xx) 0.985 ms 0.665 ms 0.882 ms
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 *

and it's just been sitting there for a while. I compared it to a traceroute from alertsite.com and am feeling mollified, if a bit silly, now.
 
Help a brother out, I am looking at valuablehost also.

What does this traceroute mean? Your mistake? Valuablehost is reliable and quick then no?
 
Hmm, your machine seems to be having problems:




1 206.117.161.1 (206.117.161.1) 0.564 ms 0.832 ms
2 isi-acg.ln.net (130.152.136.1) 2.411 ms 2.305 ms
3 usc-isi-atm.ln.net (130.152.128.2) 5.33 ms 3.841 ms
4 uscisi-pbi-630375.cust-rtr.pbi.net (209.232.128.189) 4.666 ms 4.352 ms
5 edge1-ge2-0.lsan03.pbi.net (206.13.29.205) 4.132 ms 5.464 ms
6 sl-gw15-ana-6-0.sprintlink.net (144.232.192.61) 4.659 ms 4.973 ms
7 sl-bb21-ana-12-0.sprintlink.net (144.232.1.209) 6.871 ms 6.274 ms
8 pos6-0.core2.LosAngeles1.Level3.net (209.0.227.49) 15.664 ms 17.894 ms
9 so-4-1-0.mp1.LosAngeles1.Level3.net (209.247.10.197) 18.689 ms 18.401 ms
10 so-0-1-0.mp2.Philadelphia1.Level3.net (64.159.0.142) 88.619 ms 88.536 ms
11 gigabitethernet9-1.hsipaccess1.Philadelphia1.Level3.net (64.159.0.154) 87.407 ms 86.442 ms
12 63.209.178.162 (63.209.178.162) 87.674 ms 91.260 ms
13 rif1.phl004bd01.yipes.com (209.50.43.189) 88.784 ms 88.213 ms
14 phl018s101.yipes.com (66.54.144.46) 88.993 ms 90.614 ms
15 66.7.139.82 (66.7.139.82) 90.802 ms 91.817 ms
16 66.54.221-yipes-webreseller.net (66.54.221.131) 89.143 ms 88.211 ms


from samspade.org, type in valuablehost.com for traceroute.



P.S this is quite good, dont forget the train derailed today and cut out uunet cables.

Regards,
ValuableHost
Originally posted by robin
hahahaha. never mind. check out this traceroute from my machine:

traceroute to valuablehost.com (66.54.221.131), 30 hops max, 40 byte packets
1 resnetx-xx-x.resnet.umbc.edu (xx.xx.xx.xx) 1.198 ms 0.744 ms 0.711 ms
2 * * *
3 xxx.umbc.edu (xx.xx.xx.xx) 0.985 ms 0.665 ms 0.882 ms
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 *

and it's just been sitting there for a while. I compared it to a traceroute from alertsite.com and am feeling mollified, if a bit silly, now.
Click to expand...
 
Speed

Just so you know.

There was a major train reck in PA where the servers are located.

This reck has cut the UUnet line.

Even though Valuablehost is on Yipes if anyone uses UUnet for peering to get to the server, there might be some issues.

Overall The Server has maintained 100% uptime through this reck.

Its currently just a UUnet issue... Yipes was not affected at all...
 
Well, my network has been having problems all day, and I'm running on no sleep so I apparently didn't notice until the traceroute :) Things seem to be back to normal now.

Coincidentally, there was also a train wreck down here in Baltimore yesterday... they had to quarantine the inner harbor because it was carrying stuff like hydrochloric acid.
 
P.S this is quite good, dont forget the train derailed today and cut out uunet cables.

Regards,
ValuableHost
[/B]
Click to expand...

Also not to mention there are ISP's who are effected by this "Code Red" worm If any part of your network is experiencing a DOS "denial of service" then it may make part of the net unavailable to you, just a note.
 
Worm

We were not effected by the code red worm

neither was valuablehost.

Just so everyone knows. Yipes is a extremely reliable backbone. Occasionaly it will do rerouting from a peering point some where on a level 3 router, but mostly its a stable connection

We monitor server speed all the time, and from chicago to the datacenter in PA, its 40ms.

Joe
 
ValuableHost:
I saw "Root Access - Yes" appear on your features list for your hosting plan, and I wonder what is it?

Don't tell me you are offering your server's root access to all of your customers...

Not to be offense, just wondering.
 
Oh right, now I get it. Still remember some mail someone sent you about accessing the root?
Well, it's just a faik. He gives you like /home/username/home/httpd/html/ and in your FTP it looks like /home/httpd/html/. Smart guy.
 
What are you on about, please backup your posts with factual information, YOU cannot access the root via ftp BUT if you login into the panel you DO get root access.

Regards,
Vhost
 
It would help if you descibed the difference between virtual shared hosting and virtual private servers (VPS). In talking with Valuablehost, he's told me that even the smallest plans are actually VPS' which basically means that each account is set up with its own root directory, similar to a fully dedicated server (the difference being that there are many VPS on one physical server). As he said, similar to fully dedicated servers, you can't access the root directory via FTP. (Actually you can, but that's a whole 'nuther topic and something few would recommend).
 
Originally posted by Valuablehost
What are you on about, please backup your posts with factual information, YOU cannot access the root via ftp BUT if you login into the panel you DO get root access.

Regards,
Vhost
Click to expand...
First of all the info is take from an error a script generated (a php script allways display it's path) an it shoed that info.
Anyway, if you give users root acces, isn't that a huge securety risk? What if someone doesn't like you and desides to delete your webserver,PHP and Perl. After all that can be done by a root.
 
Root

In regards to root access

Just so everyone knows, ensim does not give root access to every client. The reason i know this is because we use server xchange.

And valuablehost has a full server with us. there is 1 root access and that is his. He does have telnet access. Now sphera does create a vpn for every account, but lets not discuss that.


Root access should be describe as someone who can switch to a super user and manipulate the server.

Only one person can do that.

Now im totally sure how he has it setup, but there is telnet access.
 
They do not get root access via telnet, but if you log into the Ensim panel, you will notice via the file manager that they access certain root folders, /etc, /var etc...

Well its not really root access similar to VDS (virtual Dedicated Server).

Regards,
ValuableHost
 
You must log in or register to reply here.
Back
Top