LowEndBox - Cheap VPS, Hosting and Dedicated Server Deals

VelociHost – $48/Year 256MB SSD KVM in Miami, FL

Tags: , , , , , Date/Time: October 7, 2013 @ 8:02 am, by Liam

Roger, from VelociHOST, has got three offers for us this time. For the yearly plan, you will need to use the coupon code ONLYFORLEBS and for the other two plans, you will need to use the code ONLYFORLEB.

256-KVM VPS

  • 256MB Ram
  • 1 CPU Core
  • 5GB SSD Disk
  • 1TB Bandwidth
  • 1 IPv4 Address
  • KVM/SolusVM
  • 1Gbit Port Speed
  • $48/Year | Order Link
384-KVM VPS

  • 384MB Ram
  • 2 CPU Core
  • 7GB SSD Disk
  • 1TB Bandwidth
  • 1 IPv4 Address
  • KVM/SolusVM
  • 1Gbit Port Speed
  • $4.55/Month | Order Link
512-KVM VPS

  • 512MB Ram
  • 2 CPU Cores
  • 10GB SSD Disk
  • 1TB Bandwidth
  • 1 IPv4 Address
  • KVM/SolusVM
  • 1Gbit Port Speed
  • $6.50/Month | Order Link

VelociHOST have been featured on LowEndBox a couple of times before. KVM SSD-VPS plans provisioned on dual CPU of the newest Xeon E5-2600 Series Processors with pure Samsung SSD enterprise hardware. They provide support in both English and Spanish. All VPSs are deployed on their own enterprise hardware hosted at Colohouse, a SSAE 16 and PCI DSS compliant Miami, FL datacenter. You can view some benchmarks on ServerBear. Coupon valid until 10/10/2013. Reviews, thus far, have been rather good.

VelociHOST accept payments via Paypal. They have a 14 day free trial, since they know you will be convinced by the level of service they provide by testing it yourself. VelociHOST have most of the major Linux distribution and Windows Server trials. If they don’t have what you want, they will get it for you. Servers will be provisioned instantly. For more information, have a read of their Terms of Service.

Network Information:

Servers are located in Miami, Florida. For more information regarding their network, click here.

Test IPv4: 38.89.160.12
Test File: http://www.velocihost.net/speedtest/test100.zip

