Hello Low End Spirit!

Pulsar67 · February 19

Hi everyone,

I'm from Pulsar67. We’re currently working on building a new website focused on delivering quality cloud hosting services. At this stage, we’re still developing our infrastructure and refining our operations, so please hold off on any purchases—we’re not production ready yet but will have some offers for LES soon!

We currently operate services using colocation out of Tampa, Florida, and looking to expand! Let us know if you have any locations that we should also operate out of!

Non-Profit Partnerships:
We’re passionate about giving back to the community. As part of our mission, we’re looking to work with non-profits that support communities in any way. If you know of any organizations that could benefit from our services or that we should consider partnering with, please let us know. We’re eager to explore opportunities to make a positive impact together.

We truly value the feedback from this community. If you have any suggestions or notice any issues as we progress, please feel free to share. We’re here to learn, grow, and eventually serve you better.

Thanks for having us, and we look forward to engaging with you all!

Best regards,
The Pulsar67 Team

yoursunny · February 20

Checklist of quality cloud hosting service:

Routed IPv6 /64 or larger prefix.
IPv4 can be removed during ordering when it's not needed.
BGP session with automated RPKI updates.
rDNS for both IPv4 and IPv6.
At least one upstream that is neither 174 nor 1299.
Custom ISO.
CPU steal less than 10%.
High CPU usage causes throttling instead of suspension.
$7/year dealz.

Pulsar67 · February 20

@yoursunny said:
Checklist of quality cloud hosting service:

Routed IPv6 /64 or larger prefix.

IPv4 can be removed during ordering when it's not needed.

BGP session with automated RPKI updates.

rDNS for both IPv4 and IPv6.

At least one upstream that is neither 174 nor 1299.

Custom ISO.

CPU steal less than 10%.

High CPU usage causes throttling instead of suspension.

$7/year dealz.

Hello!

We're going to have IPv6—we have a /40 allocation. We're still determining the best allocation size for our customers, and we're trying to keep our setup versatile so that if someone needs a larger allocation, we can offer that.
We're definitely planning on adding the option to disable IPv4, possibly with savings too!
We currently don't support customer-sided rDNS updates. We will offer that functionality by opening a ticket; this is something we look into for the future.
We don't support client-ended ISO at the moment; however, this is something in the works, but I don't think it'll be ready before we start selling. We are able to mount ISOs if needed and will also include that in our FAQ while we work on that functionality.
CPU steal will be a metric we monitor once we start selling!
We don't have any throttling on the CPU. In the case of excessive CPU usage, we may ask you to upgrade or reach out to understand why. We don't have and won't implement any automated processes for throttling or suspending servers over this.
Definitely will look into some deals for LES!

dotdotnetworks · February 20

@yoursunny said:
Checklist of quality cloud hosting service:

Routed IPv6 /64 or larger prefix.

IPv4 can be removed during ordering when it's not needed.

BGP session with automated RPKI updates.

rDNS for both IPv4 and IPv6.

At least one upstream that is neither 174 nor 1299.

Custom ISO.

CPU steal less than 10%.

High CPU usage causes throttling instead of suspension.

$7/year dealz.

Hah, It's so harsh

sh97 · February 20

@yoursunny said: At least one upstream that is neither 174 nor 1299.

why not 1299?

terrorgen · February 20

Just give everyone /64 like all other good providers do. You have enough of them.

host_c · February 20

@Pulsar67

Hy and welcome, hope your project gets a good take-off

@yoursunny said: CPU steal less than 10%.

I recommend you 0, as anything above 0.1% will ultimately get you nowhere, read LES & OGF, that never worked for anyone.

@yoursunny said: $7/year dealz.

I can agree on some level on this, it is really up to you how much $$$ you wish to burn for Marketing, if you go down this path just keep in mind that those are 100% loss

@yoursunny said: Routed IPv6 /64 or larger prefix.

Even @yoursunny can agree that a /64 is enough, right?? , but yes, anything lower than that will cost you a ton of work to fix later ( it was for us )

@Pulsar67 said: We're definitely planning on adding the option to disable IPv4, possibly with savings too!

Don't, at least do not focus on this right from the start, out of 100 IPV6 only services, 70% will ask for IPV4 within 24 hours, this is the truth for now, at least from our point of view.

@Pulsar67 said: We don't support client-ended ISO at the moment; however, this is something in the works, but I don't think it'll be ready before we start selling. We are able to mount ISOs if needed and will also include that in our FAQ while we work on that functionality.

That will work nicely for start

