Dedicated servers with a real good con to europe and asia?

[johndoebob]

Is there any hoster that has lines with pings below 160ms to most parts of europe and west asia?I'm happy with ~167ms from EV1 but better would always be good.

[EviLGuY]

I doubt you'll do much better then that with a host located in the US.

[webair]

johndoebob

contact me at your convenience

[johndoebob]

I think Webair would be the best solution, I'm getting a 130ms ping here

Jupiter is the worst with over 200ms.

[keyDet79]

I think you'll do well with most hosts on the east coast. But why not host in Europe?

[liquidmoe]

Hit me up on icq at 36837470 we have moved over plenty of people from France and other parts of Europe to our network and they have been much happier, both network speedwise and support wise.

We have some great specials and I'll give you prices lower than whats listed at www.realitychecknetwork.com

[Big Ray]

Originally posted by johndoebob
I think Webair would be the best solution, I'm getting a 130ms ping here

Jupiter is the worst with over 200ms.

I think we're pretty good. With that said, you cant measure the performance of a network from one ping from one address.

----------------------
UK = 80ms (West Coast of US to the UK)
----------------------
traceroute to www.bbc.net.uk (212.58.240.33), 64 hops max, 44 byte packets
1 VE20.BI8-1-TELCO3-COLO7-SPSC.jupiterhosting.com (64.255.160.1) 0.304 ms 0.213 ms 0.186 ms
2 E3-4.ER-1-C99-P4-PAIX.jupiterhosting.com (64.255.167.17) 0.715 ms 0.591 ms 0.595 ms
3 198.32.176.151 (198.32.176.151) 1.148 ms 0.816 ms 0.846 ms
4 rt0-POS3-0.sjc.bbc.co.uk (212.58.255.173) 2.147 ms 2.244 ms 1.844 ms
5 rt0-POS7-0.thdo.bbc.co.uk (212.58.255.49) 78.479 ms 78.681 ms 78.077 ms
6 rt1.111ny.bbc.co.uk (212.58.255.138) 78.893 ms 78.561 ms 78.802 ms
7 rt1-POS7-0.thdo.bbc.co.uk (212.58.255.32) 78.804 ms 78.919 ms 78.173 ms
8 www3.thny.bbc.co.uk (212.58.240.33) 79.152 ms 80.298 ms 80.330 ms
root@www:~#


----------------------
Europe = 154ms (West Coast of US to the Central Europe)
----------------------
traceroute to www.netcologne.de (194.8.194.59), 64 hops max, 44 byte packets
1 VE20.BI8-1-TELCO3-COLO7-SPSC.jupiterhosting.com (64.255.160.1) 0.356 ms 0.223 ms 0.190 ms
2 E1-3.CCR-1-TELCO3-COLO7-SPSC.jupiterhosting.com (64.255.167.1) 1.019 ms 1.081 ms 0.962 ms
3 rteq-fe0.netcologne.de (206.223.116.108) 153.469 ms 153.591 ms 153.337 ms
4 cat6509-pg1-g64.netcologne.de (81.173.192.78) 154.529 ms 154.346 ms 155.019 ms
root@www:~#

----------------------
JAPAN / ASIA = 102ms (West Coast of US to ASIA)
----------------------

traceroute to wwwvip.nic.ad.jp (202.12.30.115), 64 hops max, 44 byte packets
1 VE20.BI8-1-TELCO3-COLO7-SPSC.jupiterhosting.com (64.255.160.1) 0.349 ms 0.208 ms 0.171 ms
2 E1-3.CCR-1-TELCO3-COLO7-SPSC.jupiterhosting.com (64.255.167.1) 1.033 ms 1.297 ms 1.168 ms
3 if-3-0.core1.SanJose.teleglobe.net (66.198.97.5) 1.245 ms 1.025 ms 0.968 ms
4 if-8-0.core2.SanJose.teleglobe.net (66.198.97.14) 1.192 ms 1.221 ms 1.039 ms
5 sanjose-bb0.iij.net (206.223.116.23) 1.580 ms 1.514 ms 1.529 ms
6 sjc002bb00.IIJ.Net (216.98.96.165) 1.799 ms 1.704 ms 1.603 ms
7 plt001bb01.IIJ.net (216.98.96.152) 2.733 ms 3.221 ms 3.055 ms
8 PaloAlto-bb2.IIJ.net (216.98.97.53) 3.771 ms 3.216 ms 3.255 ms
9 otemachi-bb7.IIJ.net (216.98.96.194) 99.064 ms 99.176 ms 98.845 ms
10 tky001ix01.IIJ.Net (210.130.143.49) 99.163 ms 99.080 ms 99.132 ms
11 nspixp2.nic.ad.jp (202.249.2.13) 99.614 ms 98.640 ms 98.855 ms
12 dixcrswa.nic.ad.jp (202.12.30.69) 100.978 ms 102.825 ms 99.929 ms


WHO DOES JUPITER PEER WITH?

[AndrewKanuck]

You can't judge by traceroute to one IP - as Jupiter said - we get

