RTB Dedicated Hosting Service - Service Closing

Author Topic: RTB Dedicated Hosting Service - Service Closing  (Read 257115 times)

Having a ping of 50 from the west coast and 30 from the east coast is certainly better than 80 from the west coast.



I live in San Diego. Oops, looks like my connection to NY is faster than my connection to your servers. :panda:
« Last Edit: December 16, 2012, 07:04:06 PM by Trinick! »

Having a ping of 50 from the west coast and 30 from the east coast is certainly better than 80 from the west coast.
Code: [Select]
<name>-Mac-mini:~ jincux$ ping -c 15 ny01.returntoblockland.com
PING ny01.returntoblockland.com (209.159.159.94): 56 data bytes
64 bytes from 209.159.159.94: icmp_seq=0 ttl=114 time=36.061 ms
64 bytes from 209.159.159.94: icmp_seq=1 ttl=114 time=38.582 ms
64 bytes from 209.159.159.94: icmp_seq=2 ttl=114 time=34.558 ms
64 bytes from 209.159.159.94: icmp_seq=3 ttl=114 time=49.376 ms
64 bytes from 209.159.159.94: icmp_seq=4 ttl=114 time=35.763 ms
64 bytes from 209.159.159.94: icmp_seq=5 ttl=114 time=36.965 ms
64 bytes from 209.159.159.94: icmp_seq=6 ttl=114 time=37.087 ms
64 bytes from 209.159.159.94: icmp_seq=7 ttl=114 time=36.590 ms
64 bytes from 209.159.159.94: icmp_seq=8 ttl=114 time=39.857 ms
64 bytes from 209.159.159.94: icmp_seq=9 ttl=114 time=35.279 ms
64 bytes from 209.159.159.94: icmp_seq=10 ttl=114 time=37.771 ms
64 bytes from 209.159.159.94: icmp_seq=11 ttl=114 time=39.630 ms
64 bytes from 209.159.159.94: icmp_seq=12 ttl=114 time=35.071 ms
64 bytes from 209.159.159.94: icmp_seq=13 ttl=114 time=36.190 ms
64 bytes from 209.159.159.94: icmp_seq=14 ttl=114 time=35.604 ms

--- ny01.returntoblockland.com ping statistics ---
15 packets transmitted, 15 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 34.558/37.626/49.376/3.496 ms

<name>-Mac-mini:~ jincux$ ping -c 15 69.64.43.11
PING 69.64.43.11 (69.64.43.11): 56 data bytes
64 bytes from 69.64.43.11: icmp_seq=0 ttl=112 time=104.796 ms
64 bytes from 69.64.43.11: icmp_seq=1 ttl=112 time=104.057 ms
64 bytes from 69.64.43.11: icmp_seq=2 ttl=112 time=102.979 ms
64 bytes from 69.64.43.11: icmp_seq=3 ttl=112 time=102.483 ms
64 bytes from 69.64.43.11: icmp_seq=4 ttl=112 time=95.075 ms
64 bytes from 69.64.43.11: icmp_seq=5 ttl=112 time=98.739 ms
64 bytes from 69.64.43.11: icmp_seq=6 ttl=112 time=103.566 ms
64 bytes from 69.64.43.11: icmp_seq=7 ttl=112 time=103.439 ms
64 bytes from 69.64.43.11: icmp_seq=8 ttl=112 time=105.821 ms
64 bytes from 69.64.43.11: icmp_seq=9 ttl=112 time=103.499 ms
64 bytes from 69.64.43.11: icmp_seq=10 ttl=112 time=101.468 ms
64 bytes from 69.64.43.11: icmp_seq=11 ttl=112 time=99.087 ms
64 bytes from 69.64.43.11: icmp_seq=12 ttl=112 time=103.533 ms
64 bytes from 69.64.43.11: icmp_seq=13 ttl=112 time=100.412 ms
64 bytes from 69.64.43.11: icmp_seq=14 ttl=112 time=103.508 ms

--- 69.64.43.11 ping statistics ---
15 packets transmitted, 15 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 95.075/102.164/105.821/2.692 ms

From Florida. About 2 hours from Glass.

From San Diego

Code: [Select]
traceroute to 69.64.43.11 (69.64.43.11), 30 hops max, 60 byte packets
 1  vl3.mag01.san01.atlas.cogentco.com (66.250.250.137)  0.468 ms  0.474 ms
 2  te4-3.ccr01.san01.atlas.cogentco.com (154.54.84.233)  0.573 ms  0.573 ms
 3  te4-2.ccr01.phx02.atlas.cogentco.com (154.54.7.85)  9.435 ms  9.457 ms
 4  te7-8.ccr01.sat01.atlas.cogentco.com (154.54.80.210)  28.671 ms  28.728 ms
 5  te0-3-0-1.mpd22.iah01.atlas.cogentco.com (154.54.29.37)  34.431 ms  34.470 ms
 6  te0-4-0-1.ccr21.dfw01.atlas.cogentco.com (154.54.0.134)  39.440 ms te0-0-0-6.ccr21.dfw01.atlas.cogentco.com (154.54.25.217)  39.433 ms
 7  te0-3-0-2.ccr22.mci01.atlas.cogentco.com (154.54.25.210)  49.616 ms te0-2-0-1.ccr21.mci01.atlas.cogentco.com (154.54.2.114)  49.472 ms
 8  te2-8.ccr01.stl03.atlas.cogentco.com (154.54.30.106)  54.949 ms  54.990 ms
 9  154.54.88.122 (154.54.88.122)  55.040 ms 154.54.88.154 (154.54.88.154)  55.040 ms
