All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Paid for LA (invoice confirmed), used for months → forced move to Buffalo after node issue – need ad
Hi,
Apologies for my English — I’m not a native speaker and used Google Translate for parts of this post.
I’ll try to keep this brief and clear. I recently ran into an issue with my VPS and would really appreciate some advice on whether this is normal.
## Background
I purchased a VPS from CCS during Black Friday (Nov 26, 2025):
- Location: Los Angeles (confirmed on invoice)
- Plan: 3 CPU / 4GB RAM / 60GB SSD / 40TB traffic
I have been using it normally for several months without any issues.
What happened
Today my VPS suddenly went offline.
- The server was powered off
- I could not start it from the control panel
So I opened a support ticket.
Support told me the node had memory issues, and they temporarily adjusted resources so the VPS could boot.
Then they asked me to back up my data and agreed to migrate my VPS to another node.
After migration
After the migration, I noticed:
- Location changed from Los Angeles → Buffalo (NY)
- Performance became worse
Here are my NodeQuality tests:
Before (Los Angeles):
https://nodequality.com/r/aUMx0N91GBjxe33ZxZbWl4EBuK99fIeY
After (Buffalo):
https://nodequality.com/r/mHE60bFNKL8AxETA9T7YtswHxIQLeg4s
Differences I observed
- CPU performance is lower
- Network routing is worse (higher latency)
- Overall experience is clearly downgraded
Support explanation
Support told me:
- This plan was always supposed to be in New York
- The Los Angeles location was assigned by mistake
- The migration “corrected” the location
My concern
What confuses me is:
- If the LA location was a mistake, why was it delivered and kept running for months?
- Why was this only “corrected” after a node issue happened?
From my point of view, it feels like I was given a better location first, and then moved to a worse one later.
- The service was delivered as Los Angeles (and shown on invoice)
- I used it for months without any issue
- Then after a node problem, it was changed to another location with worse performance
Question
I wouldn’t mind the migration itself, but the downgrade in location and performance is what concerns me most.
Is this kind of situation normal?
If you were in my position, would you:
- Accept it
- Ask for compensation or refund
- Open a dispute
Thanks in advance for any advice.
Comments
If it was really a mistake, I feel it should have been corrected earlier, not after a node failure.
You purchased LA, they should deliver you LA.
Personally I would just ask for a refund, opening a dispute is last resort.
@ColoCrossing
Ask for a refund and go with a more reliable provider in Los Angeles who can give you the service you are asking.
I love that the support tech who replied to this MJJ’s work order is named Mitchell Jackson.
Thanks, that’s helpful.
Update:
Support has offered to recreate my VPS in Los Angeles.
I will proceed with this and update the thread with the results.
Ernie is an absolute angel, happy to see he got this fixed for you. Noticed their VM platform support is much worse than their dedi support, seems to be a different team.
I wonder how they got that big.
Update:
The VPS has been recreated in Los Angeles.
However, I noticed some important differences compared to my original setup:
So while the location has been restored, the performance and features are still not the same as before.
I have contacted support again and will update once I get a response.
Yeah, Ernie has been helpful so far.
The location is back to LA now, but there are still some differences compared to my original setup (CPU, performance, and port 25), so I’m still following up with them.
Not sure, I just hope the issue can be fully resolved.
Did they advertise the 6152 CPU? If not, you may not get what you want.
Ask for a refund and switch to a more reliable provider.
Update:
Support confirmed they cannot provide the same CPU as before and offered a prorated refund.
However, this issue was caused by a node problem on their side, not by anything on my end. The VPS was stopped without prior notice, and after migration, the service I received is clearly downgraded compared to what I originally had (CPU, performance, and port 25).
Since the service was already delivered and working for months before this incident, I believe this is not a normal variation, but a change of the original service.
I have requested either:
Will update once I hear back.
The support responses were really interesting. Host node running out of memory, having to reduce vps ram to get it to boot, is that shit for real?
They didn’t advertise a specific CPU model, so I understand that part.
But in this case, the VPS was already delivered with that CPU and ran like that for months. After a node issue on their side, it was replaced with a noticeably lower performance setup.
So my concern is not about requesting a specific CPU model, but about the consistency of the service that was already provided.
That’s what I’m considering. If they can’t restore the original performance, a full refund would make the most sense.
Did they advertise a full or partial refund when you bought? Generally they don't refund for promotional plans. If I were you, I would accept partial refund.
Final Update:
Support has issued a full refund and canceled the service.
They were unable to restore the original level of performance in Los Angeles, and the replacement setup did not match what I initially received.
Since the issue was caused on their side and led to a downgrade, I opted for a full refund.
Thanks everyone for the input — really appreciate it.
That’s generally true for promotional plans.
But in this case, the issue was caused by a node problem on their side and resulted in a downgrade of the service, so they ended up issuing a full refund.
Yeah, that surprised me as well.
They reduced the resources just to get the VPS to boot, which I didn’t expect. That was basically when all the issues started.
In the end, they issued a full refund, so it worked out fine.
Plot twist: Jssi added to FraudRecord for being difficult.
Haha, hopefully not 😄
I think I was just trying to get back what I originally had.