All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
C-Servers VPS Suspended Without Notice – Beware Before Buying
Title: ⚠️ Warning: C-Servers / Centerfield Ltd – Zeta.10 Houston VPS Suspended, Refunds Only After KYC
Content:
I want to share a serious issue with C-Servers (Centerfield Ltd) regarding their Zeta.10 Houston VPS service.
Timeline & Issue:
March 17–25: The server suffered multiple DDoS attacks.
Shortly after, the upstream provider DartNode suspended the VPS, claiming port scanning and malicious activity. No technical logs or evidence were provided.
After repeated requests, DartNode only gave a minimal 21-word response. Customers were left in the dark.
Key Facts:
The VPS is permanently suspended. You cannot continue using it, even if you complete KYC.
Refunds are conditional on KYC. A third-party company handles the process. Without completing KYC, no refund will be issued.
No public KYC portal exists. You must wait for a dedicated email from C-Servers.
Non-compliance risks: If you ignore or fail KYC, all other C-Servers services may be terminated.
Takeaway:
High dependency on third-party providers means service can be terminated without clear evidence.
Refunds are conditional and delayed.
Exercise caution if you consider using C-Servers. Document everything and protect your funds.
Tags: #VPS #HostingWarning #CServers #RefundRisk #KYC

Comments
Tags: #i #love #fumos
Then don't rely on fucking third party providers?
And also don't do port scanning
tldr:
I don't understand why kyc for refund, is that just a blatant attempt to steal money from people that paid them?
How dare he!
I must be still not getting emails. Heh
How does one even submit a ticket to C-Servers.
There is no ticketing system but a chat bot called Williams that cannot escalate to a human.
What does "We have 67 different reports of port scanning from the IPv4" even suppose to mean?
Those reports can be fake. IP address can be spoofed and the port scan might not be even originating from the mentioned server. Even if the port scan is originating from the mentioned server it can be due to an exploit that is the fault of the server provider and not the customer.
Before doing a KYC rampage on the userbase DartNode should check the validity of the reports, check that the IP address is not spoofed. And if necessary determine the root cause of the issue. If this is just a fake report or a spoofed IP address the customer should not even be bothered with this at all.
@alfatarsos
Probably this one
https://www.abuseipdb.com/check/149.112.84.49
Doesn't look good
While this isn't a great look for C-Servers, this is also incredibly concerning for @DartNode. Why won't they let their customer look into and address the problem?
looks like 67 is the limit for abuse reports. ill be sure to stop at 66 next time
Ive seen hosts get ddosed because they were doing sketchy shit in the past, as rpqu said;
Perhaps this is it.
Maybe OP running some script and compromised their host into being a malicious actor without their knowing. What's Chatgippity think?
So the technical log is there after all.
No KYC needed for chargeback.
I purchased a 3-year plan from them just three weeks ago on the same node. I have not received any emails from them, nor have I received any system-generated reply to my email. However, their network status page indicates that everything is currently fine.
https://web.c-servers.co.uk/network-status.html
I received neither the e-mail that was supposedly sent on March 29, nor the one quoted earlier in this thread - just like I did not get the notification regarding an upcoming migration earlier this year.
Has anyone received the KYC request yet? As I did not get one so far at least, it is likely I will not be able to do the KYC. Which means apparently that not only will I not get a refund for Houston VPS, but if I understand correctly, they will also terminate my other VPSes.
I raised a ticket about the whole issue, mentioning that I did not get any e-mails, but it's "in progress", whatever that means...
What a load of ... Was about to get a couple more with them, glad I did not yet...
"All existing services are operating correctly."
The Dallas node no longer exists, so that it is excluded from this statement.
Did you have to buy the $0.79 package of 3 tickets?
If you "opened a ticket" thru the bot as I did, the bot lied to you, it has no ability to open a ticket or do anything at all in fact. It just keeps you company.
Oh boy...
Because nobody is opening tickets anymore?
Even billing issues? lol
This sounds like a wonderful provider.
I put this guy on my "lol, never" list just from seeing his interactions with people here on LET.
I also did, after seeing the kind of comments the owner has been leaving.
lol what is this bullshit, gtfo
chatgpt ahh post
geez first xhosts now this? what is up with the UK providers
As much as we'd like to actually merely proceed with refunds without any verification, as it has always been the rule at C-Servers so far, on this particular instance that is unfortunately not possible. I'll explain why below.
Mentioning to us that there were 67 reports for port scanning, as much as I'd like to ignore it, can't really be ignored and poses a serious systemic risk to customers at the other servers. Abusers or attackers could simply do as they allegedly did at that server elsewhere and the risk simply can't be taken. Imagine being affected in Falkenstein because an abuser purchased servers with any provided refund at the company again. Can't happen.
I seriously doubt about that number, always did, but since that was the reported number to us, it has to go like this. Unfortunately, DartNode did not provide C-Servers with any technical log nor details associated with this issue, nor gave us headroom to see and fix the issue - I had zero IPMI access to the server from the moment it was suspended, and it took multiple attempts and multiple days insisting to merely get a four line answer from DartNode.
I don't take that well. No one does.
At Hetzner, whenever these issues occur, who has the server is provided with a certain timeframe - ranging from 4 to 36 hours, depending on the number of cases on the calendar year - and within that period of time I, or any user, can take a look at any issues, fix them restricting or suspending any abuse, and things go on. That's a reasonable policy. That's why many providers use Hetzner. That was also the general rule of thumb I expected to happen here - reasonability. I was wrong.
By not having access to the server when attacks or abuses like these occur, and most especially not providing any technical evidence on the matter, theoretically anyone can be suspended or terminated at DartNode if they do so choose, for any reason, and no one can assess whether it's true or false. I'm as well also unable to check any logs for who possibly had caused these issues at the server, in order to filter the abusers from the normal users, and proceed accordingly, since server access was cut.
It's an incorrect procedure in my point of view, through and through. Excessive.
That's why it has to go like this, with KYC. I have to protect the present customers. I can assure this was the only service with DartNode, and other dedicated servers of the Zeta or Delta series are not with them.
I'm sincerely sorry for all of this, I can assure this is deeply frustrating for you as it is for me. It's deeply frustrating to have to insist 10+ times over several areas and multiple days to get a short answer. I wanted to get this fixed in ~24h and couldn't over 6 days. Not to mention the loss of customers there.
If DartNode is willing to reconsider on their final posture, and work together with me to fix the issues at hand, I'll be happy to do it and get users a restored service as soon as possible - and everyone gets 2x the number of days the service was down, as a compensation for the lack of service.
I'm absolutely not happy to have users down or suspended for 6 days, nor having to do these things. If I can avoid it, I absolutely will.
That shall be my statement on the matter.
@alfatarsos
Hey. Answering your questions:
Just for added transparency, this verification will cover ~15.3% of the existing userbase.