A customer reported an issue which put me down a rabbit hole and I discovered a strange bug, if you add a domain on port 80 and then another using the same backend on a different port but the same vps/ip you get an odd situation where only 1 is checked and then the wrong one is marked online.
This has been fixed, we have stronger logic now so single backend, multi domain, multi ports works now instead of randomly going offline after around 6 hours.
We did a few more robustness checks on this too to generally improve backend online logic.
Additionally, we were getting load spikes on the HAProxy servers, causing periodic high response times. The root cause has been found, essentially an sqlite db on the haproxy server for stats did not scale well, its only job is to show us stats on the admin side per domain for requests and responce times and actually while it seemed like a great idea at the time, we never expected it to run at this scale so it has 54 million rows and is read multiple times every few minutes to pull data from a timeperiod. This is being stopped and stripped out, we can do it via cli if we need to know.
All in all the HAProxy server will become more responsive and reliable when this is finished, hoping to push to production and clean up today without any live disruption.
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. | Static Hosting Free for life: https://tierhive.com/static-hosting/
A customer reported an issue which put me down a rabbit hole and I discovered a strange bug, if you add a domain on port 80 and then another using the same backend on a different port but the same vps/ip you get an odd situation where only 1 is checked and then the wrong one is marked online.
Thanks for the quick fix. Seems to be working great now
Could you please confirm if you have already applied the security fix for the Januscape vulnerability (CVE-2026-53359) on your infrastructure/hypervisors?
Could you please confirm if you have already applied the security fix for the Januscape vulnerability (CVE-2026-53359) on your infrastructure/hypervisors?
Thanks
We are going to start the reboots later today and downtime will be as long as it needs to be.
Expect issues.
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. | Static Hosting Free for life: https://tierhive.com/static-hosting/
We hit some snags early on, we have been using this as an opportunity in real time to improve things, around 20 changes have gone into production to help the self-healing, did not go quite to plan for the first few nodes, but we stuck with it, as how often do you get an opportunity to reboot your entire infrastructure in an orderly manner eh!
Now by location 6 we are pretty sure we have it nailed down, meaning any unexpected outages, power cycles, hangs, and reboots should self-heal much faster without human intervention in some cases.
I have zero doubt the clever/dumb balance will be restored when we realise we missed something tomorrow when customers open tickets, but, you know, we are in Alpha for a reason.
We are going to continue work on it over the weekend and expect to be all patched up by Monday, by which point we expect at least 2 more CVE's that will require an update and reboot
Seriously, though, if this happens, we are actually considering doing live patching for Debian stable, if this one has been there for 16 years, imagine what else is going to hit....
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. | Static Hosting Free for life: https://tierhive.com/static-hosting/
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. | Static Hosting Free for life: https://tierhive.com/static-hosting/
IPv6 now seems working again in Hillsboro for me as well.
The link-local IPv6 router address on NetBSD has been statically configured, and the address seems to have changed.
If the link-local IPv6 router address changes again, maybe I could have fun trying NetBSD's dhcpcd(8) to build the route dynamically. . . .
Thanks again @david3! Thanks to @AnthonySmith for TierHive! Lots of Low End fun!
Best wishes and kindest regards!
Tom
hil# date
Sun Jul 12 19:14:24 UTC 2026
hil# uptime
7:14PM up 1 min, 1 user, load averages: 0.13, 0.04, 0.01
hil# ping6 -c 2 ipv6.google.com
PING6(56=40+8+8 bytes) [hil] --> 2607:f8b0:4023:100d::64
16 bytes from 2607:f8b0:4023:100d::64, icmp_seq=0 hlim=102 time=57.382 ms
16 bytes from 2607:f8b0:4023:100d::64, icmp_seq=1 hlim=102 time=57.291 ms
--- ipv6.l.google.com ping6 statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 57.291/57.337/57.382/0.064 ms
hil#
I'm using Alpine, and I didn't do anything special to statically configure the link-local address. I think that is auto configured. This is my /etc/network/interfaces:
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 10.1.80.10/24
dns-nameservers 76.76.2.2 76.76.10.2
post-up ip route add default via 10.1.80.1 || true
pre-down ip route del default via 10.1.80.1 || true
iface eth0 inet6 static
address {ipv6-address}
gateway {ipv6-gateway}
IPv6 now seems working again in Hillsboro for me as well.
The link-local IPv6 router address on NetBSD has been statically configured, and the address seems to have changed.
If the link-local IPv6 router address changes again, maybe I could have fun trying NetBSD's dhcpcd(8) to build the route dynamically. . . .
I'm using Alpine, and I didn't do anything special to statically configure the link-local address. I think that is auto configured. This is my /etc/network/interfaces:
When I last tried NetBSD on TierHive, the IPv6 configuration as shown in the panel for IPv6 didn't work, but using the link-local address of the router instead made it work. Maybe I was just unlucky at that time and there was some general IPv6 issue on TierHive or there was a compatibility issue between NetBSD and how TierHive has configured IPv6. There are just too many unknowns.
@WSS said:
$ ping 2a11:6c7:2300:9508::1
PING 2a11:6c7:2300:9508::1 (2a11:6c7:2300:9508::1) 56 data bytes
From 2a11:6c7:2300:9508::70 icmp_seq=1 Destination unreachable: Address unreachable
ping: sendmsg: No route to host
Vint Hill again.
thanks, stand by.
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. | Static Hosting Free for life: https://tierhive.com/static-hosting/
IPv6 now seems working again in Hillsboro for me as well.
The link-local IPv6 router address on NetBSD has been statically configured, and the address seems to have changed.
If the link-local IPv6 router address changes again, maybe I could have fun trying NetBSD's dhcpcd(8) to build the route dynamically. . . .
I'm using Alpine, and I didn't do anything special to statically configure the link-local address. I think that is auto configured. This is my /etc/network/interfaces:
When I last tried NetBSD on TierHive, the IPv6 configuration as shown in the panel for IPv6 didn't work, but using the link-local address of the router instead made it work. Maybe I was just unlucky at that time and there was some general IPv6 issue on TierHive or there was a compatibility issue between NetBSD and how TierHive has configured IPv6. There are just too many unknowns.
Honestly, we were just talking about it yesterday, Ipv6 was kind of forced in to alpha before we were ready because so much noise was made about ipv6.
In hindsight, it was a huge mistake, in the end I could not make it work as I wanted with the restrictions we have right now, on top of that only 1.8% of people even allocate a /64 the actual use figure is way lower.
It has periods of shameful stability as a result of us not having enough control, and it is by far the biggest management and ticket burden, that is in part our fault, but its not a problem we can easily fix. Mostly, people just open a ticket saying their IPv6 did not auto-configure and then people need lessons on how to do it, or reports of it being down and actually its not but that launches a full investigation.
So really, we have kind of backed ourselves into a corner, but for such a tiny amount of tthe customer base actually really using it, we are thinking about cutting our losses before we make things worse and dropping IPv6, we would obviously refund any credit to anyone that bought credit because we have IPv6 and then relaunching IPv6 properly when we finish our own ASN registration and have our own range that we can directly manage rather than relying on to many external and uncontroable factors.
This has not been fully decided yet, but honestly, it will probably go this way.
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. | Static Hosting Free for life: https://tierhive.com/static-hosting/
@WSS said:
$ ping 2a11:6c7:2300:9508::1
PING 2a11:6c7:2300:9508::1 (2a11:6c7:2300:9508::1) 56 data bytes
From 2a11:6c7:2300:9508::70 icmp_seq=1 Destination unreachable: Address unreachable
ping: sendmsg: No route to host
Vint Hill again.
thanks, stand by.
fixed
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. | Static Hosting Free for life: https://tierhive.com/static-hosting/
If IPv6 is becoming such a headache- just turn it off and tell people "Later." - It'd be annoying for me, but I can live with NAT since the whole point is a backup running through HAProxy anyhow.
IPv6 now seems working again in Hillsboro for me as well.
The link-local IPv6 router address on NetBSD has been statically configured, and the address seems to have changed.
If the link-local IPv6 router address changes again, maybe I could have fun trying NetBSD's dhcpcd(8) to build the route dynamically. . . .
I'm using Alpine, and I didn't do anything special to statically configure the link-local address. I think that is auto configured. This is my /etc/network/interfaces:
When I last tried NetBSD on TierHive, the IPv6 configuration as shown in the panel for IPv6 didn't work, but using the link-local address of the router instead made it work. Maybe I was just unlucky at that time and there was some general IPv6 issue on TierHive or there was a compatibility issue between NetBSD and how TierHive has configured IPv6. There are just too many unknowns.
Honestly, we were just talking about it yesterday, Ipv6 was kind of forced in to alpha before we were ready because so much noise was made about ipv6.
In hindsight, it was a huge mistake, in the end I could not make it work as I wanted with the restrictions we have right now, on top of that only 1.8% of people even allocate a /64 the actual use figure is way lower.
It has periods of shameful stability as a result of us not having enough control, and it is by far the biggest management and ticket burden, that is in part our fault, but its not a problem we can easily fix. Mostly, people just open a ticket saying their IPv6 did not auto-configure and then people need lessons on how to do it, or reports of it being down and actually its not but that launches a full investigation.
So really, we have kind of backed ourselves into a corner, but for such a tiny amount of tthe customer base actually really using it, we are thinking about cutting our losses before we make things worse and dropping IPv6, we would obviously refund any credit to anyone that bought credit because we have IPv6 and then relaunching IPv6 properly when we finish our own ASN registration and have our own range that we can directly manage rather than relying on to many external and uncontroable factors.
This has not been fully decided yet, but honestly, it will probably go this way.
We can vouch for NetBSD being kind of hard with the IPv6 addresses. Our attempts at providing a usable template with IPv6 were among the hardest we've done for any OS on the new panel. It's hard, indeed.
You will really want to have a go at DHCPv6 to reduce tickets and increase reliability, and to test and test and re-test provisioning: sometimes it failed in different ways just because it could...
Honestly I stopped using tierhive cause of the ipv6 issues as well. The latency for IPv6 is higher thæn normal, auto configuration doesn't work and even after manual configuration, some US regions IPv6 did not work. Well, hope it'll get better once it's out of alpha...
I've been using tierhive for a while now and I'm amazed with the service, it's been more stable than quite a few "production ready" hosts. Is there a reason, however, that you charge VAT even for customers outside EU? It's a minor thing really, but I've never seen it done before.
@kickinit68 said:
I've been using tierhive for a while now and I'm amazed with the service, it's been more stable than quite a few "production ready" hosts. Is there a reason, however, that you charge VAT even for customers outside EU? It's a minor thing really, but I've never seen it done before.
We use a merchant of record, FastSpring. Technically, you are their customer, not ours, and FastSpring is our only customer; this allows us to not require any of your personal data.
They detect your location during checkout based on your IP and the details you enter, and they charge you the VAT or tax rate of your local country, or state, fastSpring then pay all taxes on our behalf, making our bookkeeping and accounting incredibly simple.
Similar to paddle, lemonsqueezy and a few others, we found that FastSpring was the most "human" company to work with in the end even though the rate is slightly higher per transaction, the additional fees cost less than a part-time bookkeeper and accountant meaning I can do everything myself and keep the operating costs lower and you guys get a lower price.
So You were only charged VAT if you are in a country that has a standard VAT rate and you were charged at your country's VAT rate, the VAT you paid was then given to your government directly
I hope that clarifies.
Obviously, if you are hiding your location well, then this is also a side effect: you are charged the VAT rate of the location you are hiding in IP address-wise and you are acting as a tax proxy for that contry, and I am sure they will thank you for 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. | Static Hosting Free for life: https://tierhive.com/static-hosting/
Payments, tagging @ehab as he initially got me started on this bit:
Amount is now shown as an estimate in GBP, EUR and USD, live.
Also, you can now redeem a coupon in the same place, hopefully making that less disjointed.
We removed the need for an account to be a certain age to use a coupon, and using a coupon now activates a subnet and mesh for you as an end user, just like an actual payment; there is no need to open a support ticket.
The token amount in the header bar now link to the billing page.
Other stuff:
We untied the VPS from the recipe it was deployed on, meaning when you reinstall, you just reinstall; it does not deploy the recipe again.
Apart from that, the latest tranche of work was almost all admin side, a lot around improving HAProxy sensitivity, a final push (make or break) for IPv6 stability, and a bit of added logic in the haproxy side to avoid SSL generation failures.
Was passed 10000 total customers a while back (in terms of registrations) but it was a busy week so it just happened without being noticed, keep in mind we delete accounts that are considered dormant with no active service or activity, still in batches, still manually as we keep finding exceptions to account for so dont want to risk the automation yet, which actuall puts us at around the 5000 mark in terms of what we consider to be live active customers (Have credit, active service now or within the last 90 days)
We turned off the free tokens on the 3rd July, signups slowed by around 30% which was to be expected, however node loads also dropped by around the same amount and remained there while daily average takings remained exactly on track, we will probably open up the free trial credit again anyway for periods of time when appropriate but we will also likely restrict the available locations and services for the free tokens.
Looking for new locations all the time, if anyone has any suggestions along with hosts to consider (dedicated or VDS only please), always let us know, if you are a host and you think it's worth a chat about a location then drop me a PM.
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. | Static Hosting Free for life: https://tierhive.com/static-hosting/
Extra resources added to singapore, available to add VPS now, the load balancers will put every new VPS on the new node for a while if anyone wants or needs a second IP in SG.
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. | Static Hosting Free for life: https://tierhive.com/static-hosting/
Comments
Few Haproxy updates.
A customer reported an issue which put me down a rabbit hole and I discovered a strange bug, if you add a domain on port 80 and then another using the same backend on a different port but the same vps/ip you get an odd situation where only 1 is checked and then the wrong one is marked online.
This has been fixed, we have stronger logic now so single backend, multi domain, multi ports works now instead of randomly going offline after around 6 hours.
We did a few more robustness checks on this too to generally improve backend online logic.
Additionally, we were getting load spikes on the HAProxy servers, causing periodic high response times. The root cause has been found, essentially an sqlite db on the haproxy server for stats did not scale well, its only job is to show us stats on the admin side per domain for requests and responce times and actually while it seemed like a great idea at the time, we never expected it to run at this scale so it has 54 million rows and is read multiple times every few minutes to pull data from a timeperiod. This is being stopped and stripped out, we can do it via cli if we need to know.
All in all the HAProxy server will become more responsive and reliable when this is finished, hoping to push to production and clean up today without any live disruption.
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. | Static Hosting Free for life: https://tierhive.com/static-hosting/
Thanks for the quick fix. Seems to be working great now
Just curious, is there a way to clear the announcements?
The "keep your recipes up to date" one is always marked new.
Go under account settings 👍
Ah, got it, thanks.
Hi @AnthonySmith ,
Could you please confirm if you have already applied the security fix for the Januscape vulnerability (CVE-2026-53359) on your infrastructure/hypervisors?
Thanks
We are going to start the reboots later today and downtime will be as long as it needs to be.
Expect issues.
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. | Static Hosting Free for life: https://tierhive.com/static-hosting/
We hit some snags early on, we have been using this as an opportunity in real time to improve things, around 20 changes have gone into production to help the self-healing, did not go quite to plan for the first few nodes, but we stuck with it, as how often do you get an opportunity to reboot your entire infrastructure in an orderly manner eh!
Now by location 6 we are pretty sure we have it nailed down, meaning any unexpected outages, power cycles, hangs, and reboots should self-heal much faster without human intervention in some cases.
I have zero doubt the clever/dumb balance will be restored when we realise we missed something tomorrow when customers open tickets, but, you know, we are in Alpha for a reason.
We are going to continue work on it over the weekend and expect to be all patched up by Monday, by which point we expect at least 2 more CVE's that will require an update and reboot
Seriously, though, if this happens, we are actually considering doing live patching for Debian stable, if this one has been there for 16 years, imagine what else is going to hit....
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. | Static Hosting Free for life: https://tierhive.com/static-hosting/
All patched up, might be a bit unpredictable for a few hours while the mesh corrections run in batches
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. | Static Hosting Free for life: https://tierhive.com/static-hosting/
Could anyone please confirm whether IPv6 is working in Hillsboro? Thanks!
It's working for me.
Thanks @david3!
IPv6 now seems working again in Hillsboro for me as well.
The link-local IPv6 router address on NetBSD has been statically configured, and the address seems to have changed.
If the link-local IPv6 router address changes again, maybe I could have fun trying NetBSD's dhcpcd(8) to build the route dynamically. . . .
Thanks again @david3! Thanks to @AnthonySmith for TierHive! Lots of Low End fun!
Best wishes and kindest regards!
Tom
I'm using Alpine, and I didn't do anything special to statically configure the link-local address. I think that is auto configured. This is my /etc/network/interfaces:
$ ping 2a11:6c7:2300:9508::1
PING 2a11:6c7:2300:9508::1 (2a11:6c7:2300:9508::1) 56 data bytes
From 2a11:6c7:2300:9508::70 icmp_seq=1 Destination unreachable: Address unreachable
ping: sendmsg: No route to host
Vint Hill again.
"It's a hard life- to be a stick insect." - Karl Pilkington
When I last tried NetBSD on TierHive, the IPv6 configuration as shown in the panel for IPv6 didn't work, but using the link-local address of the router instead made it work. Maybe I was just unlucky at that time and there was some general IPv6 issue on TierHive or there was a compatibility issue between NetBSD and how TierHive has configured IPv6. There are just too many unknowns.
thanks, stand by.
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. | Static Hosting Free for life: https://tierhive.com/static-hosting/
Honestly, we were just talking about it yesterday, Ipv6 was kind of forced in to alpha before we were ready because so much noise was made about ipv6.
In hindsight, it was a huge mistake, in the end I could not make it work as I wanted with the restrictions we have right now, on top of that only 1.8% of people even allocate a /64 the actual use figure is way lower.
It has periods of shameful stability as a result of us not having enough control, and it is by far the biggest management and ticket burden, that is in part our fault, but its not a problem we can easily fix. Mostly, people just open a ticket saying their IPv6 did not auto-configure and then people need lessons on how to do it, or reports of it being down and actually its not but that launches a full investigation.
So really, we have kind of backed ourselves into a corner, but for such a tiny amount of tthe customer base actually really using it, we are thinking about cutting our losses before we make things worse and dropping IPv6, we would obviously refund any credit to anyone that bought credit because we have IPv6 and then relaunching IPv6 properly when we finish our own ASN registration and have our own range that we can directly manage rather than relying on to many external and uncontroable factors.
This has not been fully decided yet, but honestly, it will probably go this way.
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. | Static Hosting Free for life: https://tierhive.com/static-hosting/
fixed
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. | Static Hosting Free for life: https://tierhive.com/static-hosting/
If IPv6 is becoming such a headache- just turn it off and tell people "Later." - It'd be annoying for me, but I can live with NAT since the whole point is a backup running through HAProxy anyhow.
"It's a hard life- to be a stick insect." - Karl Pilkington
We can vouch for NetBSD being kind of hard with the IPv6 addresses. Our attempts at providing a usable template with IPv6 were among the hardest we've done for any OS on the new panel. It's hard, indeed.
You will really want to have a go at DHCPv6 to reduce tickets and increase reliability, and to test and test and re-test provisioning: sometimes it failed in different ways just because it could...
Maybe you should just tell those retards to fuck off?
"It's a hard life- to be a stick insect." - Karl Pilkington
Honestly I stopped using tierhive cause of the ipv6 issues as well. The latency for IPv6 is higher thæn normal, auto configuration doesn't work and even after manual configuration, some US regions IPv6 did not work. Well, hope it'll get better once it's out of alpha...
I've been using tierhive for a while now and I'm amazed with the service, it's been more stable than quite a few "production ready" hosts. Is there a reason, however, that you charge VAT even for customers outside EU? It's a minor thing really, but I've never seen it done before.
We use a merchant of record, FastSpring. Technically, you are their customer, not ours, and FastSpring is our only customer; this allows us to not require any of your personal data.
They detect your location during checkout based on your IP and the details you enter, and they charge you the VAT or tax rate of your local country, or state, fastSpring then pay all taxes on our behalf, making our bookkeeping and accounting incredibly simple.
Similar to paddle, lemonsqueezy and a few others, we found that FastSpring was the most "human" company to work with in the end even though the rate is slightly higher per transaction, the additional fees cost less than a part-time bookkeeper and accountant meaning I can do everything myself and keep the operating costs lower and you guys get a lower price.
So You were only charged VAT if you are in a country that has a standard VAT rate and you were charged at your country's VAT rate, the VAT you paid was then given to your government directly
I hope that clarifies.
Obviously, if you are hiding your location well, then this is also a side effect: you are charged the VAT rate of the location you are hiding in IP address-wise and you are acting as a tax proxy for that contry, and I am sure they will thank you for 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. | Static Hosting Free for life: https://tierhive.com/static-hosting/
A few updates on TierHive in general:
Payments, tagging @ehab as he initially got me started on this bit:
Amount is now shown as an estimate in GBP, EUR and USD, live.
Also, you can now redeem a coupon in the same place, hopefully making that less disjointed.
We removed the need for an account to be a certain age to use a coupon, and using a coupon now activates a subnet and mesh for you as an end user, just like an actual payment; there is no need to open a support ticket.
The token amount in the header bar now link to the billing page.
Other stuff:
We untied the VPS from the recipe it was deployed on, meaning when you reinstall, you just reinstall; it does not deploy the recipe again.
Apart from that, the latest tranche of work was almost all admin side, a lot around improving HAProxy sensitivity, a final push (make or break) for IPv6 stability, and a bit of added logic in the haproxy side to avoid SSL generation failures.
Was passed 10000 total customers a while back (in terms of registrations) but it was a busy week so it just happened without being noticed, keep in mind we delete accounts that are considered dormant with no active service or activity, still in batches, still manually as we keep finding exceptions to account for so dont want to risk the automation yet, which actuall puts us at around the 5000 mark in terms of what we consider to be live active customers (Have credit, active service now or within the last 90 days)
We turned off the free tokens on the 3rd July, signups slowed by around 30% which was to be expected, however node loads also dropped by around the same amount and remained there while daily average takings remained exactly on track, we will probably open up the free trial credit again anyway for periods of time when appropriate but we will also likely restrict the available locations and services for the free tokens.
Looking for new locations all the time, if anyone has any suggestions along with hosts to consider (dedicated or VDS only please), always let us know, if you are a host and you think it's worth a chat about a location then drop me a PM.
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. | Static Hosting Free for life: https://tierhive.com/static-hosting/
Extra resources added to singapore, available to add VPS now, the load balancers will put every new VPS on the new node for a while if anyone wants or needs a second IP in SG.
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. | Static Hosting Free for life: https://tierhive.com/static-hosting/