TierHive General thread | Discuss, Updates, questions & Suggestions | LATEST: new location USA WEST
AnthonySmith
AdministratorHosting ProviderOGSenpai
I was about to post a new offer, really more to provide some updates, it's probably not good, @msatt was probably right 
I decided to just post a single TierHive thread instead. I might still post some offers and specials from time to time, but for now, I will keep it contained to a single thread for updates etc, as most offer threads seem to turn in to that anyway.
So what's been going on recently?
Updates in live bullet points to keep it simple
- IPv6 was added, its free, you get 1 x /64 per location and can then add individual addresses from that /64 to any VPS in that location, elastic IPv6 coming based on user take-up over 6 months, Current user take-up on IPv6 is 1.5% This is measured by the number of users that have allocated at least 1 IPv6 address to a VPS.
- Users can now allocate 5 additional NAT ports in addition to the SSH port.
- Users can now manage the internal forwarding of ports, so for example, if you are allocated 2345 you can have that forward to 8080 internal if you want.
- You can now download your SSL certificate from the HAProxy directly. I don't fully understand why anyone wants this, but it's a very popular request.
- We have introduced burst buckets on IOPS and Network as of today for network and disk, you now can now double your tier limit for 5 seconds continuously, any VPS that existed before today will need to change their network and disk tier down and up again to gain access to this (Sorry, it's a pain in the ass to do restrospectivley) so if medium tier is on 300mbit for example you will be able to do 600mbit for 5 seconds sustained, then when you idle again below 300mbit your bucket empties and you can burst up again on demand. (Hope I explained that ok)
- You can now copy the IP, Port or whole ssh string separately in the UI, aparently that was annoying for Windows users.
- Crypto mining detectors are now deployed on all nodes, load dropped globally by 50% in the first hour
haha.. just wow. - We decided to remove the network disk options and the sql service, and the mail relay, even fewer people use this than use IPv6 so it's not really worth the code maintenance and complexity. It might come back one day, for now its not worth it, you will still be able to attack backups as network disks.
- We plan to decouple the backups from the VPS so that you can put a VPS disk image on cold storage.
- Added an FAQ which is being built following support tickets to provide real answers without needing to open a ticket, but you can if you want anyway.
Things we are playing with now that may make it out of the sand pit version.
- A static hosting layer, which will likely just be free to any user with a positive balance, details still in progress.
- We want to start charging less for shut down VPS, obviously we still maintain the mesh elements, the disk/data, and the firewall and port reservations and have to account for the fact that you can boot it at any time, but initially I am thinking 50% discount for powered off servers, it helps us keep it cheap if you make the effort to shut down when not using it.
- unikernels - not me playing with this, I think its an interesting idea but lets see where it goes
- Bring your own image automation, this will have 2 modes, give us the key or password for another running VPS somewhere else and we will try to import it, obviously its best if thats in rescue mode but not absolutely needed, and just give us the url to a qcow2 or raw image and we will do the rest.
- long long long term, personal project I am working on multiplexing VNC for audio into a custom html5 client using a single WebSocket, but this is actually sort of for another project but would be cool in TierHive.
- It makes me very sad how few people have enabled DHCP or mess with the DHCP options for your scopes, it took me bloody ages to get it working over the whole /24 regardless of location, so I will probably end up being free, if people still don't use it, ah well, its done, nothing new to add.
- network page for network tests and mesh status.
And thats it, thats my update, probably missed 100 minor things but at least I have a thread to do it in now.
Linky: https://tierhive.com/
TierHive - Hourly VPS - NAT Native - /24 per customer - DE, UK, SG, CA, USA x3, FR, AU, PL, NL
FREE tokens on sign up, try before you buy. | Join us on Reddit
Tagged:
Comments
Re: #4: That will enable one to setup SSL on their IPv6 network and add native access to the box outside of NAT using the same certificate. It's a feature, not a bug.
#5: Why recreate the world? streaming already exists. https://gavv.net/articles/roc-0.4/
#6: Honestly, the DHCP caused random hanging with my iPXE booting, and it confused the hell out of the Debian 12 template when I turned it off. It's also a use of system resources on a shared server where we're paying pennies (or less) via microtransactions, so why not save that 0.00005/hr and just not be lazy one time during installation.
"It's a hard life- to be a stick insect." - Karl Pilkington
oh nice, the 1.5% will be happy then! I did not think of that.
Thanks for the link, saved, when I get back to that mental space I will review it properly, scan read shows that yes, indeed, I am probably reinventing the wheel.
Thanks, I will need to look into that, I did not know.
TierHive - Hourly VPS - NAT Native - /24 per customer - DE, UK, SG, CA, USA x3, FR, AU, PL, NL
FREE tokens on sign up, try before you buy. | Join us on Reddit
This is a question, not a request:
Why a /56 and not a /64
TierHive - Hourly VPS - NAT Native - /24 per customer - DE, UK, SG, CA, USA x3, FR, AU, PL, NL
FREE tokens on sign up, try before you buy. | Join us on Reddit
Usually you assign a /64 per host. Logically then if you have more than one host you get a larger allocation.
Well, the longer answer is:
Initially, there were no plans to implement IPv6 at all in Alpha, because I know first-hand that it very rarely makes it into double-digit percentages of use in budget hosting.
But it was the constant burning question, when IPv6? I have responded to everyone that opened a ticket about it that I could find, only 1 of them enabled it. I might be being reductive but it just feels like a knee jerk question and as such a loud minority subject, time will tell.
From a technical stand point tierhive is not enterprise grade so we use budget hardware and providers up stream, this brings limitations one of which was not being able to get the size ranges I wanted in all cases and I did not want some locations to be a /56 and some a /64 its confusing and messy.
Personally, I just felt a /64 per location was enough; it has absolutely no real-world limitations that apply to TierHive and will allow a drop in replacement (hopefully) when we own our own IPv6/4 when we get to Beta.
If the use rate is not over 5% by 2027 though, IPv6 may be cut entirely, even if it means going on yoursunnys blacklist
I hope that is a better explanation.
TierHive - Hourly VPS - NAT Native - /24 per customer - DE, UK, SG, CA, USA x3, FR, AU, PL, NL
FREE tokens on sign up, try before you buy. | Join us on Reddit
Yeah, I kinda guessed that upstream allocations were the reason for using /64s.
If /when we get our own allocations that we fully own and control, it will change to a global /48 I guess that you can do what you want with, but really I still dont believe IPv6 will be very popular.
TierHive - Hourly VPS - NAT Native - /24 per customer - DE, UK, SG, CA, USA x3, FR, AU, PL, NL
FREE tokens on sign up, try before you buy. | Join us on Reddit
They're a pain in the ass to manage. We get it. Sour grapes and all.
"It's a hard life- to be a stick insect." - Karl Pilkington
malic acid injected raisins
TierHive - Hourly VPS - NAT Native - /24 per customer - DE, UK, SG, CA, USA x3, FR, AU, PL, NL
FREE tokens on sign up, try before you buy. | Join us on Reddit
My entire life I'd been enunciating it as malted acid. Thankful for my drawl. They probably thought I was just a hick and not a dumbass.
E: Where can I find my SSL certificates? It's no showing immediately under HAProxy or under the VPS.
"It's a hard life- to be a stick insect." - Karl Pilkington
>
Click "View SSL" and you should see a download option
TierHive - Hourly VPS - NAT Native - /24 per customer - DE, UK, SG, CA, USA x3, FR, AU, PL, NL
FREE tokens on sign up, try before you buy. | Join us on Reddit
I do not.
"It's a hard life- to be a stick insect." - Karl Pilkington
attach?
Hey teamacc. You're a dick. (c) Jon Biloh, 2020.
Nah. Like Pokemon.
"It's a hard life- to be a stick insect." - Karl Pilkington
Not sure if trolling or.. just using firefox and need a hard refresh?
TierHive - Hourly VPS - NAT Native - /24 per customer - DE, UK, SG, CA, USA x3, FR, AU, PL, NL
FREE tokens on sign up, try before you buy. | Join us on Reddit
Maybe the 100th time you have corrected my English in the last 10 years haha, thanks!
TierHive - Hourly VPS - NAT Native - /24 per customer - DE, UK, SG, CA, USA x3, FR, AU, PL, NL
FREE tokens on sign up, try before you buy. | Join us on Reddit
Chrome, and I did a Shift-F5.
E: Any chance of using an API or something to snag this otherwise? Using the browser itself and doing an scp when they drop certificates down to ~45 days is going to be abysmal.
"It's a hard life- to be a stick insect." - Karl Pilkington
Yeah, the API endpoint is there, but I made a hard commitment to not release the user-facing API until beta. Given the sensitivity of the SSL I don't want to do any dumb ass hacks myself.
TierHive - Hourly VPS - NAT Native - /24 per customer - DE, UK, SG, CA, USA x3, FR, AU, PL, NL
FREE tokens on sign up, try before you buy. | Join us on Reddit
How do we manage the allocated port? I can't find any interface to change the allocated port to forward to something else.
API access to view, allocate and re-allocate these ports would be good too!
Not that it really matters, but I often try to use the same port number. Since I don't know what it will be, I add it so I can see what port it will assign, then delete it, then add it again.
It's on the VPS management page for the specific VPS, in the server information container, top right
TierHive - Hourly VPS - NAT Native - /24 per customer - DE, UK, SG, CA, USA x3, FR, AU, PL, NL
FREE tokens on sign up, try before you buy. | Join us on Reddit
Anything the UI can do the API can do, it has been built from day 1 on API first UI second.
The big reason the API is not public during Alpha is that things are changing constantly in Alpha and we are not wanting to entertain support of the API not to mention the pen testing to be done.
When beta is live later in 2026 or early 2027 it will be live with a full cli version.
TierHive - Hourly VPS - NAT Native - /24 per customer - DE, UK, SG, CA, USA x3, FR, AU, PL, NL
FREE tokens on sign up, try before you buy. | Join us on Reddit
One thing I've noticed; if I do a reboot from the command line on a freshly provisioned vps, it just shuts down but doesn't reboot. Then I need to boot it from the control panel. I need to remember to do the first reboot from the control panel. After the first time, it's ok from the command line.
Which template are you using? Whenever I did a shutdown on the debian 12 template it would crash so I'd have to log back in as root and do a power loff.
"It's a hard life- to be a stick insect." - Karl Pilkington
I'm using Alpine 3.23.2.
And I just did it again, despite just posting that, and wondered why it wasn't rebooting.
I prefer Debian, but I usually use Alpine for low memory stuff.
Excellent Architectural approach on being API first; kudos!
I can appreciate the cautious approach you have on releasing the APIs, as it could be a management and security nightmare.
Yeah its a known issue, its been on my list for a while, I will move it up. I know why, I just need to deal with it.
TierHive - Hourly VPS - NAT Native - /24 per customer - DE, UK, SG, CA, USA x3, FR, AU, PL, NL
FREE tokens on sign up, try before you buy. | Join us on Reddit
We think /64 per site for TierHive is appropriate.
We use TierHive's IPv6. Though we are not one of those who asked for it in a ticket.
We're the source, no cap. Address us: We/Our/Ours.
https://lowendspirit.com/discussion/comment/221016/#Comment_221016