All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Long time CloudCone customer, should I stay or move on?
I have been with CloudCone for more than six years, and to be honest, we had a very good run together for quite a long time.
There was a period when I was genuinely very happy with the service and felt that CloudCone offered excellent value. Recently, though, things seem to have changed a little. I have had some concerns about stability, and when I contact customer support, I sometimes find it difficult to understand whether my question has been fully answered.
I am not trying to criticise or attack CloudCone. After being a customer for so many years, I would actually prefer to stay rather than move everything elsewhere.
I am just wondering whether anyone can give me some good reasons to remain with CloudCone. I would be very happy to stay if the service and support can return to what they were before.
At the same time, does anyone know of any other providers that offer migration assistance or perhaps a small transfer offer for existing CloudCone customers?
Thank you very much for any advice.
Comments
@dustinc @Tang_Lichun
Run.
With them since 2017. But I smell something not right recently. I'm already shifting my stuff away.
2 girls, one cone.
Its f*d up.
It is quite sad to see CloudCone like this. Maybe @Cloudcone has something to say.
What specs do you need?
@mailme, we understand your frustration, as well as the frustration of everyone affected during this period. We sincerely appreciate your patience, your continued trust in our services, and for sticking with us throughout this time.
At the current time, all servers and customer hardware has been moved, and are online at the new DC, however, the current situation of the datacenter / upstream network is affecting connectivity intermittently (mainly on SC2)
We're going through upstream provider delays, and we should be seeing stability once everything is put into place.
At the moment, we see intermittent connectivity timeouts as stated on https://status.cloudcone.com/incidents/384910
A temporarily fix for this is to set the NIC MTU to 1400 with the following command:
ip link set dev eth0 mtu 1400This command is not persistent and will clear on a re-boot.
If you have a ticket id, please DM me and we can apply this for you until the underlying issue is addressed by the upstream
cloudcone tried to be like digitalocean and other big BS provider but failed miserably. especially in last 2years ive seen more and more drama surrounding them between breaches, connectivity issue, shitass support, and affiliate payment.
if i were using(I wouldnt) cc, i would jump ships asap until they redeem themselves like cuntabo and their diskfreezes.
We also want to add to this, we recognize that service credits cannot make up for the disruption you've experienced. However, all customers affected by this incident will receive SLA credits in accordance with our SLA policy.
I've been through their forced power-off outage back in 2024, then the hack on their system that made data unrecoverable. Now it happened again VPS and CS2 went down, and the so-called "online" status was useless, I couldn't even run an OS update. Reached out to them and got nothing, just "we're still waiting on upstream. Include{https://status.cloudcone.com}" And now I find out a simple MTU tweak could've fixed it the whole time
Thank you, CloudCone. I think this confirms that it is probably time for me to move on, which honestly makes me quite sad.
I have been with CloudCone for over six years and currently have several VPSs. Some of my clients also have their own CloudCone accounts because I recommended your service in the past.
From my own experience over the last year, many incidents have looked very similar to what happened in St. Louis:
https://lowendtalk.com/discussion/219119/cloudcone-st-louis-datacenter-fails-hard-vps-dead-4-days-support-confuses-lax-with-st-louis-ti/p1
In many cases, support told us it was “just a network issue”. However, what we actually experienced was that the VPSs were offline. It was not simply that packets were being dropped or connectivity was unstable. Most of the affected nodes appeared to be completely offline, sometimes for an extended period, with no clear ETA or resolution beyond being told it was a network issue.
I understand that infrastructure problems can happen to any provider, and I appreciate that they are difficult to resolve. My biggest concern has been the communication. As a customer, it is very difficult to understand what is really happening when the service appears to be offline, but we are repeatedly told it is only a network issue.
I genuinely hope CloudCone recovers, because it used to be one of my favourite VPS providers. Unfortunately, after everything that has happened over the past year, I no longer feel confident recommending it to everyone.
my SC2 is down right now, including their website
Segment 64.112.42 has never been restored
I was a long-time customer too — until they took my $11, couldn't deliver a VPS, promised a refund in 7-14 business days, and never paid it. I chased them for over a month. Ticket #1470108 was closed by support without resolution. I even sent them a courtesy email saying I'd post on LET — they opened the ticket, read it, and ignored it.
▎
▎ If this is how they treat $11, imagine what happens when something serious goes wrong. I'd say move. There are plenty of reliable providers out there.
▎
▎ Full story here: #219545
@wenbinxtt We’d like to clarify a few points regarding your statement. Our records show that the account was created on June 28, 2026, so the claim of being a long-time customer is not accurate.
The VPS order issue has since been resolved, and the service is available for provisioning. Additionally, our current refund process no longer follows a fixed timeframe. Refunds are now handled in the order they are submitted, and no further action is required from your side at this time.
Regarding ticket #1470108, our billing team responded approximately 5 days ago, and the request was processed once it reached the front of the queue.
We appreciate your patience while this is being completed.