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.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Comments
@serverpoint
order #8244983
We don't.
We pay close attention to the CPU resources in our hypervisors and stop adding clients to any hypervisor once we see an average 30-40% usage. Certainly, we never allow it to get to 100%.
All RAM is a dedicated resource though, thus, RAM can't be oversold.
invoice #823151
No particular reason; it just takes a long time to run Yabs with the geekbench test enabled.
We also have hypervisors with Xeon Gold processors running at 3.4Ghz, which are not part of this offer.
But I just ran the geekbench test on the three types of CPUs we use. I'll include these in our next posts.
E5-2699Av4 (VM with 8 vCPUs)
E5-2683v4 (VM with 8 vCPUs)
Xeon Gold 6144 (VM with 4 vCPUs)
Order #6403000
Please double. @serverpoint
Just to double check, if I order LET-RAM1, can I upgrade to the next package LET-RAM2 if I need more ram?
Order #2969547, thanks!
Yes, but it would have to be something that we'd have to manually do on our side, as the upgrade interface in our portal will not show plans related to special deals. Just reach out to our team via our ticket system.
Invoice #823203
double bw please.
thanks
invoice# > @serverpoint said:
@serverpoint the cc charge was made, yet the portal is not acknowledging the purchase. I've already raised a ticket for it.
order #7128769,Double BW please thanks
Evidently you have. That ipv6 part, though, so far as I've noticed, is important to just the one ubiquitous fanatic.
We found the order.
A bug somehow made the order incomplete. We've manually fixed it and approved it. We'll be investigating tomorrow what caused it... sorry about that!
That's what we've been wondering about...
https://lowendtalk.com/discussion/192023/chrome-extension-let-no-sunny/p1
all good sweet! thank you.
Invoice# 823238 for extra bw. TIA again.
Invoice #823237
Thanks!
Invoice #823239
Invoice #823144
Double please thanks
Invoice #823224
Double please!
Invoice #823264
Double bandwidth please
Not true, not having IPv6 connectivity in 2025 is kinda strange. Some countries already have majority of traffic over IPv6 so why not offer it, why stay in the stone age?
@serverpoint
What's the threshold? Let's say I have NTP server (ntppool.org contribution) which uses roughly 90 byte packets and at peak there's 100k packets per second, 9MB/s, does it get blocked? I rather ask because there are some providers offering high bandwidth but when I start using some fraction of it I find they are already throttling way below my official quota.
invoice #823220
thanks!
Invoice #823279
Thank you
Please, don't be so basic.
Economics aside for now, here's one pertinent reason: https://www.tomsguide.com/news/home-gateway-geolocation-bh21
Great offer!
What's your CPU AUP?
Any VDS plans?
One niche issue from 3 years old article about legacy IPv6 addressing that doesn't even apply to server use. It's not hard to distribute routed /64 or /56 or even better /48 prefix and let client use simple and short address without embedding it's MAC address there. What else do you have?
I've got plenty, thanks. An observant reader would have seen "Economics aside for now, here's one pertinent reason" an inferred from there. Regardless, I'll help you digest the point and realize that that alone defeats your ill-conceived blanket question "why stay in the stone age?".
More importantly, here, is what I don't have: Any desire to turn ServerPoint's excellent offer that proactively included all the YABSs and looking glasses, which most people on LET care about, into some IPv4 versus IPv6 debate, which just some people (
) on LET care about.
Hello
No, 90-100mbps of traffic should not trigger any issues over here. But, say, 500mbps or more, specially from multiple servers of the same client, then that would trigger some alarms over here, as it's usually indication of a DDoS attack...