Micronode Instances - Launching Black Friday

MicronodeMicronode
edited November 2022 in Industry News

What on earth is a Micronode Instance?

The Micronode instance range is a way for you to create virtual private servers in any of our locations at any specification you like.

What are the costs?

MicroNode instances work on a pre-paid credit based system. Credits are valid for 1 year regardless of the amount of resource used.

Credits cost £10 per year each however we will be offering 50% off on the Black Friday launch.

What does one credit give me?

Once credit = 512MB RAM and 20GB Disk

What happens when I've used all of my resources?

You can simply purchase more credits or delete some instances to free up resource.

What about CPU cores?

Instances can only ever be single core.

How many instances does 1 credit get me?

The Minimum requirements to provision an instance is 64MB RAM and 3GB disk. You can provision up to 6 instances with 3GB Disk and 85MB RAM or less higher spec'd instances.

But you only have 3 locations

As more locations are added to our NatVPS range they will also become available to Micronode instances. We aim to add a minimum of 4 locations per year.

What happens if a location is out of stock?

We will aim to add more stock as soon as possible. We will ensure that at least 1 location has available resources to create instances. You will not be entitled to a refund unless no locations are available.

Is this fully supported?

No. Instances come with no support unless a location is down. If your instance is down the recommendation is to delete it and create a new one.

Can I re-install the OS on an instance?

No. Instances cannot be re-provisioned, they must be deleted and re-created.

If I delete an instance can I get the IP address(es) back?

No

Can I migrate an instance to another location?

No. You can however delete your instance and re-create it in another location.

Can I change the specifications of an instance?

No. You can however delete your instance and re-create it with your required specifications.

TLDR: Micronode instances are a way for you to create virtual private servers in any of our locations at any specification you like. The price is £10 per year for 512MB RAM and 20GB Disk.

These will launch on Black Friday along with a brand new location, these will be reduced to 50% off for Black Friday only!

These are NAT only and IPv6 may be tunneled in some locations. Don't like tunneled IPv6? Pretend there is no IPv6 connectivity and use IPv4!

Please let us know if anyone has any questions or feedback, this is a new market for us and we're trying to answer everyone's questions before launch.

Tagged:
«13

