New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
The nodes can't be reached.
https://status.cloudcone.com/
https://status.cloudcone.com/incidents/384179
We will be migrating SC2 and dedicated workloads from our Los Angeles DC1 to our new facility in Los Angeles (DC3) location Jul 6th, starting at 6:00 PM PST. This migration is necessary due to ongoing transitions affecting our upstream providers at the LA DC1 facility.
What to expect:
SC2 and Dedicated instances currently hosted in LA DC1 will experience a brief service interruption.
Systems will undergo a controlled shutdown and reboot as part of the migration.
No configuration changes are required from customers.
We expect the downtime to be minimal and will closely monitor all services throughout the migration to ensure a smooth transition. Additional updates will be posted here if necessary.
We appreciate your patience and understanding as we complete this work to provide a more stable and reliable hosting environment.
July 2, 2026 · 06:27 PM
OK,we do not get any notice from email about the migration.
I check from link: https://services.cloudcone.com/en/
I'm sure what they're doing is for a good reason, and an update will follow shortly, based on comments made: https://lowendbox.com/blog/multacom-sued-by-aon-center-landlord-over-401128-in-alleged-unpaid-rent/
Dulsara committed to provide transparent updates. So give him and his team a chance
Cloudcone declares “We expect the downtime to be minimal,” but they’re moving servers and re-racking them just like RackNerd. At least a few hours—can that really be considered "minimal"?
Means as short as they can, driving truck fast.
7 hours past,maybe still 5 more hours......
Has CloudCone moved to a data center shared with RackNerd?
Back online finally,good thing is no IP change.
Mine is still dead
Nevermind it's alive.
another 15 hours past.....
Our network is experiencing intermittent timeouts on the SC2 services. Our initial investigation shows that the problem appears to be isolated on the new DC (LAX) at the moment. Our engineers are working on a fix
July 8, 2026 · 12:52 AM
Depends on how you look at it. A few hours downtime to physically move to another dc is absolutely minimal, it's actually very well done.
Legally, if they promise 99% uptime they can be down for 3.5 days per year and still be within SLA. Or 7.5 hours per month if you calculate it monthly.
I have no idea what kind of SLA they promised you but if they break whatever your contract says I'm sure you will be compensated.
@tommyluo Thanks for reaching out. The SC2 product-line disruption was related to the planned colocation migration event in Los Angeles, USA. Our scheduled migration has now been completed.
Following the migration, some intermittent network timeouts were observed while services were coming back online and traffic levels were stabilizing. As the environment continues to normalize, the network performance is expected to improve further.
Additionally, as we planned this infrastructure improvement in stages, the physical move was completed without requiring any IP changes. Your existing IPv4 address, VPS resources, and login credentials remain unchanged.
Our engineering team is actively monitoring the situation and taking the necessary steps. We appreciate everyone's patience and understanding during this transition.
Further updates will continue to be shared through our Status Page.
@rcy026 Thanks for the kind words. It was a large-scale physical infrastructure migration, and our team worked extensively to complete the move as safely/efficiently as possible.
Yeah we got no email either about this, so it hit us a bit unprepared.
It says migration has now been completed, not ours, are you sure all nodes are up?
I think the services are up,but still have network connection issue.
https://status.cloudcone.com/incidents/384910
Deafult MTU change from 1500 to be 1400,it works,they are still investigating and trying to fix it.
Change MTU only works for IPV4 but not for IPV6,have reported to cloudcone to check.
ip link set dev eth0 mtu 1400 [It is for IPV4]
ip link set dev eth1 mtu 1400 [It is for IPV6]
Honestly, CloudCone Los Angeles has been having issues for more than a year, and I really thought they might be about to close down.
Thankfully, they have finally started fixing things, but unfortunately it looks like they have created another issue in the process.
Networking seems fun on these boxes
can't even upgrade or do anything.
At least,by changing the MTU,the IP4 works,in that case,it doesn't matter.
Just wait till they settle it.