16 Comments

  1. Andrzej:

    Test IPv4 37.46.197.39 seems to be dead.

    October 7, 2013 @ 8:56 am | Reply
  2. Guys, our latest test IP is 38.89.160.12 Thank you!

    October 7, 2013 @ 9:18 am | Reply
  3. Zdravko:

    I would like to test your VPS, where is the Free Trial?

    October 7, 2013 @ 12:01 pm | Reply
    • We have a 14 days refund policy in case you are not satisfied for any reason.

      October 7, 2013 @ 4:44 pm | Reply
  4. DomainBop:

    “Reviews, thus far, have been rather good.”

    mini review after using VelociHost for 6 months: stable nodes, stable network, great uptime, haven’t had to open any support tickets.

    October 7, 2013 @ 2:49 pm | Reply
    • Thank you DomainBop! We’re always putting our best efforts to keep a high-industry-standard. We’re glad you’re satisfied!

      October 7, 2013 @ 4:48 pm | Reply
  5. Neptune:

    I was first interested, but they don’t seem to have good peering. Even from Orlando, I get more than 10 hops. From Europe then is a mess. They don’t seem to have direct peering with Terremark (NAP of the Americas).

    October 7, 2013 @ 6:14 pm | Reply
    • We merely have a 5.2 ms ping to Orlando’s DIMENOC:


      [root@test ~]$ ping 67.30.140.198
      PING 67.30.140.198 (67.30.140.198) 56(84) bytes of data.
      64 bytes from 67.30.140.198: icmp_seq=1 ttl=56 time=5.26 ms
      64 bytes from 67.30.140.198: icmp_seq=2 ttl=56 time=5.30 ms
      64 bytes from 67.30.140.198: icmp_seq=3 ttl=56 time=5.25 ms
      64 bytes from 67.30.140.198: icmp_seq=4 ttl=56 time=5.25 ms
      ^C
      --- 67.30.140.198 ping statistics ---
      4 packets transmitted, 4 received, 0% packet loss, time 3630ms
      rtt min/avg/max/mdev = 5.252/5.270/5.303/0.055 ms
      [root@test ~]$

      [root@test ~]$ traceroute 67.30.140.198
      traceroute to 67.30.140.198 (67.30.140.198), 30 hops max, 60 byte packets
      1 38.89.160.1 (38.89.160.1) 0.292 ms 0.314 ms 0.356 ms
      2 gi3-2.ccr01.mia09.atlas.cogentco.com (38.88.36.13) 0.910 ms 1.045 ms 1.151 ms
      3 te0-6-0-5.ccr21.mia01.atlas.cogentco.com (154.54.85.201) 0.754 ms te0-6-0-5.ccr22.mia01.atlas.cogentco.com (154.54.85.205) 0.659 ms te0-6-0-5.ccr21.mia01.atlas.cogentco.com (154.54.85.201) 0.669 ms
      4 be2055.ccr21.mia03.atlas.cogentco.com (154.54.24.234) 1.022 ms 0.915 ms be2054.ccr21.mia03.atlas.cogentco.com (154.54.80.42) 1.025 ms
      5 4.68.110.161 (4.68.110.161) 0.462 ms 0.494 ms ge-7-6.car2.Atlanta1.Level3.net (4.68.110.169) 0.420 ms
      6 ae-32-52.ebr2.Miami1.Level3.net (4.69.138.123) 4.994 ms 5.112 ms 5.063 ms
      7 ae-3-5.bar2.Orlando1.Level3.net (4.69.148.210) 5.174 ms 5.641 ms 5.610 ms
      8 ae-0-11.bar1.Orlando1.Level3.net (4.69.137.145) 5.037 ms 4.984 ms 4.929 ms
      9 ten-7-4.edge1.level3.mco01.hostdime.com (67.30.140.198) 5.562 ms 5.285 ms 5.588 ms
      [root@test ~]$

      October 8, 2013 @ 8:51 am | Reply
      • Neptune:

        That is still a little bit too much comparing to what I would expecet for the distance, maybe because there are a lot of hops in between. However, from Europe is my biggest concern (first example to you and second to DIMENOC):

        traceroute to 38.89.160.12 (38.89.160.12), 30 hops max, 40 byte packets using UDP
        1 lis1-cr1-gi13-4-1.cprm.net (195.8.0.118) 1.362 ms 3.878 ms 1.980 ms
        2 lon3-cr1-be4.cprm.net (195.8.1.46) 36.164 ms 35.209 ms 35.175 ms
        3 te3-7.ccr01.lon07.atlas.cogentco.com (149.11.30.25) 33.534 ms 33.535 ms 33.526 ms
        4 te0-0-0-32.ccr21.lon01.atlas.cogentco.com (154.54.62.101) 33.639 ms te0-7-0-32.ccr21.lon01.atlas.cogentco.com (130.117.1.177) 33.793 ms te0-7-0-35.ccr22.lon01.atlas.cogentco.com (154.54.59.173) 34.132 ms
        5 te0-5-0-6.ccr21.lon13.atlas.cogentco.com (154.54.74.46) 33.807 ms te0-1-0-4.mpd22.lon13.atlas.cogentco.com (154.54.57.161) 34.304 ms te0-5-0-6.mpd22.lon13.atlas.cogentco.com (154.54.74.62) 34.056 ms
        6 te0-7-0-4.ccr21.jfk02.atlas.cogentco.com (154.54.84.125) 102.243 ms te0-2-0-4.ccr22.bos01.atlas.cogentco.com (154.54.43.57) 107.857 ms te0-7-0-27.ccr21.bos01.atlas.cogentco.com (154.54.1.93) 106.978 ms
        7 be2095.mpd21.jfk02.atlas.cogentco.com (154.54.30.37) 105.254 ms te0-4-0-6.ccr22.dca01.atlas.cogentco.com (154.54.42.29) 114.914 ms te0-3-0-6.mpd21.dca01.atlas.cogentco.com (154.54.41.21) 107.391 ms
        8 te0-1-0-4.mpd22.dca01.atlas.cogentco.com (154.54.3.233) 112.619 ms te0-3-0-6.ccr21.dca01.atlas.cogentco.com (154.54.41.5) 111.810 ms te0-7-0-21.ccr22.atl01.atlas.cogentco.com (154.54.1.121) 128.493 ms
        9 te0-7-0-21.ccr21.atl01.atlas.cogentco.com (154.54.2.45) 122.640 ms te0-7-0-9.ccr22.atl01.atlas.cogentco.com (154.54.28.222) 122.750 ms te0-7-0-21.mpd22.atl01.atlas.cogentco.com (154.54.28.234) 122.582 ms
        10 te2-2.ccr01.mia09.atlas.cogentco.com (154.54.85.202) 296.743 ms te2-1.ccr01.mia09.atlas.cogentco.com (154.54.85.206) 295.969 ms be2124.ccr21.mia01.atlas.cogentco.com (154.54.24.246) 137.477 ms
        11 cr.mia1.velocihost.net (38.88.36.14) 132.394 ms te2-1.ccr01.mia09.atlas.cogentco.com (154.54.85.206) 292.550 ms cr.mia1.velocihost.net (38.88.36.14) 132.338 ms
        12 cr.mia1.velocihost.net (38.88.36.14) 136.518 ms 142.714 ms 136.458 ms
        13 * * *
        14 * * *

        traceroute to 198.49.66.130 (198.49.66.130), 30 hops max, 40 byte packets using UDP
        1 lis1-cr1-gi13-4-1.cprm.net (195.8.0.118) 2.201 ms 1.077 ms 3.495 ms
        2 mia1-cr1-te0-0-0.cprm.net (195.8.0.178) 75.683 ms 74.606 ms 73.523 ms
        3 dimenoc.nota-miami.net (198.32.125.68) 78.401 ms 78.368 ms 78.397 ms
        4 xe7-1-mco1.cr2.dimenoc.com (72.29.88.34) 79.133 ms * *
        5 198-49-66-130.static.dimenoc.com (198.49.66.130) 78.322 ms 78.311 ms 78.357 ms

        October 8, 2013 @ 12:32 pm | Reply
        • Jim Popovitch:

          I’m sure you could find further traces to Miami, with even more hops!! Seriously, hops don’t mean anything (unless it’s resiliency), timing is what matters.

          Why would you want a server in Miami to serve EU. There are plenty of EU hosting companies on LEB/LET.

          October 9, 2013 @ 9:54 am | Reply
          • Eg. for running a VPN service? Streaming of any kind is affected by this as well – just think about setting up some shoutcast, and then running into buffering issues ..

            There are plenty of other scenarios thou – these are just the ones that first appeared in my mind ;)

            cu, w0lf.

            October 17, 2013 @ 9:34 am | Reply
  6. Darwin:

    @Liam I think 256-KVM VPS has the wrong amount of RAM listed (I think it is 256 Mb, not 384Mb). When you click order link it shows 256 Mb.

    October 7, 2013 @ 10:32 pm | Reply
  7. Brendan:

    LEB community,

    We have been very happy with our investment. We have not had any problems with setting up our service, configuration changes, or billing support. We came to Veloci-Hosting after a problem with another provider in FL and have not looked back. The network speed has been great. Simple things like re-loads are fast and config’s are simple and fast if needed.

    Good Regards
    Brendan

    October 8, 2013 @ 11:11 am | Reply
    • Thank you Brendan! We really look forward to do quality business for the years to come. We appreciate your trust!

      October 8, 2013 @ 11:30 am | Reply

Leave a Reply

Some notes on commenting on LowEndBox:

  • Do not use LowEndBox for support issues. Go to your hosting provider and issue a ticket there. Coming here saying "my VPS is down, what do I do?!" will only have your comments removed.
  • Akismet is used for spam detection. Some comments may be held temporarily for manual approval.
  • Use <pre>...</pre> to quote the output from your terminal/console, or consider using a pastebin service.

Your email address will not be published. Required fields are marked *