10  38.88.130.10 (38.88.130.10)  54.921 ms 38.104.162.90 (38.104.162.90)  54.892 ms
11  static-ip-209-239-125-4.inaddr.ip-pool.com (209.239.125.4)  56.887 ms static-ip-209-239-125-3.inaddr.ip-pool.com (209.239.125.3)  62.188 ms
12  s03.kaphost.com (69.64.43.11)  55.225 ms  55.208 ms



From Miami

Code: [Select]
1  vl99.mag01.mia01.atlas.cogentco.com (66.28.3.217)  0.482 ms  0.508 ms
 2  te3-4.ccr01.mia01.atlas.cogentco.com (154.54.83.65)  6.257 ms  6.261 ms
 3  te0-1-0-4.mpd21.atl01.atlas.cogentco.com (154.54.3.25)  15.040 ms te0-1-0-4.mpd22.atl01.atlas.cogentco.com (154.54.46.53)  14.759 ms
 4  te0-2-0-7.mpd22.ord01.atlas.cogentco.com (154.54.29.86)  31.888 ms te0-1-0-6.mpd22.ord01.atlas.cogentco.com (154.54.29.82)  32.101 ms
 5  154.54.88.30 (154.54.88.30)  38.391 ms  38.424 ms
 6  154.54.88.114 (154.54.88.114)  38.422 ms 154.54.88.126 (154.54.88.126)  38.416 ms
 7  38.88.130.6 (38.88.130.6)  38.346 ms 38.104.162.66 (38.104.162.66)  38.340 ms
 8  static-ip-209-239-125-3.inaddr.ip-pool.com (209.239.125.3)  40.569 ms  40.637 ms
 9  s03.kaphost.com (69.64.43.11)  38.576 ms  38.679 ms



I can detect the problem being in Dallas (dfw), however this is not shown in my results. This is not regular behavior.

You definitely seemed interested in Zack0Wack0's and I gave you his.
cause I used to use it, but I always thought it was butt ugly :P

I can detect the problem being in Dallas (dfw), however this is not shown in my results. This is not regular behavior.
If you used MTR to come to this conclusion your understanding of what MTR is is completely wrong. Not sure how many times I need to tell you, or why you won't listen but Server4You is just poor with poor quality, slow routing. Look how inconsistent your latency is



If you're stuck on St. Louis being the best location for you PM me and I'll show you a better provider for the same money, otherwise w.e., back on topic.

We hope to have a few cool new features released today or tomorrow, keep checking back!
« Last Edit: December 16, 2012, 09:29:05 PM by Rub »

What type of check do you use for your own server?

The same check I use for yours backed with my own probes fed into munin from 2 different servers in Atlanta and a server in Manchester, UK. All the data matches up and is consistent.


TCP port, ICMP packets are always routed at a low priority and can (rarely) lead to incorrect results.

Since we are on the subject of pings, I thought I would post this. The results are in two images per test as it was too long to fit in one screenshot. Tests were both done at the same time.

Kalphiter's server:





Lub's server:





I'll let the results speak for themselves.

Since we are on the subject of pings, I thought I would post this. The results are in two images per test as it was too long to fit in one screenshot. Tests were both done at the same time.

Kalphiter's server:

[img]http://2.bp.blogspot.com/-PJOg-WDWq0U/UM6lEn4omQI/AAAAAAAAAMk/M-UNYkM4M4s/s1600/Page1Kal.PNG[/img

[img]http://4.bp.blogspot.com/-jpaitIlgNag/UM6lGRxmMEI/AAAAAAAAAM0/l8g-gX2uyg4/s1600/Page2Kal.PNG[/img

Lub's server:

[img]http://1.bp.blogspot.com/-KhWQw5bZlYc/UM6lF2f6IDI/AAAAAAAAAMs/R3o_e_6c_m8/s1600/Page1Lub.PNG[/img

[img]http://1.bp.blogspot.com/-kcOx3E4Bnao/UM6lHI6MlLI/AAAAAAAAAM8/F9r5sFoZTCM/s1600/Page2Lub.PNG[/img

I'll let the results speak for themselves.

Hey thanks, I've been waiting for something like this to show up. I'll use this when considering services to buy.

Another test from a different site:

Kal's:



Lub's:


Does anyone want to average all that data for me?

Never mind I'm on an iPad.
« Last Edit: December 16, 2012, 11:35:29 PM by Ravencroft² »

kalph: 111.16667
lub: 83.16667