Comments

  • MicronodeMicronode

    @FrankZ @Mason Apologizes for adding this to LES Exclusive - I got a little trigger happy and posted before I'd picked the category! Could this be moved to discussions or news?

  • FrankZFrankZ ModeratorOG

    @natvps_uk said:
    @FrankZ Mason Apologizes for adding this to LES Exclusive - I got a little trigger happy and posted before I'd picked the category! Could this be moved to discussions or news?

    Moved to News as requested. :)

  • JabJab TOP Member 2027

    Now 75% off for LET Exclusive as punishment!
    Joking ofc.

    Good luck with sale!

    Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.

  • dosaidosai OG தோசை

    No mention about bandwidth?

  • MicronodeMicronode

    @dosai said:
    No mention about bandwidth?

    Unlimited

  • ehabehab

    its exciting to see such possibility. Look forward for launch.

  • dosaidosai OG தோசை

    @natvps_uk said:

    @dosai said:
    No mention about bandwidth?

    Unlimited

    Great, hoping to see APAC region in the future.

  • legendarylegendary

    This deal could look fragrant if:

    1. Proper, clickable URL provided to order page;
    2. Less irrelevant text. WoT with FAQ. Tafak?
    3. Less cumbersome billing. Credits? What else, manual service provisioning?

    Overall: improve your advertisement and be more simple. Here folks are with refined taste and WoT is definitely not on the pallet.

  • JabJab TOP Member 2027

    @natvps_uk said: IPv6 may be tunneled in some locations. Don't like tunneled IPv6? Pretend there is no IPv6 connectivity and use IPv4!

    cc @yoursunny trigger PTSD

    Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.

  • MicronodeMicronode

    @legendary said:
    This deal could look fragrant if:

    1. Proper, clickable URL provided to order page;
    2. Less irrelevant text. WoT with FAQ. Tafak?
    3. Less cumbersome billing. Credits? What else, manual service provisioning?

    Overall: improve your advertisement and be more simple. Here folks are with refined taste and WoT is definitely not on the pallet.

    Just to be clear, this is not a deal - this is an announcement of a deal that will be available on Black Friday.

    The Q&A style is to answer everyone’s questions before launch. The purpose of this thread is to allow people to ask any questions prior to the launch.

    The credit system is clearly explained above, it’s not clumbersome at all. It’s essentially a way to provide a bundle where people can change their locations.

    Just to be very clear on the Manual Service Provisioning point. All micronode services are delivered within two minutes via automated provisioning subject to a fraud check.

  • ralfralf
    edited November 2022

    @natvps_uk said:
    The credit system is clearly explained above, it’s not clumbersome at all. It’s essentially a way to provide a bundle where people can change their locations.

    I very much disagree with this statement.

    @natvps_uk said: What are the costs?
    MicroNode instances work on a pre-paid credit based system. Credits are valid for 1 year regardless of the amount of resource used.

    Valid for 1 year - does this mean they expire after one year or that the credit gives the use of the VPS for one year?

    Credits cost £10 per year each however we will be offering 50% off on the Black Friday launch.

    Is that £10 per credit or £10 for some credits?

    What does one credit give me?
    Once credit = 512MB RAM and 20GB Disk

    Is this per month for one credit or per year?

    Why do you have separate sliders if you get a fixed about of RAM and disk for a credit?

    What happens when I've used all of my resources?
    You can simply purchase more credits or delete some instances to free up resource.

    How does the deleting an instance help? Are the credits just buying some maximal total configuration and you can reassign it at will? Is so, why not just say so?

    What about CPU cores?
    Instances can only ever be single core.

    Why? And in any case is it a dedicated core, or a shared core, or a dedicated thread or a shared thread?

    You've also not given any clue about specs? Is the CPU an Atom or a recent high-end EPYC?

    What about network and bandwidth? The specs seem to indicate that IPv4 is NATted.

    The fact the screenshot talks about TAP/TUN suggest that it's LXC, which is a major turn off and should be mentioned up front.

    To me, if I'm understanding any of this correctly, a tenner a year gets me a 512MB RAM, 20GB disk of a shared thread on an unknown CPU, that's NATted with no information about bandwidth usage.

  • MicronodeMicronode
    edited November 2022

    @ralf said:

    @natvps_uk said:
    The credit system is clearly explained above, it’s not clumbersome at all. It’s essentially a way to provide a bundle where people can change their locations.

    I very much disagree with this statement.

    @natvps_uk said: What are the costs?
    MicroNode instances work on a pre-paid credit based system. Credits are valid for 1 year regardless of the amount of resource used.

    Valid for 1 year - does this mean they expire after one year or that the credit gives the use of the VPS for one year?

    Credits cost £10 per year each however we will be offering 50% off on the Black Friday launch.

    Is that £10 per credit or £10 for some credits?

    What does one credit give me?
    Once credit = 512MB RAM and 20GB Disk

    Is this per month for one credit or per year?

    Why do you have separate sliders if you get a fixed about of RAM and disk for a credit?

    What happens when I've used all of my resources?
    You can simply purchase more credits or delete some instances to free up resource.

    How does the deleting an instance help? Are the credits just buying some maximal total configuration and you can reassign it at will? Is so, why not just say so?

    What about CPU cores?
    Instances can only ever be single core.

    Why? And in any case is it a dedicated core, or a shared core, or a dedicated thread or a shared thread?

    1 credit = 512Mb RAM and 20GB disk. You are free to do what you want with this resource. The credit is valid for 1 year. 1 credit is £10.

    Credits are simply an amount of resource, you can reuse this resource indefinitely whilst your credit is valid. Deleting an instance frees up resource and allows you to create a new instance.

    1 VM does not = 1 credit! Hence the difference in the sliders for RAM and CPU. You can create as many instances as you like within the amount of resource provided by your credits.

    I hope this clears things up and apologies if it was overly confusing.

    As for the single CPU core, these are real budget offerings, if you want more then our VPS deals are more fitting.

  • duckgoduckgo

    Cool, look forward to that :3 <3

  • yoursunnyyoursunny OG

    Suppose I purchase one credit on Dec 01 and purchase another credit on Dec 11, I would have two credits until Dec 01 next year.
    Now I create several VMs to use up all resources from the two credits, but each VM is smaller than the resources given by one credit.
    On Dec 01 next year, one of the credits would expire.
    My VMs are now exceeding the limits of my remaining one credit.
    How does the system determine which VMs should be deleted?

    We accept Karma donations for the last flan. 🍮 affbrr

  • MicronodeMicronode

    @yoursunny said:
    Suppose I purchase one credit on Dec 01 and purchase another credit on Dec 11, I would have two credits until Dec 01 next year.
    Now I create several VMs to use up all resources from the two credits, but each VM is smaller than the resources given by one credit.
    On Dec 01 next year, one of the credits would expire.
    My VMs are now exceeding the limits of my remaining one credit.
    How does the system determine which VMs should be deleted?

    Very good question!

    Currently it is down to the customer to ensure that they do not go over their resource limits on credit expiry. All VMs are suspended until either X amount are deleted to free up resource or more credits are added.

  • MicronodeMicronode

    @natvps_uk said:

    @yoursunny said:
    Suppose I purchase one credit on Dec 01 and purchase another credit on Dec 11, I would have two credits until Dec 01 next year.
    Now I create several VMs to use up all resources from the two credits, but each VM is smaller than the resources given by one credit.
    On Dec 01 next year, one of the credits would expire.
    My VMs are now exceeding the limits of my remaining one credit.
    How does the system determine which VMs should be deleted?

    Very good question!

    Currently it is down to the customer to ensure that they do not go over their resource limits on credit expiry. All VMs are suspended until either X amount are deleted to free up resource or more credits are added.

    Essentially the credits purchased on December 1st are no longer valid however the credits purchased on December 11th remain valid until expiry.

  • legendarylegendary

    "simplistic credit system" :D this has some drama potential. I hope.

  • yoursunnyyoursunny OG

    @natvps_uk said:

    @yoursunny said:
    Suppose I purchase one credit on Dec 01 and purchase another credit on Dec 11, I would have two credits until Dec 01 next year.
    Now I create several VMs to use up all resources from the two credits, but each VM is smaller than the resources given by one credit.
    On Dec 01 next year, one of the credits would expire.
    My VMs are now exceeding the limits of my remaining one credit.
    How does the system determine which VMs should be deleted?

    Very good question!

    Currently it is down to the customer to ensure that they do not go over their resource limits on credit expiry. All VMs are suspended until either X amount are deleted to free up resource or more credits are added.

    Essentially the credits purchased on December 1st are no longer valid however the credits purchased on December 11th remain valid until expiry.

    Suppose I have three VMs, each has 300MB RAM and 5GB disk.
    Once my first credit expires on Dec 01, the remaining credit can still cover one VM's RAM and three VM's disk.
    While it's fine to suspend them, I would expect being able to start at least one VM at a time.

    You would otherwise get drama threads regarding customer being forced to delete data even if they still have unexpired credit.

    We accept Karma donations for the last flan. 🍮 affbrr

  • MicronodeMicronode

    I think there is some overall confusion on how this works.

    It is pretty simple in practice.

    1 Credit lasts for 365 days from the date of purchase.

    1 Credit gives you 512MB RAM and 20GB disk

    You can create as many instances that will physically fit within that resource. If you run out of resource you can either delete a VM to free up resource or purchase another credit.

    I’m not sure how to explain this anymore simply however I am open to handing out a bunch of demo accounts for people to test if that helps.

    @ehab is currently on the beta and hopefully he can help answer some questions.

  • MicronodeMicronode
    edited November 2022

    @yoursunny said:

    @natvps_uk said:

    @yoursunny said:
    Suppose I purchase one credit on Dec 01 and purchase another credit on Dec 11, I would have two credits until Dec 01 next year.
    Now I create several VMs to use up all resources from the two credits, but each VM is smaller than the resources given by one credit.
    On Dec 01 next year, one of the credits would expire.
    My VMs are now exceeding the limits of my remaining one credit.
    How does the system determine which VMs should be deleted?

    Very good question!

    Currently it is down to the customer to ensure that they do not go over their resource limits on credit expiry. All VMs are suspended until either X amount are deleted to free up resource or more credits are added.

    Essentially the credits purchased on December 1st are no longer valid however the credits purchased on December 11th remain valid until expiry.

    Suppose I have three VMs, each has 300MB RAM and 5GB disk.
    Once my first credit expires on Dec 01, the remaining credit can still cover one VM's RAM and three VM's disk.
    While it's fine to suspend them, I would expect being able to start at least one VM at a time.

    You would otherwise get drama threads regarding customer being forced to delete data even if they still have unexpired credit.

    Whilst I get where you are coming from we still have to store the data from the suspended VMs which comes at a cost to us.

    We have at least a year to modify how the suspension system works and we’re open to any suggestions!

    Maybe a way for the client to export their Instance and re-import it at a later date?

    Edit: if the remaining VMs fit in the disk space allocated then the VMs could simply be resized to fit within the allocated memory?

    We are looking to add a way to change the specifications of each instance.

    I also agree that the client should be able to start one Vm at a time and that is something that we can make possible. I’ll definitely add it to the backlog - thanks for the suggestion.

  • yoursunnyyoursunny OG

    @natvps_uk said:

    @yoursunny said:
    Suppose I have three VMs, each has 300MB RAM and 5GB disk.
    Once my first credit expires on Dec 01, the remaining credit can still cover one VM's RAM and three VM's disk.
    While it's fine to suspend them, I would expect being able to start at least one VM at a time.

    You would otherwise get drama threads regarding customer being forced to delete data even if they still have unexpired credit.

    Whilst I get where you are coming from we still have to store the data from the suspended VMs which comes at a cost to us.

    Yes, but my remaining credit would provide 20GB disk, and my three suspended VMs only consume 15GB total.

    We have at least a year to modify how the suspension system works and we’re open to any suggestions!

    Maybe a way for the client to export their Instance and re-import it at a later date?

    This is useful in general, not just at suspension.
    This would enable more use cases:

    • resize RAM, by deleting instance and creating new instance from snapshot
    • resize disk (if it's LXC container)
    • migrate to another location
    • duplicate a VM template to multiple VMs

    Storage used for instance snapshot should count towards the credit limits, possibly at a reduced rate if it's HDD vs SSD.

    We accept Karma donations for the last flan. 🍮 affbrr

  • MicronodeMicronode

    @yoursunny said:

    @natvps_uk said:

    @yoursunny said:
    Suppose I have three VMs, each has 300MB RAM and 5GB disk.
    Once my first credit expires on Dec 01, the remaining credit can still cover one VM's RAM and three VM's disk.
    While it's fine to suspend them, I would expect being able to start at least one VM at a time.

    You would otherwise get drama threads regarding customer being forced to delete data even if they still have unexpired credit.

    Whilst I get where you are coming from we still have to store the data from the suspended VMs which comes at a cost to us.

    Yes, but my remaining credit would provide 20GB disk, and my three suspended VMs only consume 15GB total.

    We have at least a year to modify how the suspension system works and we’re open to any suggestions!

    Maybe a way for the client to export their Instance and re-import it at a later date?

    This is useful in general, not just at suspension.
    This would enable more use cases:

    • resize RAM, by deleting instance and creating new instance from snapshot
    • resize disk (if it's LXC container)
    • migrate to another location
    • duplicate a VM template to multiple VMs

    Storage used for instance snapshot should count towards the credit limits, possibly at a reduced rate if it's HDD vs SSD.

    I have a few ideas on how we could do that! I’ll look into it.

  • blissbliss

    Hello @natvps_uk

    my service remains suspended status because of "torrentting" since my removal of transmission-bt for weeks now, thus "actions" in the 'product details' is not operatable (only 'request cancellation' is available).

    I'd like to do some management in the control panel, like OS re-installation or monitor traffic usage to avoid over-usage, which may cause another strict ban.

    So please turn my service into a normal status, which will enable me to do some management work, thank you.

    The original ticket went unanswered, so I have no way but resort to the forum.

    GMY-834926

    MicroLXC is lovable.

  • MicronodeMicronode

    @bliss said:
    Hello @natvps_uk

    my service remains suspended status because of "torrentting" since my removal of transmission-bt for weeks now, thus "actions" in the 'product details' is not operatable (only 'request cancellation' is available).

    I'd like to do some management in the control panel, like OS re-installation or monitor traffic usage to avoid over-usage, which may cause another strict ban.

    So please turn my service into a normal status, which will enable me to do some management work, thank you.

    The original ticket went unanswered, so I have no way but resort to the forum.

    GMY-834926

    I've replied to the ticket, sorry for the delay.

  • ehabehab

    i am on beta and can try to reproduce your use cases. Please add them here, if it works i will quote with PASS if not i will comment the outcome.

  • rootroot OG

    This offer is quite interesting for NAT VPS used as VPN. Basically we can choose location, and since we all love to squeeze out all resources from low-end machines, this makes it perfect for our low-end community.

    There is only one thing left: DMCA - will you ignore it @natvps_uk ?

    Cloudcone | Crunchbits | Dartnode | Dedirock | Georgedatacenter | Gigahost | Hostbilby | Host-c | Hostdzire | Hostsailor | Namecrane | Nuyek | Realtoxmedia | Servarica | Terabit | Tnahosting | Virmach

  • MicronodeMicronode

    @root said:
    This offer is quite interesting for NAT VPS used as VPN. Basically we can choose location, and since we all love to squeeze out all resources from low-end machines, this makes it perfect for our low-end community.

    There is only one thing left: DMCA - will you ignore it @natvps_uk ?

    Thanks @root

    Not in the current locations unfortunately however we may have an option soon.

  • atomiatomi OG

    @natvps_uk to support smaller instances, would it be possible to add AlpineLinux template?

  • kuroneko23kuroneko23 OG

    Basically a resource pool for NAT VPS. Will try it out on BF.

  • welllamwelllam

    very interesting. When will the stock be replenished?

  • MicronodeMicronode

    @welllam said:
    very interesting. When will the stock be replenished?

    These will be released on Black Friday

  • MicronodeMicronode

    @atomi said:
    @natvps_uk to support smaller instances, would it be possible to add AlpineLinux template?

    Yes, alpine support is on our roadmap. It’s possible it could be available before launch

  • MicronodeMicronode

    Launch Locations finalised:

    Locations coming soon:
    Seoul, KR
    Amsterdam, NL

    We've added a small amount of stock for the credits - Think of it like a Pre Launch, these are available for existing Micronode users only.

  • codelockcodelock

    @natvps_uk said:
    Launch Locations finalised:

    Locations coming soon:
    Seoul, KR
    Amsterdam, NL

    We've added a small amount of stock for the credits - Think of it like a Pre Launch, these are available for existing Micronode users only.

    No love for natvpsuk customers ?

    Want free vps ? https://microlxc.net

  • fluttershyfluttershy

    @natvps_uk said:
    Launch Locations finalised:

    Locations coming soon:
    Seoul, KR
    Amsterdam, NL

    We've added a small amount of stock for the credits - Think of it like a Pre Launch, these are available for existing Micronode users only.

    Who are you using for Seoul and Amsterdam?

  • MicronodeMicronode

    YABS

    Beauharnois, Canada

    # ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #

    Yet-Another-Bench-Script

    v2022-08-20

    https://github.com/masonr/yet-another-bench-script

    ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##

    Sun Nov 20 13:42:38 UTC 2022

    Basic System Information:

    Uptime : 0 days, 0 hours, 0 minutes
    Processor : Intel(R) Xeon(R) CPU D-1521 @ 2.40GHz
    CPU cores : 1 @ 800.244 MHz
    AES-NI : ✔ Enabled
    VM-x/AMD-V : ✔ Enabled
    RAM : 1.0 GiB
    Swap : 256.0 MiB
    Disk : 39.2 GiB
    Distro : Ubuntu 22.04.1 LTS
    Kernel : 5.2.0

    fio Disk Speed Tests (Mixed R/W 50/50):

    Block Size 4k (IOPS) 64k (IOPS)
    Read 56.88 MB/s (14.2k) 122.65 MB/s (1.9k)
    Write 56.97 MB/s (14.2k) 123.30 MB/s (1.9k)
    Total 113.85 MB/s (28.4k) 245.95 MB/s (3.8k)
    Block Size 512k (IOPS) 1m (IOPS)
    ------ --- ---- ---- ----
    Read 138.58 MB/s (270) 153.44 MB/s (149)
    Write 145.94 MB/s (285) 163.66 MB/s (159)
    Total 284.53 MB/s (555) 317.10 MB/s (308)

    iperf3 Network Speed Tests (IPv4):

    Provider | Location (Link) | Send Speed | Recv Speed
    | | |
    Clouvider | London, UK (10G) | 241 Mbits/sec | 807 Mbits/sec
    Online.net | Paris, FR (10G) | 244 Mbits/sec | 824 Mbits/sec
    Hybula | The Netherlands (40G) | 245 Mbits/sec | 857 Mbits/sec
    Uztelecom | Tashkent, UZ (10G) | 217 Mbits/sec | 512 Mbits/sec
    Clouvider | NYC, NY, US (10G) | 261 Mbits/sec | 940 Mbits/sec
    Clouvider | Dallas, TX, US (10G) | 258 Mbits/sec | 920 Mbits/sec
    Clouvider | Los Angeles, CA, US (10G) | 247 Mbits/sec | 843 Mbits/sec

    iperf3 Network Speed Tests (IPv6):

    Provider | Location (Link) | Send Speed | Recv Speed
    | | |
    Clouvider | London, UK (10G) | 244 Mbits/sec | 480 Mbits/sec
    Online.net | Paris, FR (10G) | 239 Mbits/sec | 839 Mbits/sec
    Hybula | The Netherlands (40G) | 241 Mbits/sec | 805 Mbits/sec
    Uztelecom | Tashkent, UZ (10G) | 221 Mbits/sec | 437 Mbits/sec
    Clouvider | NYC, NY, US (10G) | 257 Mbits/sec | 927 Mbits/sec
    Clouvider | Dallas, TX, US (10G) | 253 Mbits/sec | 908 Mbits/sec
    Clouvider | Los Angeles, CA, US (10G) | 244 Mbits/sec | 658 Mbits/sec

    Geekbench 5 Benchmark Test:

    Test | Value
    |
    Single Core | 751
    Multi Core | 734
    Full Test | https://browser.geekbench.com/v5/cpu/18760064

    London, Uk

    ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##

    Yet-Another-Bench-Script

    v2022-08-20

    https://github.com/masonr/yet-another-bench-script

    ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##

    Sun Nov 20 14:14:38 UTC 2022

    Basic System Information:

    Uptime : 0 days, 0 hours, 1 minutes
    Processor : Intel(R) Xeon(R) CPU D-1521 @ 2.40GHz
    CPU cores : 1 @ 800.097 MHz
    AES-NI : ✔ Enabled
    VM-x/AMD-V : ✔ Enabled
    RAM : 512.0 MiB
    Swap : 256.0 MiB
    Disk : 39.2 GiB
    Distro : Debian GNU/Linux 10 (buster)
    Kernel : 4.19.0

    fio Disk Speed Tests (Mixed R/W 50/50):

    Block Size 4k (IOPS) 64k (IOPS)
    Read 1.25 MB/s (312) 10.76 MB/s (168)
    Write 1.28 MB/s (320) 11.25 MB/s (175)
    Total 2.53 MB/s (632) 22.01 MB/s (343)
    Block Size 512k (IOPS) 1m (IOPS)
    ------ --- ---- ---- ----
    Read 37.80 MB/s (73) 39.06 MB/s (38)
    Write 40.14 MB/s (78) 41.86 MB/s (40)
    Total 77.95 MB/s (151) 80.93 MB/s (78)

    iperf3 Network Speed Tests (IPv4):

    Provider | Location (Link) | Send Speed | Recv Speed
    | | |
    Clouvider | London, UK (10G) | 244 Mbits/sec | 942 Mbits/sec
    Online.net | Paris, FR (10G) | 247 Mbits/sec | 940 Mbits/sec
    Hybula | The Netherlands (40G) | 246 Mbits/sec | 939 Mbits/sec
    Uztelecom | Tashkent, UZ (10G) | 233 Mbits/sec | 825 Mbits/sec
    Clouvider | NYC, NY, US (10G) | 237 Mbits/sec | 900 Mbits/sec
    Clouvider | Dallas, TX, US (10G) | 232 Mbits/sec | 862 Mbits/sec
    Clouvider | Los Angeles, CA, US (10G) | 226 Mbits/sec | 851 Mbits/sec

    iperf3 Network Speed Tests (IPv6):

    Provider | Location (Link) | Send Speed | Recv Speed
    | | |
    Clouvider | London, UK (10G) | 243 Mbits/sec | 928 Mbits/sec
    Online.net | Paris, FR (10G) | 244 Mbits/sec | 925 Mbits/sec
    Hybula | The Netherlands (40G) | 244 Mbits/sec | 926 Mbits/sec
    Uztelecom | Tashkent, UZ (10G) | 225 Mbits/sec | 820 Mbits/sec
    Clouvider | NYC, NY, US (10G) | 236 Mbits/sec | 886 Mbits/sec
    Clouvider | Dallas, TX, US (10G) | 228 Mbits/sec | 856 Mbits/sec
    Clouvider | Los Angeles, CA, US (10G) | 220 Mbits/sec | 838 Mbits/sec

    Geekbench 5 Benchmark Test:

    Test | Value
    |
    Single Core | 671
    Multi Core | 673
    Full Test | https://browser.geekbench.com/v5/cpu/18760513

    Helsinki, Finland

    ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##

    Yet-Another-Bench-Script

    v2022-08-20

    https://github.com/masonr/yet-another-bench-script

    ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##

    Sun Nov 20 09:07:20 EST 2022

    Basic System Information:

    Uptime : 0 days, 0 hours, 0 minutes
    Processor : Intel(R) Xeon(R) Gold 6240L CPU @ 2.60GHz
    CPU cores : 1 @ 2593.904 MHz
    AES-NI : ✔ Enabled
    VM-x/AMD-V : ✔ Enabled
    RAM : 1.0 GiB
    Swap : 256.0 MiB
    Disk : 9.7 GiB
    Distro : Debian GNU/Linux 10 (buster)
    Kernel : 4.19.0

    fio Disk Speed Tests (Mixed R/W 50/50):

    Block Size 4k (IOPS) 64k (IOPS)
    Read 78.18 MB/s (19.5k) 276.70 MB/s (4.3k)
    Write 78.39 MB/s (19.5k) 278.16 MB/s (4.3k)
    Total 156.57 MB/s (39.1k) 554.87 MB/s (8.6k)
    Block Size 512k (IOPS) 1m (IOPS)
    ------ --- ---- ---- ----
    Read 364.53 MB/s (711) 380.14 MB/s (371)
    Write 383.90 MB/s (749) 405.45 MB/s (395)
    Total 748.44 MB/s (1.4k) 785.59 MB/s (766)

    iperf3 Network Speed Tests (IPv4):

    Provider | Location (Link) | Send Speed | Recv Speed
    | | |
    Clouvider | London, UK (10G) | 52.7 Mbits/sec | 68.0 Mbits/sec
    Online.net | Paris, FR (10G) | 53.7 Mbits/sec | 119 Mbits/sec
    Hybula | The Netherlands (40G) | 48.5 Mbits/sec | 422 Mbits/sec
    Uztelecom | Tashkent, UZ (10G) | 31.0 Mbits/sec | 124 Mbits/sec
    Clouvider | NYC, NY, US (10G) | 28.1 Mbits/sec | 49.5 Mbits/sec
    Clouvider | Dallas, TX, US (10G) | 27.4 Mbits/sec | 66.8 Mbits/sec
    Clouvider | Los Angeles, CA, US (10G) | 61.6 Mbits/sec | 91.6 Mbits/sec

    iperf3 Network Speed Tests (IPv6):

    Provider | Location (Link) | Send Speed | Recv Speed
    | | |
    Clouvider | London, UK (10G) | 56.3 Mbits/sec | 68.4 Mbits/sec
    Online.net | Paris, FR (10G) | 33.5 Mbits/sec | 66.7 Mbits/sec
    Hybula | The Netherlands (40G) | 44.4 Mbits/sec | 350 Mbits/sec
    Uztelecom | Tashkent, UZ (10G) | 21.4 Mbits/sec | 79.7 Mbits/sec
    Clouvider | NYC, NY, US (10G) | 20.4 Mbits/sec | 94.8 Mbits/sec
    Clouvider | Dallas, TX, US (10G) | 17.0 Mbits/sec | 48.0 Mbits/sec
    Clouvider | Los Angeles, CA, US (10G) | 29.6 Mbits/sec | 43.9 Mbits/sec

    Geekbench 5 Benchmark Test:

    Test | Value
    |
    Single Core | 647
    Multi Core | 672
    Full Test | https://browser.geekbench.com/v5/cpu/18760525

    Paris, France

    We've added this one in for a bit of fun - Don't expect it to be in stock for long.

    ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##

    Yet-Another-Bench-Script

    v2022-08-20

    https://github.com/masonr/yet-another-bench-script

    ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##

    Sun Nov 20 14:28:49 UTC 2022

    Basic System Information:

    Uptime : 2 days, 2 hours, 42 minutes
    Processor : Intel(R) Atom(TM) CPU N2800 @ 1.86GHz
    CPU cores : 1 @ 1862.000 MHz
    AES-NI : ❌ Disabled
    VM-x/AMD-V : ❌ Disabled
    RAM : 96.0 MiB
    Swap : 256.0 MiB
    Disk : 4.9 GiB
    Distro : Debian GNU/Linux 10 (buster)
    Kernel : 4.19.0

    fio Disk Speed Tests (Mixed R/W 50/50):

    Block Size 4k (IOPS) 64k (IOPS)
    Read 791.00 KB/s (197) 4.73 MB/s (73)
    Write 828.00 KB/s (207) 5.01 MB/s (78)
    Total 1.61 MB/s (404) 9.74 MB/s (151)
    Block Size 512k (IOPS) 1m (IOPS)
    ------ --- ---- ---- ----
    Read 29.89 MB/s (58) 2.47 MB/s (2)
    Write 32.00 MB/s (62) 2.81 MB/s (2)
    Total 61.89 MB/s (120) 5.28 MB/s (4)

    iperf3 Network Speed Tests (IPv4):

    Provider | Location (Link) | Send Speed | Recv Speed
    | | |
    Clouvider | London, UK (10G) | 95.8 Mbits/sec | 94.2 Mbits/sec
    Online.net | Paris, FR (10G) | 95.5 Mbits/sec | 94.0 Mbits/sec
    Hybula | The Netherlands (40G) | 95.5 Mbits/sec | 94.0 Mbits/sec
    Uztelecom | Tashkent, UZ (10G) | 92.7 Mbits/sec | 85.9 Mbits/sec
    Clouvider | NYC, NY, US (10G) | 93.0 Mbits/sec | 92.6 Mbits/sec
    Clouvider | Dallas, TX, US (10G) | 92.2 Mbits/sec | 90.7 Mbits/sec
    Clouvider | Los Angeles, CA, US (10G) | 90.8 Mbits/sec | 89.5 Mbits/sec

    iperf3 Network Speed Tests (IPv6):

    Provider | Location (Link) | Send Speed | Recv Speed
    | | |
    Clouvider | London, UK (10G) | 91.3 Mbits/sec | 88.3 Mbits/sec
    Online.net | Paris, FR (10G) | 92.3 Mbits/sec | 89.4 Mbits/sec
    Hybula | The Netherlands (40G) | 92.4 Mbits/sec | 87.7 Mbits/sec
    Uztelecom | Tashkent, UZ (10G) | 88.5 Mbits/sec | 62.5 Mbits/sec
    Clouvider | NYC, NY, US (10G) | 90.1 Mbits/sec | 82.6 Mbits/sec
    Clouvider | Dallas, TX, US (10G) | 85.7 Mbits/sec | 68.1 Mbits/sec
    Clouvider | Los Angeles, CA, US (10G) | 84.7 Mbits/sec | 62.8 Mbits/sec

  • MicronodeMicronode

    @codelock said:

    @natvps_uk said:
    Launch Locations finalised:

    Locations coming soon:
    Seoul, KR
    Amsterdam, NL

    We've added a small amount of stock for the credits - Think of it like a Pre Launch, these are available for existing Micronode users only.

    No love for natvpsuk customers ?

    Of course, if you want the order link DM me.

  • MicronodeMicronode

    @fluttershy said:

    @natvps_uk said:
    Launch Locations finalised:

    Locations coming soon:
    Seoul, KR
    Amsterdam, NL

    We've added a small amount of stock for the credits - Think of it like a Pre Launch, these are available for existing Micronode users only.

    Who are you using for Seoul and Amsterdam?

    Seoul is likely going to be on Vulturs network. Amsterdam is looking likely to be cloudvider.

  • htgyhtgy OG

    Looks like very interesting, I will definitely have a try.

  • coldcold OG

    so France is also HE.NET tunnel ?

  • MicronodeMicronode

    @cold said:
    so France is also HE.NET tunnel ?

    Finland and France are yes, France was just added for fun - it will be replaced soon with Amsterdam which has native ipv6. Probably within the next 2-3 weeks.

  • fluttershyfluttershy

    @natvps_uk said:

    @fluttershy said:

    @natvps_uk said:
    Launch Locations finalised:

    Locations coming soon:
    Seoul, KR
    Amsterdam, NL

    We've added a small amount of stock for the credits - Think of it like a Pre Launch, these are available for existing Micronode users only.

    Who are you using for Seoul and Amsterdam?

    Seoul is likely going to be on Vulturs network. Amsterdam is looking likely to be cloudvider.

    Very nice upstreams, super tempted by this sale now. Really interesting to see more "cloud like" NAT VMs.

  • soulchiefsoulchief
    edited November 2022

    Just got one of the "presale" credits, looks very interesting. Are the 50% discounts reoccurring or will it renew at full price (which still seems pretty good).
    I also seem Romania in the list now, is this a test or is it a valid location now?

  • nick_nick_

    The Korea location is very tempting. Probably the first NAT VPS provider in that location.

  • contactwajeehcontactwajeeh OG

    Just a suggestion if you can up the disk quota to 24gb instead of 20gb on the micronode credits

  • maobunimaobuni

    The Korea location is very tempting. Probably the first NAT VPS provider in that location.

    https://maobuni.com vps测评|sharing information of vps

  • nick_nick_

    @maobuni said:
    The Korea location is very tempting. Probably the first NAT VPS provider in that location.

    Why copy my post above lol?

  • MicronodeMicronode

    @soulchief said:
    Just got one of the "presale" credits, looks very interesting. Are the 50% discounts reoccurring or will it renew at full price (which still seems pretty good).
    I also seem Romania in the list now, is this a test or is it a valid location now?

    @soulchief said:
    Just got one of the "presale" credits, looks very interesting. Are the 50% discounts reoccurring or will it renew at full price (which still seems pretty good).
    I also seem Romania in the list now, is this a test or is it a valid location now?

    Its reoccurring for the pre-sale but it is just 50% off for the first year come Black Friday.

    Romainia is in the setup phase, might be ready before launch as a very last minute location!

  • chimichurrichimichurri
    edited November 2022

    @nick_ said:

    @maobuni said:
    The Korea location is very tempting. Probably the first NAT VPS provider in that location.

    Why copy my post above lol?

    The Korea location is very tempting. Probably the first NAT VPS provider in that location.

    Contribute your idling VPS/dedi (link), Android (link) or iOS (link) devices to medical research

  • MicronodeMicronode
    edited November 2022

    Seoul

    Yabs:

    ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##

    Yet-Another-Bench-Script

    v2022-08-20

    https://github.com/masonr/yet-another-bench-script

    ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##

    Mon Nov 21 12:12:28 UTC 2022

    Basic System Information:

    Uptime : 0 days, 0 hours, 0 minutes
    Processor : Intel Xeon Processor (Cascadelake)
    CPU cores : 1 @ 2999.998 MHz
    AES-NI : ✔ Enabled
    VM-x/AMD-V : ❌ Disabled
    RAM : 512.0 MiB
    Swap : 256.0 MiB
    Disk : 19.6 GiB
    Distro : Debian GNU/Linux 10 (buster)
    Kernel : 4.19.0

    fio Disk Speed Tests (Mixed R/W 50/50):

    Block Size 4k (IOPS) 64k (IOPS)
    Read 48.79 MB/s (12.1k) 204.18 MB/s (3.1k)
    Write 48.86 MB/s (12.2k) 205.25 MB/s (3.2k)
    Total 97.65 MB/s (24.4k) 409.43 MB/s (6.3k)
    Block Size 512k (IOPS) 1m (IOPS)
    ------ --- ---- ---- ----
    Read 334.78 MB/s (653) 379.21 MB/s (370)
    Write 352.57 MB/s (688) 404.47 MB/s (394)
    Total 687.36 MB/s (1.3k) 783.68 MB/s (764)

    iperf3 Network Speed Tests (IPv4):

    Provider | Location (Link) | Send Speed | Recv Speed
    | | |
    Clouvider | London, UK (10G) | 599 Mbits/sec | 738 Mbits/sec
    Online.net | Paris, FR (10G) | 1.02 Gbits/sec | 916 Mbits/sec
    Hybula | The Netherlands (40G) | 594 Mbits/sec | 689 Mbits/sec
    Uztelecom | Tashkent, UZ (10G) | 1.56 Gbits/sec | 4.41 Mbits/sec
    Clouvider | NYC, NY, US (10G) | 921 Mbits/sec | 1.10 Gbits/sec
    Clouvider | Dallas, TX, US (10G) | 938 Mbits/sec | 1.17 Gbits/sec
    Clouvider | Los Angeles, CA, US (10G) | 1.15 Gbits/sec | 1.31 Gbits/sec

    iperf3 Network Speed Tests (IPv6):

    Provider | Location (Link) | Send Speed | Recv Speed
    | | |
    Clouvider | London, UK (10G) | 150 Mbits/sec | 640 Mbits/sec
    Online.net | Paris, FR (10G) | 162 Mbits/sec | 752 Mbits/sec
    Hybula | The Netherlands (40G) | 151 Mbits/sec | 554 Mbits/sec
    Uztelecom | Tashkent, UZ (10G) | 151 Mbits/sec | 430 Mbits/sec
    Clouvider | NYC, NY, US (10G) | 196 Mbits/sec | 698 Mbits/sec
    Clouvider | Dallas, TX, US (10G) | 201 Mbits/sec | 788 Mbits/sec
    Clouvider | Los Angeles, CA, US (10G) | 253 Mbits/sec | 870 Mbits/sec

    Geekbench 5 test failed. Run manually to determine cause.

    We've added Seoul on a CPU Dedicated Vultur instance, this will be migrated to a physical node when possible. Please be aware if using this location that a migration will be taking place. We've also limited the stock for this one, these limits will be lifted once we move to dedicated hardware.

    This really is the launch locations now:

    Amsterdam is still planned but we don't have a timeline.

    Romania is a bonus location provided by @Calin - This will hopefully be setup before launch - Please note that this location will be IPv4 NAT Only!

Sign In or Register to comment.