I would recommend you own your Routing and Switching hardware and do not rely on upstream or the Datacenter, but that is me. You can do whatever works for you.

Just my 2 cents on this, please do not:

use the hypervisor ( Proxmox, Xen, vMware and so on ) to do routing, use a Physical Router or a VM with a router OS installed ( vyos or any other )
do not use layer 3 switches as routers, they lack the ASIC's for filtering and high PPS Throughput, they also cannot handle 2 or more full BGP tables ( in case you will be multi-homed ). While some can do BGP that is true, that function was never intended to be used at ISP level, also some struggle with large IPV6 tables as they lack the RAM for it.
Do what you tested and use whatever you are comfortable waking up at 3 AM to fix ( this is something a friend of mine suggested to me, he was 100% right )

Other then this, read the forums and see where others have failed, so you do not try to do the same thing.

Cheers and Godspeed !

HOST-C

AlwaysSkint · February 20

@host_c said: Other then this, read the forums and see where others have failed

FAILED

yoursunny · February 20

@Pulsar67 said:
We don't have any throttling on the CPU. In the case of excessive CPU usage, we may ask you to upgrade or reach out to understand why. We don't have and won't implement any automated processes for throttling or suspending servers over this.

What happens if the customer ignores contacts while keeps consuming CPU?
We'd like it to be throttling instead of suspension.

@host_c said:

@yoursunny said: Routed IPv6 /64 or larger prefix.

Even @yoursunny can agree that a /64 is enough, right?? , but yes, anything lower than that will cost you a ton of work to fix later ( it was for us )

Yes, /64 is enough for most servers during automated provisioning.
Options to request larger or additional prefixes can be offered via tickets.

One such use case is tunneling to a home router or another server that lacks sufficient IPv6 space.
We made such a tunnel from Cloudie YTZ to VirmAche EWR.
Since less-than-/64 equals headache, the tunnel needs its own /64, which in turn requires the source server to have more than /64.

@Pulsar67 said: We're definitely planning on adding the option to disable IPv4, possibly with savings too!

Don't, at least do not focus on this right from the start, out of 100 IPV6 only services, 70% will ask for IPV4 within 24 hours, this is the truth for now, at least from our point of view.

Disabling IPv4 can be offered through pre-sales ticket.
We got this saving on our Salmon HKG server via ticket.

AlwaysSkint · February 20

@yoursunny said: We got this..

The royal We. Crass!

Otus9051 · February 20

@yoursunny why not AS1299? What did Telia ever do wrong. I understand your concerns with Cogent.

I guess Wholesale should be fine as an upstream.

Pulsar67 · February 20

@yoursunny said:
What happens if the customer ignores contacts while keeps consuming CPU?
We'd like it to be throttling instead

We would likely throttle the CPU if we don’t receive a response in a reasonable amount of time. We would only ever suspend a service for repeated abuse or extreme cases (ie: distributing malware, network abuse)

@host_c said:

Yes, /64 is enough for most servers during automated provisioning.
Options to request larger or additional prefixes can be offered via tickets.

One such use case is tunneling to a home router or another server that lacks sufficient IPv6 space.
We made such a tunnel from Cloudie YTZ to VirmAche EWR.
Since less-than-/64 equals headache, the tunnel needs its own /64, which in turn requires the source server to have more than /64.

We will do /64 as that seems to be the general consensus for the best network size to offer. We will allow multiple or larger block sizes to be requested.

@Pulsar67 said: We're definitely planning on adding the option to disable IPv4, possibly with savings too!

Don't, at least do not focus on this right from the start, out of 100 IPV6 only services, 70% will ask for IPV4 within 24 hours, this is the truth for now, at least from our point of view.

Disabling IPv4 can be offered through pre-sales ticket.
We got this saving on our Salmon HKG server via ticket.

Still deciding on the whole v6 implementation.

AuroraZero · February 20

Ignore the want to be trolls. Read, read, and read some more. Listen to what other hosts tell you about the market.

Pulsar67 · February 20

@host_c said: I would recommend you own your Routing and Switching hardware and do not rely on upstream or the Datacenter, but that is me. You can do whatever works for you.

Did a lot of research into what would be best for us and decided on going with Juniper for our routers & switches (both routers do L3 while both our switches only do Layer 2 switching). Been working very well for us in our test environment so far.

@host_c said: Do what you tested and use whatever you are comfortable waking up at 3 AM to fix ( this is something a friend of mine suggested to me, he was 100% right )

That's for sure definitely want to get everything right the first time around so it's smooth sailing and we aren't trying to make extreme changes on production.

