All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Dead Pulsar67 is now back as LayerOne
Hey everyone,
I first signed up to Pulsar67 annually back in May 2025. At first it was a pretty good provider with fast connection for the price of $25 per year. I setup my website, with a bunch of custom scripts I wrote. It was still in the alpha phase of things and I did not commit it to Git yet cause I was still playing with it. I was about to create a git repo when everything went offline.
pulsar67.com suffered severe structural outages starting around June/July 2025, leaving customers completely in the dark with dead servers and a non-responsive panel.
Instead of an orderly, communicative migration, the platform went completely dark for extended periods. The recent activity you are seeing is the result of the domain being wired up to forward to the LayerOne platform.
I recently found out that Pulsar67 is now back as LayerOne ran by the same operator. I feel that this company is not trustworthy as the operator might do a rug pull agian as he did with Pulsar67. As I understand it, Pulsar67 was blacklisted from Lowendtalk and Lowendhost.
I have lost about three months worth of data, however I do have some backups which I might be able to recover fully from, however it will not be the same. I wanted to give users of LayerOne a heads up with my personal experience dealing with Pulsar aka LayerOne. If you do a whois on both domain names, you will see they are both the same person who registered it. Best of luck, cheers.
Comments
Thank you, but you are late
yea i don't think it was a secret they.. rebranded i guess? i didn't realize the previous incarnation went so badly, guess i was correct in avoiding.
I think you missed one more. There's ReviveHost between those two brands.
Edit: Revivehost first one.
I mean...You either playing with your data and then do not say you lost it or you back it up in full and then losing it is not an issue.
Well I had the scripts 2/3 done. I backed up via shell scripts but not to git. Im not a fan of doing commits to git until something is at least working. There were intermediate issues with it going on and offline before the shutdown. Thus breaking my backup scripts. So I do have most but there are some important parts that were completed but not backed up. Regardless, I paid for a year of service, got a few months out of it then nothing. That is not acceptable.
Agreed but only in relation the downtime, did you open a ticket with them? what was the result?
@JohnFilch123 How could I open a ticket if their website was 100% offline for almost a year?
Did you contain them in any other way? Did you contact LayerOne ?
@JohnFilch123 I tried many different ways to try to contact them via the information in whois and the support email. Nothing. I reached out to LayerOne as well, nothing. Hence why I am letting others know what happened to me.
@LayerOne
@LayerOne Thats what I thought. No response.
Sad. I quite liked the @LayerOne VPS i tested.
Hello, we would like to just mention
This has been disclosed in LET which you can view here: https://lowendtalk.com/discussion/220108/layerone-tampa-fl-kvm-vps-from-17-99-year-sas-ssd-ddos-included-50-first-deposit/p1
Hello, I don't see any open tickets or emails from you (we get so much spam, we're trying to work on a system to better sort through our support mailbox so possibly it got missed?)
Maybe stop using orbit?
Oh wait...thats your own services not doing great with emails. Sorry about that.
So yeah... Ditch yourself, get a solid mail provider. Problem solved.
@LayerOne I read https://lowendtalk.com/discussion/220108/layerone-tampa-fl-kvm-vps-from-17-99-year-sas-ssd-ddos-included-50-first-deposit/p1 . What are you talking about, all you said was "One housekeeping note while we are being straightforward. This is our first offer under
the LayerOne name. Some of you will have bought from us as Pulsar67. New hardware, new colocation facility, same staff."
Wow such disclosure. You did not mention the fact that you went abruptly offline with out any notice, or support for your customers. I lost a month of work, lost 8 month of service. You claim you did not get any email from me, yet I have proof that I have send numerous support emails and tickets that went unanswered.
Great way to run a company. You should have backups from Pulsar67. How about letting your previous customers access their data so they can move forward if they have not already done so. You give no apologies for terminating all access and support to your customers while running Pulsar67. What makes us customers think you and your team will not do this again? You also just ignored any customer mentioning Pulsar67's failure in the thread you mentioned. Come on, do you think we are stupid?
@Maddog187 The outage you’re referring to was in 2025. Affected customers were notified by email in November 2025 about refunds, cancellations, and backups. We paused new sales from November 2025 to February 2026, and Pulsar67 continued operating until it was rebranded to LayerOne in August 2026. If that email didn’t reach you, contact [email protected] with your Pulsar67 account details and we’ll look into it. Beyond that, we have nothing further to add here.
@LayerOne The structural outage lasted roughly 3 to 4 months without any notice. No, I did not receive any notice at all. Glad that you stated that you sent out notice in November after being offline for 3 to 4 months. Timeline as follows:
• The severe routing failures and infrastructure drops started around June/July 2025. The network didn't permanently hit its final "completely dead" state until late November/early December 2025, when the remaining customer panels and main website vanished for good.
• During that 3-to-4 month window, customer virtual servers were entirely dead, and the management dashboard was completely non-responsive. Affected users reported losing roughly three months' worth of unrecoverable data because there was zero communication, no orderly migration window, and the operator essentially vanished until reappearing under the new brand.
So, do you think it's acceptable to be offline for 3 to 4 months, then send out a " November 2025 about refunds, cancellations, and backups"? Are you even serious about affected customers? All customers were affected. No one was able to ping, access or connect to anything Pulsar67 related. How can you even say customers affected when Pulsar67.com was 100% offline. Very professional response you gave, "Pulsar67 account details and we’ll look into it. Beyond that, we have nothing further to add here." I am very confident you will look into as much as I am confident paying for new Layerone service again....
I can confirm that Pulsar67 suddenly went deadpool. I had several VPSes with them, and without any prior notification or email, their domain stopped working, the control panel became inaccessible, and all my VPSes went offline for several months. To this day, I still haven't received any emails from them regarding the incident. Eventually, I just gave up, moved on, and never checked back again.
Afaik after speedrun to read these wall of text...
OP told he contacted LayerOne via many channel, but no response.
LayerOne told notified all users by email about refund, backup.
So one side have problem here. At least, as a user perspective, provider MUST ensure the user get the refund by many notification method, rather than yes we told you by email, you didn't got that email then it is your fault.
Now I think it is better to have some log like notification email with timestamp from provider, or some screenshot of trace back June/July 2025 from OP. Both side with conflict conversation will have no end if no one can provide evidence.
@LayerOne To add to the absolute sketchiness of this "rebrand," look at the WHOIS data for their new domain layeronecloud.com:
Registrant Phone: +1.87155175122
That phone number is completely fake. There is no such area code, and the digit count is nonsense.
Because they are using falsified contact data to hide their identity, a formal WHOIS Accuracy Complaint has been filed with ICANN.
If you are thinking of hosting your data with LayerOne, keep in mind that their domain faces suspension once the registrar enforces ICANN's accuracy policies. Do not trust your data to an operator who can't even provide a real phone number.
Use code with caution.
@pdalancer Thank you for confirming. This is exactly what happened. They pulled the plug, went completely dark for months, and now they are gaslighting the community by claiming they handled it professionally with "emails and backups."
@vuanhson You are completely right. Let's look at the actual verifiable evidence regarding who we are dealing with here.
Network Evidence: You can't pull backups or read provider alerts when the host nodes, main website, and customer panels are 100% deadpool for 4 months straight.
The "Rebrand" Lie: LayerOne is trying to act like a new company dealing with a legacy issue. But the public WHOIS data reveals that pulsar67.com and layeronecloud.com are registered to the EXACT SAME OWNER. It is the exact same operator who vanished in 2025.
Fraudulent Contact Info: To make matters worse, LayerOne's current WHOIS records list a completely falsified phone number (+1.87155175122). Because they are using fake details to hide their identity from the community, a formal Inaccurate Contact Information report has already been filed with ICANN.
@LayerOne Thanks for actually updating your contact number correctly. Went from a fake +1.87155175122 to +1.4153197517 which is just CloudFlare's abuse contact: https://community.cloudflare.com/t/newly-registered-domain-at-cloudflare-registrar-suddenly-stopped-working/624440 . Registrar Abuse Contact Phone: +1.4153197517. This still does not comply with ICANN rules. According to Whois Updated Date: 2026-10-26T02:42:04Z. Like common, you are still trying to play games with your customers.
@LayerOne Since you dropped that generic link and told me to "read that page," I decided to take your advice and read your page's source code instead.
As a senior sysadmin, I don't look at marketing copy—I look at the telemetry infrastructure. And you left your actual fingerprints all over the crime scene.
Let's look at the active Google Tag Manager container currently running your new LayerOne site (G-TEF1LDEH9V). Anyone can view the script source and see your hardcoded conversion routing rules:
"const_value","\/client\/products\/virtual-servers\/pulsar-nano\/checkout"
You didn't just rebrand under the exact same owner registry while falsifying your phone number with Cloudflare's abuse hotline. You literally cloned the billing front-end and deployment infrastructure of Pulsar67, and you were so incredibly lazy that you forgot to change your Google tracking container.
You are still actively running the exact same analytical tracking script, logging to the exact same dashboard, explicitly configured for the legacy "Pulsar-Nano" server checkout paths.
The "New Management/Different Company" facade is entirely dead. This isn't a new company cleaning up an old mess. This is the exact same operator using a stolen/cloned front-end to wash a burned brand and avoid honoring refunds from a 4-month data blackout.
The timeline of your panic-updates today tells the whole story to the community:
• You get called out for a 4-month total blackout in 2025.
• You claim "professional emails" were sent.
• Other victims pop up to confirm they never got any notices or data windows.
• I find your WHOIS number is completely fake.
• You panic-update your WHOIS in real-time to spoof Cloudflare's corporate hotline.
• I pull your script metrics and find you're still tracking users via the Pulsar67 GTM container.
This isn't even deep forensic work. This is all completely public information. All I ran in my terminal was a simple:
curl https://layeronecloud.com/account/sign-in
And right there in the raw source code of your active sign-in page is your legacy Google Tag Manager container (G-TEF1LDEH9V), explicitly hardcoded with tracking rules for:
"\/client\/products\/virtual-servers\/pulsar-nano\/checkout"
Taken to the cleaners. Dang.
@LayerOne Good thing I have screenshots and text output before I started this forum. Do you really think that I am that incompetent? This is the third time you have changed your whois output in the last 12 hours. Good work. This just proves further how much anyone can trust LayerOne as a provider.
Domain Name: LAYERONECLOUD.COM
Registry Domain ID: 3126942581_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.cloudflare.com
Registrar URL: https://www.cloudflare.com
Updated Date: 2026-10-26T02:42:04Z
Creation Date: 2026-07-30T17:39:16Z
Registrar Registration Expiration Date: 2027-07-30T17:39:16Z
Registrar: Cloudflare, Inc.
Registrar IANA ID: 1910
Domain Status: clienttransferprohibited https://icann.org/epp#clienttransferprohibited
Registry Registrant ID:
Registrant Name: DATA REDACTED
Registrant Organization:
Registrant Street: DATA REDACTED
Registrant City: DATA REDACTED
Registrant State/Province: FL
Registrant Postal Code: DATA REDACTED
Registrant Country: US
@Maddog187 Username deserved