All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
YorkHost RYZEN-VPS-24 CPU mismatch: AMD Ryzen VPS moved to Intel Xeon E5-2683 v3, confirmed by YorkH
I want to document my experience with YorkHost RYZEN-VPS-24.
I ordered a RYZEN-VPS-24 VPS, sold as an AMD Ryzen VPS. During troubleshooting, I discovered that the VPS was no longer running on AMD Ryzen hardware, but on an Intel Xeon E5-2683 v3 host.
This was not just a subjective “performance feels slower” complaint. The CPU vendor/model had changed from AMD Ryzen to Intel Xeon, and benchmark results also showed a significant performance drop.
After opening tickets and providing evidence, YorkHost eventually confirmed the issue in writing. Their reply stated that following a provider-side change on June 17, my VPS ended up on an Intel Xeon E5-2683 v3 host, which did not match stated that following a provider-side change on June 17, my VPS ended up on an Intel Xeon E5-2683 v the AMD Ryzen specification under which RYZEN-VPS-24 is sold. They also wrote that they take full responsibility.
YorkHost later migrated the VPS back to an AMD Ryzen node. However, this happened only after I had already investigated the issue myself, migrated my infrastructure to another provider, cancelled the service, and securely wiped the old VPS data because I no longer trusted the service.
The unresolved part is billing/refund handling. YorkHost’s replies focused on the fact that the service had been migrated back to Ryzen, but did not fully resolve the account balance / refund / crypto top-up issue. They also did not fully answer all direct billing and GDPR-related questions.
My concern is that an internal “non-refundable credit/crypto” policy is being used in a situation where the provider itself confirmed that the service was non-conforming and that it takes responsibility.
Summary:
Service: YorkHost RYZEN-VPS-24
Advertised/sold as: AMD Ryzen VPS
Actual host after provider-side change: Intel Xeon E5-2683 v3
Date mentioned by YorkHost: June 17
YorkHost confirmed: the VPS did not match the AMD Ryzen specification
YorkHost stated: they take full responsibility
Later action: VPS migrated back to Ryzen
Current issue: refund/billing/account balance resolution still incomplete
I am posting this as a documented consumer experience. I will update the post if YorkHost provides a proper refund, withdrawal, payout, or compensation resolution.
Update:
YorkHost has now replied publicly on Trustpilot and again confirmed the core issue: following a provider-side change, my RYZEN-VPS-24 was temporarily placed on a host that did not match the AMD Ryzen specification.
They state that the VPS was restored to Ryzen within roughly 34 hours after I reported it. My point is that the provider-side change was previously stated to have happened on June 17, and I discovered the issue myself later during troubleshooting.
YorkHost confirmed:
- cancellation remains in place;
- unpaid invoice #75963 was voided;
- no further charges will be generated;
- provider-side backups/snapshots/images are scheduled for deletion under retention policy.
They also offered 15 free days if I reactivate the VPS, but I already migrated away and do not want to reactivate the service.
The unresolved part remains the account balance / refund / withdrawal issue.
Comments
Can you use AI to summarize your AI? Provider X is shit. Evidence, that's all.
That's very strange, especially if they have some sort of automated process in place if not then being done manually would clearly show it being the wrong service.
Fair point.
AI helped only with wording/structure. The evidence itself is real: CPU outputs, benchmark differences, ticket screenshots, and YorkHost’s own written confirmation.
Full evidence/write-up:
https://gist.github.com/xn-spy/42cf854db0b32f66a67575ac61d3fa9c
Yes, that is exactly why I found it strange too. If it was automated, it means their provisioning/migration process allowed a Ryzen VPS product to end up on an Intel Xeon host. If it was manual, then someone knowingly placed/moved the service to the wrong hardware class.
Either way, YorkHost later confirmed in writing that it did not match the AMD Ryzen specification.