2 206.165.102.1 (206.165.102.1) 0.679 ms 0.699 ms 0.482 ms
3 so-1-1.hsa2.StLouis1.Level3.net (4.79.252.1) 6.432 ms 6.233 ms 5.824 ms
4 so-4-1-0.mp2.StLouis1.Level3.net (64.159.4.137) 5.799 ms 5.945 ms 6.527 ms
5 so-0-0-0.bbr2.NewYork1.Level3.net (64.159.0.238) 43.254 ms 43.894 ms 45.223 ms
6 ge-9-0-53.hsa1.NewYork1.Level3.net (64.159.17.71) 43.015 ms ge-9-1-56.hsa1.NewYork1.Level3.net (64.159.17.167) 42.409 ms 42.593 ms
7 BBC-TECHNOLO.hsa1.Level3.net (209.246.126.6) 42.721 ms 42.810 ms 43.002 ms
8 www10.thny.bbc.co.uk (212.58.240.110) 43.824 ms 42.870 ms 42.843 ms

and

2 206.165.102.1 (206.165.102.1) 0.732 ms 1.264 ms 0.570 ms
3 so-1-1.hsa2.StLouis1.Level3.net (4.79.252.1) 5.659 ms 6.256 ms 7.412 ms
4 ge-4-0-0.mp2.StLouis1.Level3.net (64.159.0.73) 5.690 ms 5.829 ms 5.676 ms
5 so-0-1-0.bbr1.NewYork1.Level3.net (64.159.1.41) 43.005 ms 42.738 ms 42.953 ms
6 4.68.128.105 (4.68.128.105) 109.711 ms 108.613 ms 108.708 ms
7 so-3-0-0.mp1.Dusseldorf1.Level3.net (212.187.128.22) 118.677 ms 119.970 ms 119.895 ms
8 so-2-0.hsa1.Dusseldorf1.Level3.net (4.68.114.238) 119.821 ms 118.196 ms 118.792 ms
9 62.67.38.230 (62.67.38.230) 134.843 ms 133.689 ms 133.764 ms
10 cat6509-pg2-vl31.netcologne.de (195.14.247.196) 134.458 ms 133.924 ms 135.277 ms

To Europe thru our Level3 link.

[Big Ray]

Originally posted by egonetworks
You can't judge by traceroute to one IP - as Jupiter said - we get

To Europe thru our Level3 link.

Are you not in Ohio?

I'm sorry, but until I can change the speed of light constant, that ain't going to change.lol

Where is your JP equiv. traceroute?

I am pointing out that we are directly connected to those countries. Notice that we don't go through anyone (such as Level 3) to get to those points?

[AndrewKanuck]

Originally posted by Big Ray
Are you not in Ohio?

I'm sorry, but until I can change the speed of light constant, that ain't going to change.lol

Where is your JP equiv. traceroute?

Ohio? Nope.

My bad, forgot to paste that one.

2 206.165.102.1 (206.165.102.1) 0.563 ms 0.592 ms 0.605 ms
3 so-1-1.hsa2.StLouis1.Level3.net (4.79.252.1) 5.976 ms 5.951 ms 5.872 ms
4 so-4-1-0.mp2.StLouis1.Level3.net (64.159.4.137) 6.402 ms 5.732 ms 6.539 ms
5 ge-0-3-0.bbr2.Washington1.Level3.net (64.159.0.229) 27.914 ms so-2-0-0.bbr2.Washington1.Level3.net (209.247.10.130) 26.804 ms 27.623 ms
6 so-7-0-0.edge1.Washington1.Level3.net (209.244.11.14) 27.652 ms so-6-0-0.edge1.Washington1.Level3.net (209.244.11.10) 27.227 ms so-7-0-0.edge1.Washington1.Level3.net (209.244.11.14) 27.631 ms
7 iiji-Level3-vlan.Washington1.Level3.net (209.0.227.102) 27.718 ms 27.548 ms 27.299 ms
8 lax001bb00.IIJ.Net (216.98.96.162) 80.656 ms 81.238 ms 81.024 ms
9 lax001bb01.IIJ.Net (216.98.96.177) 80.910 ms 81.542 ms 80.992 ms
10 sjc002bb01.IIJ.Net (216.98.96.158) 81.331 ms 80.885 ms 81.266 ms
11 sjc002bb00.IIJ.Net (216.98.97.145) 80.683 ms 81.566 ms 81.009 ms
12 plt001bb01.IIJ.Net (216.98.96.152) 82.511 ms 82.112 ms 82.158 ms
13 PaloAlto-bb2.IIJ.Net (216.98.97.37) 82.481 ms 83.405 ms 82.464 ms
14 otemachi-bb7.IIJ.Net (216.98.96.194) 288.389 ms 206.353 ms 240.736 ms
15 tky001ix01.IIJ.Net (210.130.143.49) 178.327 ms 178.562 ms 178.939 ms
16 nspixp2.nic.ad.jp (202.249.2.13) 306.367 ms 181.144 ms 178.253 ms
17 dixcrswa.nic.ad.jp (202.12.30.69) 180.929 ms 180.169 ms 180.317 ms
18 dixcrswa.nic.ad.jp (202.12.30.69) 179.249 ms !X * 180.832 ms !X

[s9ann0]

from the UK on cable I get about 80ms to ch00pa.com and about the same to realitychecknetwork.com

I prefer to host on east coast, new york is best ssh doesn't lag!

[chaze]

check ours:

http://dwhs.com

It might change though since w eus redundancy for the fastest connection.

Also we just posted a thread about low prices right now.