CloudCone官网：https://www.cloudcone.com
CloudCone Hashtag 2026 Sale洛杉矶套餐：
| 架构 | CPU | 内存 | 硬盘 | 流量 | 价格 | 购买 |
|---|---|---|---|---|---|---|
| KVM | 双核 | 1GB | 50GB | 3TB/1Gbps | $10.24/年 | 点击购买 |
| KVM | 三核 | 2GB | 100GB | 4TB/1Gbps | $15.29/年 | 点击购买 |
| KVM | 六核 | 4GB | 200GB | 5TB/1Gbps | $33.88/年 | 点击购买 |
| KVM | 十核 | 8GB | 400GB | 6TB/1Gbps | $69.96/年 | 点击购买 |
CloudCone洛杉矶机房发生严重宕机事件
2026年1月29日，主打低价VPS的美国服务商 CloudCone 出现大规模故障，其美国洛杉矶地区所有VPS节点几乎同时离线。截至目前，相关服务仍未完全恢复，大量用户无法访问实例，也无法登录CloudCone后台管理面板。
在CloudCone官方状态页中Status Page ，洛杉矶 VPS Nodes 被标记为 Major incident（重大事故）。官方说明显示，当前部分服务出现网络超时，工程团队正在排查问题，但并未给出明确的故障原因或预计恢复时间。
官方状态描述要点：
- 已确认服务中断
- 部分服务出现网络超时
- 网络工程师与系统管理员正在调查
然而，从北京时间1月30日上午至当日凌晨，CloudCone 官方尚未发布完整事故通告，也未明确说明用户数据是否安全可恢复，这引发了用户的广泛担忧。
是否为Hypervisor或底层硬件故障？
从目前现象来看，此次事件并非单台VPS异常，而是整个洛杉矶节点集体不可用，包括：
- 所有实例掉线
- 管理面板无法访问
- 无提前维护通知
- 宕机时间异常偏长
这类特征，更符合以下几种可能性：
- Hypervisor虚拟化层故障
- 存储系统异常（如RAID阵列损坏）
- 数据中心供电或核心网络设备问题
- 底层主控节点异常
部分社区用户也猜测存在安全事件（如主节点被入侵），但目前没有任何公开证据能够证实这一说法，相较之下，硬件或虚拟化层事故的可能性更高。
社区反应：LowEndTalk、Nodeseek、Reddit情绪激烈
事件发生后，LowEndTalk、Nodeseek、Reddit等社区迅速出现大量讨论帖：
- 有用户表示洛杉矶VPS自早上6点起完全失联
- 有站长担心网站数据永久丢失
- 有用户指出近期CloudCone控制面板曾出现404错误
- 也有人回忆起此前洛杉矶 MC 机房的火灾事故
值得注意的是，CloudCone使用的洛杉矶机房，与此前发生火灾事故并波及 RackNerd 的 MC 机房同属一家运营体系，因此也引发了关于是否为同一机房或同一楼层的猜测，但这一点同样尚未得到官方确认。
CloudCone近一年稳定性评价分化明显
自 2024年 CloudCone 被 MC 机房母公司 Edge Centres 收购后，其服务稳定性在用户群体中呈现明显两极分化：
- 一部分用户认为价格依旧有竞争力
- 另一部分用户则频繁反馈节点短暂中断、面板异常
此次洛杉矶VPS长时间不可用，也让不少用户开始重新评估其生产环境使用风险。
当前用户可采取的应对建议
在官方尚未完全恢复服务前，用户能做的事情非常有限，但仍有几个现实建议：
- 如有异地备份，优先在其他服务商快速恢复业务
- 可临时迁移至 RackNerd、HostHatch、Dedirock 等其他机房
- 持续关注以下渠道：
- CloudCone 官方状态页
- Twitter/X：@cloudcone
- LowEndTalk、Nodeseek 社区
- 一旦服务恢复，第一时间完整备份数据
常见问题Q&A
Q1：CloudCone洛杉矶VPS宕机多久了？
A：从2026年1月29日起，洛杉矶节点出现大规模离线，截至目前仍未完全恢复，属于长时间宕机事件。
Q2：这次CloudCone宕机会导致数据丢失吗？
A：目前官方尚未明确说明数据状态，是否涉及存储或RAID损坏仍未知，存在一定不确定性。
Q3：是否可以确认是被黑客攻击？
A：暂无任何官方或技术证据表明是安全入侵事件，更可能是硬件、网络或Hypervisor层故障。
Q4：CloudCone VPS还适合跑生产业务吗？
A：对于低成本、非关键业务仍有吸引力，但生产环境建议务必做好多地备份，避免单点风险。
官方处理事件更新：
We are continuing recovery efforts following a security incident that impacted a limited portion of our Los Angeles VPS infrastructure.
The affected systems were promptly isolated, and our engineering teams are rebuilding impacted nodes from a clean state. Platform-level security reviews and additional safeguards are being applied as part of this process.
At this time:
- The incident has been contained
- Only a subset of VPS infrastructure was affected
- Core systems, billing platforms, and customer databases remain unaffected
Once rebuilding and validation are complete, affected customers will be able to reinstall their VPS and restore services. Detailed guidance and timelines will be communicated directly to impacted users via email.
We appreciate your patience while we complete the recovery and strengthen our platform. Further updates will be posted here as progress continues.
January 31, 2026 · 07:11 PM
What We First Observed
We were initially alerted to the incident when our monitoring systems detected that several virtual machines experienced network connectivity issues. Upon investigation, we observed abnormal system behavior during the boot process on a subset of affected VMs.
Our engineering teams immediately isolated the impacted servers and began a detailed technical investigation. During this process, we identified signs of unauthorized system-level modification on affected virtual machines, and recovery efforts were initiated.
We are actively exploring all viable recovery options, including low-level disk analysis and filesystem validation, while preparing contingency plans to ensure services can be restored as quickly as possible.
How the Incident Occurred
As part of the investigation, our team identified that an unauthorized script had been executed on the affected nodes. Evidence suggests that this activity originated through management-layer access rather than direct SSH connectivity, which explains the absence of anomalous SSH login records.
During our review, we also identified irregularities in logs associated with a single VPS management instance responsible for coordinating the affected nodes. Based on the available evidence, we believe this management layer was used to execute commands across connected systems.
Our investigation remains ongoing, and additional safeguards have been implemented while analysis continues.
Scope of Impact
We utilize multiple independent platforms to operate our VPS services. At this time, we have confirmed that the incident was limited to nodes associated with a single management instance. Other infrastructure, platforms, and service regions were not impacted.
We do not store customer personal data or billing information within VPS management platforms. Our investigation has found no evidence that customer databases, billing systems, or other internal services were accessed or compromised.
We are currently finalizing recovery steps and next actions. All affected customers will be contacted directly via email with further information, and we sincerely apologize for the inconvenience this incident has caused.
January 30, 2026 · 05:49 PM
We have identified an outage on our services, at this stage, some services should be facing network timeouts
Our network engineers and sysadmins are investigating the issue at the moment.
January 30, 2026 · 08:48 AM