Thank you for the suggestions!

yoursunny · February 20

@sh97 said:

@yoursunny said: At least one upstream that is neither 174 nor 1299.

why not 1299?

@Otus9051 said:
@yoursunny why not AS1299? What did Telia ever do wrong. I understand your concerns with Cogent.

1299 congested network.

ZizzyDizzyMC · February 20

@host_c said:
@Pulsar67

Hy and welcome, hope your project gets a good take-off

@yoursunny said: CPU steal less than 10%.

I recommend you 0, as anything above 0.1% will ultimately get you nowhere, read LES & OGF, that never worked for anyone.

@yoursunny said: $7/year dealz.

I can agree on some level on this, it is really up to you how much $$$ you wish to burn for Marketing, if you go down this path just keep in mind that those are 100% loss

@yoursunny said: Routed IPv6 /64 or larger prefix.

Even @yoursunny can agree that a /64 is enough, right?? , but yes, anything lower than that will cost you a ton of work to fix later ( it was for us )

@Pulsar67 said: We're definitely planning on adding the option to disable IPv4, possibly with savings too!

Don't, at least do not focus on this right from the start, out of 100 IPV6 only services, 70% will ask for IPV4 within 24 hours, this is the truth for now, at least from our point of view.

@Pulsar67 said: We don't support client-ended ISO at the moment; however, this is something in the works, but I don't think it'll be ready before we start selling. We are able to mount ISOs if needed and will also include that in our FAQ while we work on that functionality.

That will work nicely for start

I would recommend you own your Routing and Switching hardware and do not rely on upstream or the Datacenter, but that is me. You can do whatever works for you.

Just my 2 cents on this, please do not:

use the hypervisor ( Proxmox, Xen, vMware and so on ) to do routing, use a Physical Router or a VM with a router OS installed ( vyos or any other )

do not use layer 3 switches as routers, they lack the ASIC's for filtering and high PPS Throughput, they also cannot handle 2 or more full BGP tables ( in case you will be multi-homed ). While some can do BGP that is true, that function was never intended to be used at ISP level, also some struggle with large IPV6 tables as they lack the RAM for it.

Do what you tested and use whatever you are comfortable waking up at 3 AM to fix ( this is something a friend of mine suggested to me, he was 100% right )

Other then this, read the forums and see where others have failed, so you do not try to do the same thing.

Cheers and Godspeed !

HOST-C

Bless the 3AM comment, that's true. Francisco told me something similar a couple years ago and it's true. Don't use or do something you're not willing to fix at 3AM.

For small networks (10g and below) building your own router is actually quite easy using off the shelf hardware and multi port cards. Not as good as buying a router, but it's a few hundred with opnsense instead of a few thousand for a cisco or juniper (if you're avoiding microtik / ubiquiti like the plague). Haven't experimented yet with 40g routing using home brew, that's up next on my list.

Find your niche - what can you do that others can't, you'll always excel better in what you can vs what others can't do. Use what you can to your advantage - but don't do so as a detriment to customers.

And the final tidbit of advice: Treat your customers well. Even if everything goes to shit, being respectful and honest to your client goes a long way towards not building resentment. I've had a fair share of mistakes along the way, and am not afraid to admit I've definitely done outright refunds for my mistakes.

yoursunny · February 21

@ZizzyDizzyMC said:
For small networks (10g and below) building your own router is actually quite easy using off the shelf hardware and multi port cards. Not as good as buying a router, but it's a few hundred with opnsense instead of a few thousand for a cisco or juniper (if you're avoiding microtik / ubiquiti like the plague). Haven't experimented yet with 40g routing using home brew, that's up next on my list.

Why limiting to 10g or below?
Mentally strong people build 100~200 Gbps router easy using off the Rhino hardware and multi port cards.
IPv4 + IPv6 + IPv9 all supported.

imok · February 21

Ban @yoursunny

host_c · February 21

@yoursunny said: Mentally strong people build 100~200 Gbps router easy using off the Rhino hardware and multi port cards.

Agree on this,

Jokes aside.

If you need good hardware at decent prices, @NathanCore4 can provide you with such, I can personally vouch for them, no issues for the past 1+ years of collaboration. Whatever we bought, price was and the stuff was A+++

legendary · February 21

That looks like amateur reseller hosting. Who does rdns by ticket these days?

FunFap · February 21

North Korea

Otus9051 · February 21

@imok said:
Ban @yoursunny

Ratio

Hello Low End Spirit!

Comments