
|
View Full Version : Better dedicated server
Yo-chan 12-24-2003, 08:41 PM I am looking for better dedicated server, always.
I have been using few dedicated servers up to now.
ServInt
ServerMatrix
MCHost
Fastservers
Wyenet
SuperWebHost
VenturesOnline
RackShack
After all, I am currently using ServInt and Fastservers and was thinking to move all the accounts to ServInt. But their network seems very unstable these days. I am having FTP problem and my site seems slow these days. There is nothing ServInt can do because of my location ( so they say). ServInt's support is quite nice, and I like their support. But I probably should not use them as my business because of their network is unstable.
Fastserver's network is okay these days, but they had problem before so I don't trust them anymore.
I need advice.
What is your recommendation for hosting dedicate servers?
I want to hear your experiences.
Thanks,
phpdeveloper 12-24-2003, 08:58 PM You mean to say you tried all those you listed in your post and don't quite like either of them? Hm... interesting, well, try rackspace.
Yo-chan 12-24-2003, 09:07 PM Originally posted by phpdeveloper
You mean to say you tried all those you listed in your post and don't quite like either of them? Hm... interesting, well, try rackspace.
Yes.
Well, ServInt is okay.
It is just network issue from my location(Japan).
Steven 12-24-2003, 10:02 PM Get a server in china then then there will be no network issue :)
phpdeveloper 12-24-2003, 10:04 PM Just curious, not really topic-related, but are there datacenters in Japan? If yes, what is their pricing and what you can get for it? A couple of examples will be fine, thank you in advance.
SniperDevil 12-24-2003, 10:11 PM i'm pretty sure there are, for those really high-speed residential and commercial ISPs (i'm talking about families in apartments with 45 mbps connections; this is very common)...
Yo-chan 12-25-2003, 02:15 AM Originally posted by phpdeveloper
Just curious, not really topic-related, but are there datacenters in Japan? If yes, what is their pricing and what you can get for it? A couple of examples will be fine, thank you in advance.
It will be more expensive to get a ded. server in Japan and these servers are not like servermatrix, fastservers, servint, etc. (i.e. ip is only 1, don't give you root access, etc)
Also, it seems it cost for noc and for rentaling server to get a ded. server in Japan. So, dedicated server rental is $200, but to use noc, they will charge you $300, and if you want stable noc, then $500, etc.
HOUSCOUS 12-25-2003, 02:24 AM Dedicated Servers in China are very expensive, and for some political reason, they might easily be shutdown or blocked
Heymish 12-25-2003, 06:15 AM lol - for some political reason
thats because China isnt the friendliest country around when it comes to foreigners wanting a slice of their action
wheimeng 12-25-2003, 08:26 AM Get from DV2 or cyberwurx. I'm with cyberwurx now and the speed is awesome!
Tazzman 12-25-2003, 08:46 AM I second Cyberwurx, though because of your location, you might be better off looking on the West Coast, in which case you might also want to look at Atjeu.
Aushosts 12-25-2003, 08:55 AM Perhaps a server in Hong Kong would be sutiable?
That should give you better pings, depending on many things - but it would be closer then the US.
http://www.webhostingtalk.com/showthread.php?s=&threadid=218991&
Hi Yo-chan,
You might want to consider Superb Servers. They're one of the better values around in terms of price to performance, and they connect directly to pretty much all of the major ISPs/telcos in Japan (Japan Telecom, IIJ, KDDI, PoweredCom), etc.
Just a thought =)
porcupine 12-26-2003, 05:57 AM Originally posted by Heymish
lol - for some political reason
thats because China isnt the friendliest country around when it comes to foreigners wanting a slice of their action
More likely because China is the biggest spamhole in the world. Tons of places block *.cn and all associated IP's from their mailservers nowdays, cuts down on 50%+ of the spam email apparently.
rusko 12-26-2003, 06:08 AM there was a (humorous) suggestion on nanog a couple months ago to depeer the nation of china from the internet =] the argument against it was that the network security folk would be out of a job <grin>.
paul
rusko 12-26-2003, 06:10 AM konnichiwa yo-chan,
just out of curiosity, could you please ping and traceroute to 69.28.242.68 from japan and post, pm or email me the results? was always wondering how our network performs from japan =]
paul
Yo-chan 12-26-2003, 08:45 AM Originally posted by rusko
konnichiwa yo-chan,
just out of curiosity, could you please ping and traceroute to 69.28.242.68 from japan and post, pm or email me the results? was always wondering how our network performs from japan =]
paul
Hi paul,
Pinging 69.28.242.68 with 32 bytes of data:
Reply from 69.28.242.68: bytes=32 time=2890ms TTL=44
Reply from 69.28.242.68: bytes=32 time=214ms TTL=44
Reply from 69.28.242.68: bytes=32 time=202ms TTL=44
Reply from 69.28.242.68: bytes=32 time=202ms TTL=44
Reply from 69.28.242.68: bytes=32 time=202ms TTL=44
Reply from 69.28.242.68: bytes=32 time=2771ms TTL=44
Reply from 69.28.242.68: bytes=32 time=1556ms TTL=44
Reply from 69.28.242.68: bytes=32 time=202ms TTL=44
Reply from 69.28.242.68: bytes=32 time=1134ms TTL=44
Reply from 69.28.242.68: bytes=32 time=2043ms TTL=44
Reply from 69.28.242.68: bytes=32 time=3846ms TTL=44
Reply from 69.28.242.68: bytes=32 time=212ms TTL=44
Reply from 69.28.242.68: bytes=32 time=202ms TTL=44
Reply from 69.28.242.68: bytes=32 time=205ms TTL=44
Reply from 69.28.242.68: bytes=32 time=202ms TTL=44
Request timed out.
Reply from 69.28.242.68: bytes=32 time=208ms TTL=44
Reply from 69.28.242.68: bytes=32 time=200ms TTL=44
Reply from 69.28.242.68: bytes=32 time=198ms TTL=44
Reply from 69.28.242.68: bytes=32 time=207ms TTL=44
Reply from 69.28.242.68: bytes=32 time=206ms TTL=44
Reply from 69.28.242.68: bytes=32 time=207ms TTL=44
Reply from 69.28.242.68: bytes=32 time=204ms TTL=44
Reply from 69.28.242.68: bytes=32 time=207ms TTL=44
Reply from 69.28.242.68: bytes=32 time=206ms TTL=44
Reply from 69.28.242.68: bytes=32 time=205ms TTL=44
Reply from 69.28.242.68: bytes=32 time=204ms TTL=44
Ping statistics for 69.28.242.68:
Packets: Sent = 27, Received = 26, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 198ms, Maximum = 3846ms, Average = 705ms
Tracing route to 69.28.242.68 over a maximum of 30 hops
1 7 ms 5 ms 1 ms 192.168.83.250
2 311 ms 5 ms 3 ms 192.168.80.1
3 9 ms 4 ms 5 ms 219.118.165.57
4 9 ms 4 ms 6 ms 219.101.40.69
5 13 ms 7 ms 6 ms 219.101.40.66
6 760 ms 1838 ms 1022 ms osk01fer01-ge-0-3-0.sonytelecom.ad.jp [219.101.40.253]
7 9 ms 7 ms 7 ms osk01cr03-ge-0-0.sonytelecom.ad.jp [211.9.32.73]
8 17 ms 16 ms 17 ms tky01cr03-ge-0-2.sonytelecom.ad.jp [211.9.32.177]
9 3651 ms 428 ms 311 ms tky01cr01-ge-1-0.sonytelecom.ad.jp [211.9.32.3]
10 19 ms 18 ms 17 ms a2-12-0-1.a07.tokyjp01.jp.ra.verio.net [61.120.146.161]
11 18 ms 17 ms 18 ms xe-7-0-1.a21.tokyjp01.jp.ra.verio.net [61.120.144.87]
12 17 ms 16 ms 17 ms xe-0-0-0.r21.tokyjp01.jp.bb.verio.net [61.213.162.225]
13 134 ms 133 ms 134 ms p16-5-0-0.r81.sttlwa01.us.bb.verio.net [129.250.4.173]
14 134 ms 134 ms 1151 ms p16-0-1-2.r21.sttlwa01.us.bb.verio.net [129.250.2.238]
15 173 ms 170 ms 172 ms p16-0-0-0.r00.chcgil06.us.bb.verio.net [129.250.2.7]
16 177 ms 170 ms 172 ms peer1-gw.peer1.net [206.223.119.30]
17 1212 ms 485 ms 184 ms GIG7-0.tor-core-a.peer1.net [216.187.68.57]
18 184 ms 185 ms 4005 ms OC48POS1-0.tor-core-b.peer1.net [216.187.68.230]
19 201 ms 202 ms 202 ms OC48POS3-0.mtl-core-b.peer1.net [216.187.68.93]
20 202 ms 202 ms 203 ms OC48POS4-0.mtl-core-a.peer1.net [216.187.90.45]
21 202 ms 202 ms 1350 ms OC48POS0-0.nyc-gsr-b.peer1.net [216.187.123.234]
22 202 ms 202 ms 201 ms 69.28.242.68
rusko 12-26-2003, 09:25 AM cool, thanks. ~200ms is better than i expected, even though you are having problems with your home connection :)
paul
Vinayak_Sharma 12-26-2003, 02:26 PM Hi Rusko this is what I got from India, New Delhi,
Pinging 69.28.242.68 with 32 bytes of data:
Reply from 69.28.242.68: bytes=32 time=561ms TTL=52
Reply from 69.28.242.68: bytes=32 time=550ms TTL=52
Reply from 69.28.242.68: bytes=32 time=551ms TTL=52
Reply from 69.28.242.68: bytes=32 time=551ms TTL=52
Ping statistics for 69.28.242.68:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 550ms, Maximum = 561ms, Average = 553ms
Tracing route to 69.28.242.68 over a maximum
1 270 ms 261 ms 260 ms 202.54.96.17
2 260 ms 261 ms 260 ms 202.54.96.14
3 270 ms 260 ms 391 ms 203.200.87.1
4 281 ms 280 ms 271 ms 202.54.2.253
5 571 ms 571 ms 561 ms iar5-so-2-0-
6 651 ms 571 ms 571 ms agr2-loopbac
7 841 ms 611 ms 631 ms dcr1-so-6-1-
8 1692 ms 701 ms 571 ms agr4-so-4-0-
9 571 ms 570 ms 581 ms acr1-loopbac
10 571 ms 571 ms 570 ms 206.24.195.1
11 581 ms 570 ms 571 ms 216.187.123.
12 561 ms 581 ms 561 ms 216.187.123.
13 611 ms 611 ms 601 ms 69.28.242.68
Trace complete.
|