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
Hello, I bought a 6-month VPS
Server ID #276
hope I win
Live streaming. The video is encoded on server and the parts are cleaned up after being served.
Makes sense. But a small vps can encode?
Passthrough. No need to re-encode.
What are the benefits?
Hi!
Server ID #289
any comment
Does it also apply to Dedicated Servers?
GLWS<3
gl
Hello,
ID: 296
Thanks.
nice deal
Hello,
ID 298 - 299 - 300- 301
Thanks.
Server ID #320
have a great year Weyro
Doubled
Any BF2025 Flash sale ? @Weyro
Not this year
Server ID #326
Have I missed any flash sales?
GLWS
GLWS
Doubled
Great, my broadband is limited to 10mb. I hope everyone will actively purchase it
Hello, you previously wrote in this thread from another account saying that you were being mistreated. Our rules clearly state that the load on the VM must not exceed 85%.
You were informed about this multiple times, yet your VM was running at 100% load for an entire month, and during that time you transferred over 200 TB of traffic.
Now I have a question: why are you writing from a different account?
And you were already warned when you attempted to request a refund that we are aware you have more than one account with us as well.
First of all, I have two accounts, and I don't use your so-called gift balance either. The 100% CPU issue has been communicated with you through a work order but to no avail. You can disclose your CPU usage statistics method, and the traffic limit should not be 10MB
Our CPU usage statistics come directly from the hypervisor, not from inside the VM. Internal tools like top or htop only show usage inside the guest system, but they do not reflect the load that the VM generates on the host. High network throughput (in your case over 200 TB and sustained ~900 Mbps) produces significant CPU usage on the hypervisor, which is why the VM was consistently at 100% host load. This is why the VM exceeded the allowed 85% limit, regardless of what internal metrics may show

GLWS