Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


XHOSTFIRE.COM | KVM Virtual Servers in Siberia (Asia-Russia) / Sweden | 1Gbps | IPv4/IPv6 | From $5!
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

XHOSTFIRE.COM | KVM Virtual Servers in Siberia (Asia-Russia) / Sweden | 1Gbps | IPv4/IPv6 | From $5!

deployvmdeployvm Member, Host Rep
edited June 2015 in Offers




XHOSTFIRE Hosting Services


Hi LET members!



We would like to launch our new location for virtual servers in Novosibirsk (Siberia) Russia. We have cooperated with Rostelecom (state owned telecom) to make this possible. Server hardware in Siberia is owned by us and is colocated in Rostelecom's datacentre.



Why a Siberian location?

From our perspective, we chose Novosibirsk due to its exotic location and diverse network peerings around Asia and Europe. Novosibirsk has rich history, is isolated and lenient.



Reasons you may choose:
  • Project targets users in Asia, for example China mainland and you need fast response time.
  • Use the server for gameservers / voice servers / hosting.
  • Need basic protection against attacks
  • Need an interesting location with quality features or you need to host specific content.
  • Use for VPN (IPs are allocated from a clean residential subnet).





    Virtual Server Plans for LowEndTalk Members:



    We have already discounted these packages heavily, and you will not find a similar pricing for this network or location at all with our offered features/service. We have done our surveys.
    Our virtual machines are semi-managed, so we can care for your virtual machine by installing and configuring to your requirements.


    Location: Novosibirsk (Western Siberia region), Russia

    Special NSK

    Intel CPU: 1 core

    RAM: 256MB DDR3

    HDD: 15GB RAID 10 Protected

    Bandwidth: 1TB at 1Gbps

    IP Address: 1 IPv4 + 5 IPv6*

    Custom rDNS possible + Any Linux OS

    SolusVM CP / INSTANT SETUP!

    Price: $5.00 USD monthly

    Order: https://www.xhostfire.com/clientarea/cart.php?a=add&pid=38

KVM1-NSK

Intel CPU: 1 core

RAM: 512MB DDR3

HDD: 30GB RAID 10 Protected

Bandwidth: 2TB at 1Gbps

IP Address: 1 IPv4 + 5 IPv6*

Custom rDNS possible + Any Linux OS

SolusVM CP / INSTANT SETUP!

Price: $7.00 USD monthly

Order: https://www.xhostfire.com/clientarea/cart.php?a=add&pid=39



Larger plans available on our website.


DDoS filtering:



Basic filtering of UDP is provided and on best effort basis***, through ACLs and hardware firewalls. Our purpose is to provide an additional layer of protection to ensure maximum uptime. If you are targeted by attacks frequetely, we do not recommend you use our service, however we do have specialised solutions via Arbor/Cisco Guard at additional costs!
If you run an active website, TCP application or possibly gameserver, we can setup a dedicated remote TCP or HTTP filtering system in Moscow. For websites, Layer 7 filtering is provided through a cluster of NGINX proxies. Please refer to addons upon order for options.





Hardware:

We have colocation space in Rostelecom's Novosibirsk datacentre and server hardware is owned by us. For our hypervisor, we are using 2x Intel E5 CPUs, 48GB DDR3 ECC Registered RAM, Hitachi/Western Digital drives configured in H/W RAID 10 connected on dedicated 1Gbps bandwidth.

Network:

Novosibirsk is geographically located in Asia and in the eastern part of Siberia (Russia). We are also using Rostelecom - state owned ISP in Russia.
There are direct peerings with China Telecom, Unicom and China Mobile. You can expect latency of around 100-140ms and stable non-congested traffic.To further connect Asia, PCCW Hong Kong and NTT/KDDI Japan IP transit are used.
For Europe, Rostelecom has superb connectivity via PoPs in Scandinavia, Germany, Ukraine, London and Netherlands.

Latency:

We've tested the average lowest latency to many local ISPs.

Japan KDDI - 85ms / Japan NTT - 145ms

South Korea KT - 188ms

China Telecom BJ - 105ms / China Unicom BJ -110ms / Mobile GD - 135ms

Hong Kong (via PCCW) - 135ms

Moscow -40ms / short trip around Russia.

Around Europe - (average 60-100ms)

Pending enhancements in Russia:

Provide SSD storage, through SSD drives or PCI-E type SSD.

