All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Community Input Wanted: Are These Servers Right for You?
rnthosting
Member
Hopefully, this post won't be an issue with the admins, as we haven't applied for the provider tag yet and aren't offering anything at the moment. The purpose of this post is to gather feedback from the community to see if we might be a good fit for LET in the future. 
Long story short, we have a full rack of nodes from a business client who unfortunately shut down, and we're considering offering these to the LET community rather than selling them or disposing of them as e-waste. The plan is to offer these as dedicated servers since they're all in working order and we have plenty of spare parts on site.
We need your help. Below is a standard configuration for a node (which can be customized in the future). What would you consider a fair price for these servers on a monthly basis, and would there be any interest?
Basic Configuration:
2 x Xeon Gold 1st Generation - 6140 18-Core 2.30GHz (3.70GHz Boost) (Different CPUs possible but all within Gold 61XX range)
32 GB DDR4 RAM (Can be increased to 512GB)
2 x 480GB SAS Enterprise SSD (Up to 6 HDDs possible total)
FYI, all servers would be provided with the following (customizable):
1Gb uplink (100TB BW) - 1 IPv6 & 1 IPv4
Direct KVM access
Tier 3 data center - ISO27001 - Location: Europe
No reselling; we own everything from IPv4/IPv6, network equipment, servers, etc.
Same level of support we already provide to all B2B customers.
Thank you for your feedback
Comments
Offering /64 IPv6 is way better
Thanks, would not be a problem, easily added.
But realistically in 8 years we had a client using more than a few IPv6, most of them only stick to IPv4.
It is not ISPs duty to decide how long customers' IPv6 prefix should be. It is best current practice to allocate at least /64. This is also used for RBL purposes. You wouldn't like to allocate /112 or even /128 to each customer and then make all of them suffer due to abuser neighborhood within same /64 shared across multiple customers.
Agreed.
Thanks for the input.