IPv6 deployment*, we are waiting for a subnet to be announced and routed. IPv6 addresses should be ready in the next few days.

Test IP RU: 95.167.6.12/ Speedtest file for Siberia only via PM or support ticket.

Official looking glass (select Novosibirsk): http://hd.ncc.snt.ru/lg


Location: Kista (Stockholm City), Sweden

Custom plans for LET:

LET special:
CPU: 1x Intel (up to 3.5Ghz)
RAM: 256MB DDR3
HDD: 20GB
Bandwidth: 500GB monthly at 1Gbps
IPv4: 1 Dedicated IP
IPv6: 5 IPs
DDoS Mitigation - yes
Price: $5 monthly
FREE INSTANT SETUP

ORDER: https://www.xhostfire.com/clientarea/cart.php?a=add&pid=29

KVMS1:
CPU: 1x Intel (up to 3.5Ghz)
RAM: 512MB DDR3
HDD: 50GB
Bandwidth: 750GB monthly at 1Gbps
IPv4: 1 Dedicated IP
IPv6: 5 IPs
DDoS Mitigation - yes
Price: $7 monthly
FREE INSTANT SETUP

ORDER: https://www.xhostfire.com/clientarea/cart.php?a=add&pid=25

Network testing for SE:
IP: 46.227.67.1
Testfile: Contact us for SE file

We have a simple ToS for prohibited activities and content:

  • No spam
  • No child porn or related content (promoting racism, banned substances or similar)
  • Any kind of outbound floods or abuse of bandwidth that can be considered as (D)DoS.
  • No abuse of CPU and Disk IO (constant DD burn etc) and currency mining.

    If you are unsure about your content, please send us an email or ticket.

Payment methods:

We accept PayPal, 2CheckOut and Bitcoin!

International credit/debit cards are supported by both 2CO and PayPal.






Thank you.

*ISP logo remain copyright of Rostelecom
*Payment gateway logos remain copyright of their respective owners.
*Our custom icons are copyrighted on our CDN deployment.
* We have the right to nullroute/disconnect your virtual machine from the internet if attack persists for long periods or large etc. We are not focused on protection in this type of offering!!

«1

Comments

  • deployvmdeployvm Member, Host Rep
    edited June 2015

    Here is a quick speedtest for those interested:

    image

    Current simple dd write Disk IO: (RAID 10 H/W through Adaptec on hostnode)

    We can offer 12-24 hour trials, please PM me.

    Basic FAQ:

    Q: Do you limit/block any sort of ports or services?

    A: No, we do not block any services or ports. You are free to install and bind the network interface with any service.

    Q: Do you have a refund policy?

    A: Yes, we do have a refund policy if you are not satisified with your inital tests. We can only refund within 24 hours of server activation. If we see abnormalities with your server, you will not be refunded.

    Q: What operating systems can be installed?

    A: Since we are using hardware KVM virtualisation for our hypervisor, any sort of OS that can be installed through an ISO is supported. Please be aware that the provisioning of Windows incurs an extra fee.

    Q: Do you offer custom packages?

    A: Sure! We can offer any sort of configurations that is suited to your needs. Please contact us through email or ticket for further details.

    Q: Are you virtual servers managed?

    A: We offer some management (semi-managed) of your virtual machine, and this includes basic monitoring and system checks. If it is an isolated incident relating to a customised script or software, we may charge an extra fee.

    Q: How I purchase additional IPs?

    A: You can buy additional IPs through the addon section of our billing manager or submit a ticket for customised offers. We can offer IPs in different regions (e.g. in AFRNIC, ARIN) for geolocation or specialised purposes.



    *Windows not supported on under 1GB RAM plans.

  • NekkiNekki Veteran

    Siberia? Banter

    Thanked by 1deployvm
  • deployvmdeployvm Member, Host Rep
    edited June 2015

    @Nekki said:
    Siberia? Banter

    >
    >

    Yep :) A very unique location! We're glad to offer this.

  • NekkiNekki Veteran
    edited June 2015

    @deployvm said:
    Yep :) A very unique location! We're glad to offer this.

    And I'm glad you offered it. Not often an LEB interests me these days.

    Thanked by 1deployvm
  • 110ms ping from uk, not bad at all. and great prices

    Thanked by 1deployvm
  • mintmint Member

    KT (4G), South Korea:

    C:\Users>ping 95.167.6.12
    
    Pinging 95.167.6.12 with 32 bytes of data:
    Reply from 95.167.6.12: bytes=32 time=299ms TTL=239
    Reply from 95.167.6.12: bytes=32 time=298ms TTL=239
    Reply from 95.167.6.12: bytes=32 time=308ms TTL=239
    Reply from 95.167.6.12: bytes=32 time=412ms TTL=239
    
    Ping statistics for 95.167.6.12:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 298ms, Maximum = 412ms, Average = 329ms
    
    C:\Users>tracert 95.167.6.12
    
    Tracing route to 95.167.6.12 over a maximum of 30 hops
    
      1    41 ms     3 ms     4 ms  192.168.43.1
      2    42 ms    38 ms    46 ms  95.167.6.12
      3    29 ms     *       41 ms  10.9.18.18
      4   166 ms    38 ms   115 ms  10.9.66.153
      5    67 ms    59 ms    58 ms  112.174.25.209
      6    68 ms    30 ms   131 ms  112.174.8.38
      7    33 ms    46 ms    49 ms  112.174.83.222
      8   175 ms   120 ms    84 ms  112.174.89.70
      9   373 ms     *      182 ms  79.133.94.173
     10   301 ms   303 ms   289 ms  95.167.92.10
     11   334 ms   305 ms   305 ms  95.167.6.12
    
    Trace complete.  
    

    LG U+, South Korea:

    $ ping 95.167.6.12 -c 10
    PING 95.167.6.12 (95.167.6.12) 56(84) bytes of data.
    64 bytes from 95.167.6.12: icmp_seq=1 ttl=231 time=275 ms
    64 bytes from 95.167.6.12: icmp_seq=2 ttl=231 time=271 ms
    64 bytes from 95.167.6.12: icmp_seq=3 ttl=231 time=277 ms
    64 bytes from 95.167.6.12: icmp_seq=4 ttl=231 time=272 ms
    64 bytes from 95.167.6.12: icmp_seq=5 ttl=231 time=266 ms
    64 bytes from 95.167.6.12: icmp_seq=6 ttl=231 time=277 ms
    64 bytes from 95.167.6.12: icmp_seq=7 ttl=231 time=267 ms
    64 bytes from 95.167.6.12: icmp_seq=8 ttl=231 time=278 ms
    64 bytes from 95.167.6.12: icmp_seq=9 ttl=231 time=277 ms
    64 bytes from 95.167.6.12: icmp_seq=10 ttl=231 time=272 ms
    
    --- 95.167.6.12 ping statistics ---
    10 packets transmitted, 10 received, 0% packet loss, time 9009ms
    rtt min/avg/max/mdev = 266.869/273.889/278.503/4.033 ms
    $ traceroute 95.167.6.12
    traceroute to 95.167.6.12 (95.167.6.12), 30 hops max, 60 byte packets
     1  192.168.10.1 (192.168.10.1)  0.507 ms  0.702 ms  0.927 ms
     2  106.XXX.XXX.XXX (106.XXX.XXX.XXX)  5.657 ms  6.021 ms  6.116 ms
     3  10.18.233.65 (10.18.233.65)  4.984 ms  5.093 ms  5.186 ms
     4  10.18.232.169 (10.18.232.169)  4.588 ms  4.692 ms  4.787 ms
     5  1.208.24.49 (1.208.24.49)  5.300 ms  5.400 ms  5.680 ms
     6  203.248.129.149 (203.248.129.149)  5.813 ms  2.560 ms  4.294 ms
     7  1.213.149.145 (1.213.149.145)  4.433 ms  4.532 ms 1.213.148.129 (1.213.148.129)  5.080 ms
     8  1.213.148.142 (1.213.148.142)  4.683 ms  4.791 ms  4.889 ms
     9  1.208.104.57 (1.208.104.57)  6.116 ms 1.208.150.165 (1.208.150.165)  5.729 ms 1.213.148.81 (1.213.148.81)  5.945 ms
    10  1.208.107.34 (1.208.107.34)  6.417 ms 1.213.104.34 (1.213.104.34)  6.263 ms 211.53.88.22 (211.53.88.22)  6.561 ms
    11  203.233.35.242 (203.233.35.242)  6.974 ms 1.208.150.113 (1.208.150.113)  7.327 ms 203.233.35.242 (203.233.35.242)  7.066 ms
    12  TenGE0-2-1-0.br03.hkg15.pccwbtn.net (63.218.210.134)  42.564 ms  41.212 ms  42.862 ms
    13  95.167.92.10 (95.167.92.10)  264.943 ms  260.919 ms rostelecom.tengi0-1-1-3.br03.hkg15.pccwbtn.net (63.218.211.74)  42.699 ms
    14  * 95.167.92.10 (95.167.92.10)  265.260 ms *
    15  * * *
    16  * * *
    17  * * *
    18  * * *
    19  * * *
    20  * * *
    21  * * *
    22  * * *
    23  * * *
    24  * * *
    25  * * *
    26  * * *
    27  * * *
    28  * * *
    29  * * *
    30  * * *
    

    high ping :s

  • rm_rm_ IPv6 Advocate, Veteran

    Wheeee. Congratulations with the launch!

    Thanked by 1deployvm
  • NekkiNekki Veteran

    @rm_ said:
    Wheeee. Congratulations with the launch!

    Fucking hell.

  • rds100rds100 Member

    Unique location indeed. Congratulations.

    Thanked by 1deployvm
  • @themt said:
    KT (4G), South Korea:

    C:\Users>ping 95.167.6.12
    
    Pinging 95.167.6.12 with 32 bytes of data:
    Reply from 95.167.6.12: bytes=32 time=299ms TTL=239
    Reply from 95.167.6.12: bytes=32 time=298ms TTL=239
    Reply from 95.167.6.12: bytes=32 time=308ms TTL=239
    Reply from 95.167.6.12: bytes=32 time=412ms TTL=239
    
    Ping statistics for 95.167.6.12:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 298ms, Maximum = 412ms, Average = 329ms
    
    C:\Users>tracert 95.167.6.12
    
    Tracing route to 95.167.6.12 over a maximum of 30 hops
    
      1    41 ms     3 ms     4 ms  192.168.43.1
      2    42 ms    38 ms    46 ms  95.167.6.12
      3    29 ms     *       41 ms  10.9.18.18
      4   166 ms    38 ms   115 ms  10.9.66.153
      5    67 ms    59 ms    58 ms  112.174.25.209
      6    68 ms    30 ms   131 ms  112.174.8.38
      7    33 ms    46 ms    49 ms  112.174.83.222
      8   175 ms   120 ms    84 ms  112.174.89.70
      9   373 ms     *      182 ms  79.133.94.173
     10   301 ms   303 ms   289 ms  95.167.92.10
     11   334 ms   305 ms   305 ms  95.167.6.12
    
    Trace complete.  
    

    LG U+, South Korea:

    $ ping 95.167.6.12 -c 10
    PING 95.167.6.12 (95.167.6.12) 56(84) bytes of data.
    64 bytes from 95.167.6.12: icmp_seq=1 ttl=231 time=275 ms
    64 bytes from 95.167.6.12: icmp_seq=2 ttl=231 time=271 ms
    64 bytes from 95.167.6.12: icmp_seq=3 ttl=231 time=277 ms
    64 bytes from 95.167.6.12: icmp_seq=4 ttl=231 time=272 ms
    64 bytes from 95.167.6.12: icmp_seq=5 ttl=231 time=266 ms
    64 bytes from 95.167.6.12: icmp_seq=6 ttl=231 time=277 ms
    64 bytes from 95.167.6.12: icmp_seq=7 ttl=231 time=267 ms
    64 bytes from 95.167.6.12: icmp_seq=8 ttl=231 time=278 ms
    64 bytes from 95.167.6.12: icmp_seq=9 ttl=231 time=277 ms
    64 bytes from 95.167.6.12: icmp_seq=10 ttl=231 time=272 ms
    
    --- 95.167.6.12 ping statistics ---
    10 packets transmitted, 10 received, 0% packet loss, time 9009ms
    rtt min/avg/max/mdev = 266.869/273.889/278.503/4.033 ms
    $ traceroute 95.167.6.12
    traceroute to 95.167.6.12 (95.167.6.12), 30 hops max, 60 byte packets
     1  192.168.10.1 (192.168.10.1)  0.507 ms  0.702 ms  0.927 ms
     2  106.XXX.XXX.XXX (106.XXX.XXX.XXX)  5.657 ms  6.021 ms  6.116 ms
     3  10.18.233.65 (10.18.233.65)  4.984 ms  5.093 ms  5.186 ms
     4  10.18.232.169 (10.18.232.169)  4.588 ms  4.692 ms  4.787 ms
     5  1.208.24.49 (1.208.24.49)  5.300 ms  5.400 ms  5.680 ms
     6  203.248.129.149 (203.248.129.149)  5.813 ms  2.560 ms  4.294 ms
     7  1.213.149.145 (1.213.149.145)  4.433 ms  4.532 ms 1.213.148.129 (1.213.148.129)  5.080 ms
     8  1.213.148.142 (1.213.148.142)  4.683 ms  4.791 ms  4.889 ms
     9  1.208.104.57 (1.208.104.57)  6.116 ms 1.208.150.165 (1.208.150.165)  5.729 ms 1.213.148.81 (1.213.148.81)  5.945 ms
    10  1.208.107.34 (1.208.107.34)  6.417 ms 1.213.104.34 (1.213.104.34)  6.263 ms 211.53.88.22 (211.53.88.22)  6.561 ms
    11  203.233.35.242 (203.233.35.242)  6.974 ms 1.208.150.113 (1.208.150.113)  7.327 ms 203.233.35.242 (203.233.35.242)  7.066 ms
    12  TenGE0-2-1-0.br03.hkg15.pccwbtn.net (63.218.210.134)  42.564 ms  41.212 ms  42.862 ms
    13  95.167.92.10 (95.167.92.10)  264.943 ms  260.919 ms rostelecom.tengi0-1-1-3.br03.hkg15.pccwbtn.net (63.218.211.74)  42.699 ms
    14  * 95.167.92.10 (95.167.92.10)  265.260 ms *
    15  * * *
    16  * * *
    17  * * *
    18  * * *
    19  * * *
    20  * * *
    21  * * *
    22  * * *
    23  * * *
    24  * * *
    25  * * *
    26  * * *
    27  * * *
    28  * * *
    29  * * *
    30  * * *
    

    high ping :s

    Mainly because routing HK. And PCCW caj have high latency at night.
    I got 90ms from Linode JP.

  • SpanceSpance Member
    edited June 2015

    Very nice route path for china.

    
                                          My traceroute  [v0.85]
    ubuntu (0.0.0.0)                                                         Wed Jun  3 23:29:52 2015
    Resolver error: No error returned but no answers given. of fields   quit
                                                             Packets               Pings
     Host                                                  Loss%   Snt   Last   Avg  Best  Wrst StDev
     1. 10.0.0.1                                            0.0%   104    0.4   0.4   0.3   0.5   0.0
     2. **.48.100.1                                         0.0%   104    5.6  12.9   2.7 114.1  22.9
     3. **.20.125.57                                       51.9%   104    4.2   5.9   1.7  67.4   9.1
     4. **.20.126.245                                      79.6%   104    4.7   6.0   4.5  18.1   3.0
     5. 219.158.12.77                                       0.0%   104   22.8  25.0  22.5  27.6   1.1
     6. 219.158.7.57                                        0.0%   103   50.5  49.6  45.7  52.1   1.1
     7. 219.158.101.38                                      0.0%   103   49.3  47.8  45.3  50.4   1.0
     8. 219.158.97.222                                      0.0%   103   48.4  48.6  44.8  51.6   1.1
     9. 188.128.15.213                                      0.0%   103   84.7  84.4  83.2  86.3   0.2
    10. 95.167.92.10                                        0.0%   103  142.7 147.5 139.9 209.9  12.1
    11. b-internet.217.65.87.244.snt.ru                     0.0%   103  140.0 140.5 135.2 161.3   5.6
     
    
    xxx@ubuntu:~$ wget -O /dev/null http://217.65.87.xxx:81/100MB.test
    --2015-06-03 23:32:19--  http://217.65.87.xxx:81/100MB.test
    Connecting to 217.65.87.xxx:81... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 100000000 (95M) [application/octet-stream]
    Saving to: ‘/dev/null’
    
    17% [=========>                                               ] 17,634,540  2.18MB/s  eta 70s    ^C
    
    Thanked by 2hotsnow deployvm
  • mintmint Member
    edited June 2015

    >

    Only LG U+ is routing HK. KT has direct connection to Russia but routing Vologodskaya, It's much further west than Novosibirsk.

    XIAOSpider97 said: And PCCW caj have high latency at night. I got 90ms from Linode JP.

    Oh yeah I might have seen this thing alot... my HK latency is normally 40ms but I sometimes even get 80ms to there.

  • raiderraider Member

    So while my Puppet is running in the nearby window, installing my new VM in Novosibirsk ...
    I want to say BIG THANKS!!! for that rare location

    Thanked by 1deployvm
  • fitvpnfitvpn Member

    Nekki said: Fucking hell.

    Don't tell Maounique :D

  • XIAOSpider97XIAOSpider97 Member
    edited June 2015

    @themt said:

    Nope! 79.133.94.173 is in HK (physically). Seems the peering PoP is in HK.

    I work for ipip.net, a company selling IP physical location database.

  • @Spance said:
    Very nice route path for china.

    
    >                                       My traceroute  [v0.85]
    > ubuntu (0.0.0.0)                                                         Wed Jun  3 23:29:52 2015
    > Resolver error: No error returned but no answers given. of fields   quit
    >                                                          Packets               Pings
    >  Host                                                  Loss%   Snt   Last   Avg  Best  Wrst StDev
    >  1. 10.0.0.1                                            0.0%   104    0.4   0.4   0.3   0.5   0.0
    >  2. **.48.100.1                                         0.0%   104    5.6  12.9   2.7 114.1  22.9
    >  3. **.20.125.57                                       51.9%   104    4.2   5.9   1.7  67.4   9.1
    >  4. **.20.126.245                                      79.6%   104    4.7   6.0   4.5  18.1   3.0
    >  5. 219.158.12.77                                       0.0%   104   22.8  25.0  22.5  27.6   1.1
    >  6. 219.158.7.57                                        0.0%   103   50.5  49.6  45.7  52.1   1.1
    >  7. 219.158.101.38                                      0.0%   103   49.3  47.8  45.3  50.4   1.0
    >  8. 219.158.97.222                                      0.0%   103   48.4  48.6  44.8  51.6   1.1
    >  9. 188.128.15.213                                      0.0%   103   84.7  84.4  83.2  86.3   0.2
    > 10. 95.167.92.10                                        0.0%   103  142.7 147.5 139.9 209.9  12.1
    > 11. b-internet.217.65.87.244.snt.ru                     0.0%   103  140.0 140.5 135.2 161.3   5.6
    >  
    
    > xxx@ubuntu:~$ wget -O /dev/null http://217.65.87.xxx:81/100MB.test
    > --2015-06-03 23:32:19--  http://217.65.87.xxx:81/100MB.test
    > Connecting to 217.65.87.xxx:81... connected.
    > HTTP request sent, awaiting response... 200 OK
    > Length: 100000000 (95M) [application/octet-stream]
    > Saving to: ‘/dev/null’
    > 
    > 17% [=========>                                               ] 17,634,540  2.18MB/s  eta 70s    ^C
    > 

    Directly. I used speedtest.net and found "Vladivostok (Rostelecom)" it's only <70ms.

    Unfortunately, the ISP says there are no public DCs in the far east :(

  • deployvmdeployvm Member, Host Rep

    Hi Everyone!

    Unfortunately for now, we have exhausted our IP allocation from Rostelecom. We have disabled further orders.

    We have sent a request to Rostelecom for more IPs, and when further IPs are deployed, we will enable stock again.

    Thank you.

  • NekkiNekki Veteran

    @deployvm said:
    Hi Everyone!

    Unfortunately for now, we have exhausted our IP allocation from Rostelecom. We have disabled further orders.

    We have sent a request to Rostelecom for more IPs, and when further IPs are deployed, we will enable stock again.

    Thank you.

    Disappointing as I hadn't ordered yet, but good for you for disabling orders rather than taking them and making people wait.

  • hotsnowhotsnow Veteran

    a simple test, seems good :p

    root@debian:~# wget freevps.us/downloads/bench.sh -O - -o /dev/null|bash
    CPU model :  QEMU Virtual CPU version (cpu64-rhel6)
    Number of cores : 1
    CPU frequency :  2400.084 MHz
    Total amount of ram : 494 MB
    Total amount of swap : 0 MB
    System uptime :   11 min,       
    Download speed from CacheFly: 3.06MB/s 
    Download speed from Coloat, Atlanta GA: 6.97MB/s 
    Download speed from Softlayer, Dallas, TX: 5.12MB/s 
    Download speed from Linode, Tokyo, JP: 16.3MB/s 
    Download speed from i3d.net, Rotterdam, NL: 8.52MB/s
    Download speed from Leaseweb, Haarlem, NL: 9.82MB/s 
    Download speed from Softlayer, Singapore: 2.64MB/s 
    Download speed from Softlayer, Seattle, WA: 4.53MB/s 
    Download speed from Softlayer, San Jose, CA: 4.04MB/s 
    Download speed from Softlayer, Washington, DC: 2.55MB/s 
    I/O speed :  226 MB/s
    
    Thanked by 1deployvm
  • nice ! out of stock!

  • deployvmdeployvm Member, Host Rep

    Whilst Siberia is currently out of stock, we are still open for orders in Sweden!

    Sweden is also a great location, do not undermine it :)

  • NekkiNekki Veteran

    @deployvm said:
    Whilst Siberia is currently out of stock, we are still open for orders in Sweden!

    Sweden is also a great location, do not undermine it :)

    I've already got Sweden covered thanks.

  • deployvmdeployvm Member, Host Rep
    edited June 2015

    We have successfully obtained another subnet from Rostelecom however we only have 2 NSK-KVM1 (512MB plan) left. We are no longer selling anymore "Special-NSK" plans now! This will be it for this month until some events occur.

    https://www.xhostfire.com/clientarea/cart.php?gid=14

    However we have reserved space for larger plans. if the larger plans interests you, please make order as usual.

    EDIT as of now, sold out again for $7 plans.

    Thanks!

  • NekkiNekki Veteran

    Jebus, gone already? I am disappoint, son.

  • deployvmdeployvm Member, Host Rep
    edited June 2015

    @Nekki said:
    Jebus, gone already? I am disappoint, son.

    Yes, sorry the LEB plans are gone until we receive another block of IPs. Some members asked for pre-ordering and we processed it all today. We are currently reserving space only for 1GB RAM above plans. Unfortunately they are not within LEB pricing.

  • NekkiNekki Veteran

    deployvm said:

    Yes, sorry the LEB plans are gone until we receive another block of IPs. We are currently reserving space only for 1GB RAM above plans. Unfortunately they are not within LEB pricing.

    Fair enough. Like I said before, I respect a host who knows how to discount plans sensibly.

    Thanked by 1deployvm
  • deployvmdeployvm Member, Host Rep

    @themt said:

    >
    >

    Regarding South Korea connectivity, it is unfortunate there is network 'congestion' at night. Sadly not much can be done for this. Korea Telecom does indeed have direct peering with Rostelecom and latency should be around 190ms, not more.

    MTR from South Korea SEJONG/ONESE (AS9848) certainly not bad :) Latency is actually really optimal through KT.

    Host Loss% Snt Last Avg Best Wrst StDev
    1. 10.0.1.1 94.8% 59 0.5 0.3 0.2 0.5 0.1
    2. 211.239.124.225 0.0% 59 4.6 2.9 1.0 12.1 2.5
    3. 211.239.113.9 0.0% 59 0.8 4.3 0.6 13.9 4.1
    4. 211.115.197.48 0.0% 59 2.8 1.2 0.7 5.9 0.9
    5. 211.115.201.77 0.0% 59 1.1 3.7 0.8 44.9 8.0
    6. 203.234.255.13 0.0% 59 1.6 3.2 1.3 22.4 4.5
    7. 112.174.89.74 0.0% 58 44.4 47.7 36.0 108.7 11.4
    8. 79.133.94.173 0.0% 58 45.0 52.4 43.9 91.3 9.2
    9. 95.167.92.10 0.0% 58 178.0 177.6 170.2 208.2 6.9
    10. 95.156.7x.xxx 0.0% 58 173.5 173.0 164.2 185.3 4.5

    SK Broadband - Do not need to discuss as the route path is often China Telecom.
    I have not been able to test LG U+.

    PCCW to Rostelecom is often stable, but at night I've noticed the latency increase by around 30-40ms. From example from my ISP in Australia, usual latency is about 235ms whilst in the evening, it could be 260ms.

    A traceroute from PCCW HK (VM):


    Host Loss% Snt Last Avg Best Wrst StDev 1. 10.70.29.1 0.0% 74 0.2 0.1 0.1 0.4 0.0 2. 10.16.30.50 0.0% 74 0.2 0.3 0.2 1.9 0.2 3. 207-226-143-1.static.pccwglobal. 0.0% 74 1.2 1.4 0.9 5.9 1.0 4. 63-218-56-149.static.pccwglobal. 0.0% 74 1.1 1.3 0.8 3.1 0.5 5. 63-218-210-222.static.pccwglobal 0.0% 73 1.7 2.1 1.5 5.2 0.7 6. 63-218-210-222.static.pccwglobal 0.0% 73 1.5 1.7 1.3 3.6 0.5 7. rostelecom.tengi0-1-1-3.br03.hkg 0.0% 73 1.1 4.1 1.0 75.7 11.3 8. 95.167.92.10 0.0% 73 137.2 139.6 137.1 178.9 8.3 9. 95.156.7x.xxx 0.0% 73 135.2 134.0 131.0 139.2 2.1

    If you are in Taiwan Hinet, the route should also be with PCCW.

    2 18 ms 16 ms 18 ms h254.s98.ts.hinet.net [168.95.98.254]
    3 17 ms 16 ms 18 ms pcpc-3302.hinet.net [168.95.23.70]
    4 20 ms 17 ms 16 ms PCPC-3202.hinet.net [220.128.11.98]
    5 28 ms 27 ms 21 ms TPDT-3012.hinet.net [220.128.2.54]
    6 18 ms 23 ms 16 ms r4103-s2.tp.hinet.net [220.128.2.205]
    7 17 ms 18 ms 17 ms r4003-s2.tp.hinet.net [220.128.7.225]
    8 39 ms 38 ms 39 ms pos2-1.cr02.hkg05.pccwbtn.net [63.218.215.113]
    9 39 ms 41 ms 40 ms 63-218-210-222.static.pccwglobal.net [63.218.210.222]
    10 42 ms 38 ms 47 ms 63-218-210-222.static.pccwglobal.net [63.218.210.222]
    11 40 ms 39 ms 38 ms rostelecom.tengi0-1-1-3.br03.hkg15.pccwbtn.net
    12 156 ms 156 ms 156 ms 95.167.92.10
    13 156 ms 153 ms 160 ms 95.156.7x.xxx

    Thank you.

  • deployvmdeployvm Member, Host Rep
    edited June 2015

    Example of KDDI Japan from Sakura - to some regions of Japan, latency is excellent. However to NTT JP it is about 150ms.

    traceroute to 95.156.7x.xxx (95.156.7x.xxx), 25 hops max, 52 byte packets
    1 59.106.1.129 (59.106.1.129) 0.507 ms 0.468 ms
    2 tkdrt7e-drt8e.bb.sakura.ad.jp (157.17.136.61) 0.556 ms 0.433 ms
    3 tkdrt2b-drt7e.bb.sakura.ad.jp (157.17.136.105) 0.659 ms 0.430 ms
    4 tkwrt1s-drt2b.bb.sakura.ad.jp (157.17.130.93) 0.257 ms 0.252 ms
    5 tkort2-wrt1s.bb.sakura.ad.jp (157.17.130.25) 0.579 ms 0.556 ms
    6 124.211.10.41 (124.211.10.41) 0.791 ms 0.938 ms
    7 otejbb205.int-gw.kddi.ne.jp (118.155.197.1) 1.147 ms
    otejbb205.int-gw.kddi.ne.jp (118.155.197.129) 1.546 ms
    8 tr-ote122.int-gw.kddi.ne.jp (106.187.6.162) 2.166 ms 1.131 ms
    9 188.254.55.225 (188.254.55.225) 25.417 ms 24.095 ms
    10 95.167.93.10 (95.167.93.10) 89.952 ms 91.922 ms
    11 95.156.7x.xxx (95.156.7x.xxx) 87.976 ms 87.375 ms

  • hotsnowhotsnow Veteran

    when will the IPv6 ready? :)

    Thanked by 1rm_
  • deployvmdeployvm Member, Host Rep
    edited June 2015

    @hotsnow said:
    when will the IPv6 ready? :)

    Well, Rostelecom has refused our /48 IPv6 announcement due to infrastructure limitations and we will have to wait a month before they upgrade their core router and switches. An upgraded router will support the announcement and allocation of additional prefixes.

    This does mean that IPv6 support will be delayed.

    Thanked by 1hotsnow
Sign In or Register to comment.