--- title: "VPS overselling: what it is and how to spot it | StreetHosting" description: "Overselling means selling more vCPU, RAM, disk and bandwidth than the hardware delivers. Learn the signs, the fio, sysbench and Geekbench tests, and what to do." url: "https://streethosting.com.br/en/guides/vps/what-is-vps-overselling" type: "page" language: "en-US" --- VPS · 10 min · Intermediate Published on Sep 28, 2026 · Updated on Sep 28, 2026 # VPS overselling: signs and tests for when the host sells more than it has Every VPS provider splits hardware between customers, and that is fine as long as you never feel the split. Here is how overselling happens in CPU, memory, disk and network, which signs show up inside your VPS, and how to test without jumping to conclusions. By [Equipe StreetHosting](https://streethosting.com.br/en/autores#equipe-streethosting) · StreetHosting infrastructure and support team [Hardware and datacenter](https://streethosting.com.br/en/guides/topics/hardware) Summarize with: [](https://chat.openai.com/?q=Summarize%20the%20key%20points%20of%20this%20StreetHosting%20guide%3A%20https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Fvps%2Fwhat-is-vps-overselling.%20Highlight%20the%20step-by-step%20instructions%2C%20the%20prerequisites%20and%20the%20most%20common%20mistakes. "ChatGPT") [](https://claude.ai/new?q=Summarize%20the%20key%20points%20of%20this%20StreetHosting%20guide%3A%20https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Fvps%2Fwhat-is-vps-overselling.%20Highlight%20the%20step-by-step%20instructions%2C%20the%20prerequisites%20and%20the%20most%20common%20mistakes. "Claude") [](https://www.google.com/search?udm=50&aep=11&q=Summarize%20the%20key%20points%20of%20this%20StreetHosting%20guide%3A%20https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Fvps%2Fwhat-is-vps-overselling.%20Highlight%20the%20step-by-step%20instructions%2C%20the%20prerequisites%20and%20the%20most%20common%20mistakes. "Google AI Mode") [](https://x.com/i/grok?text=Summarize%20the%20key%20points%20of%20this%20StreetHosting%20guide%3A%20https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Fvps%2Fwhat-is-vps-overselling.%20Highlight%20the%20step-by-step%20instructions%2C%20the%20prerequisites%20and%20the%20most%20common%20mistakes. "Grok") [](https://www.perplexity.ai/search/new?q=Summarize%20the%20key%20points%20of%20this%20StreetHosting%20guide%3A%20https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Fvps%2Fwhat-is-vps-overselling.%20Highlight%20the%20step-by-step%20instructions%2C%20the%20prerequisites%20and%20the%20most%20common%20mistakes. "Perplexity") Share: [](https://x.com/intent/tweet?text=VPS%20overselling%3A%20what%20it%20is%20and%20how%20to%20spot%20it&url=https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Fvps%2Fwhat-is-vps-overselling "Share on X") [](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Fvps%2Fwhat-is-vps-overselling "Share on Facebook") [](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Fvps%2Fwhat-is-vps-overselling "Share on LinkedIn") [](https://wa.me/?text=VPS%20overselling%3A%20what%20it%20is%20and%20how%20to%20spot%20it%20https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Fvps%2Fwhat-is-vps-overselling "Share on WhatsApp") For agents: Copy as Markdown [.md](https://streethosting.com.br/en/guides/vps/what-is-vps-overselling.md) In this guide 7 sections * [What overselling is](https://streethosting.com.br/en/guides/vps/what-is-vps-overselling#o-que-e) * [CPU, memory, disk and network](https://streethosting.com.br/en/guides/vps/what-is-vps-overselling#onde-acontece) * [Signs you can observe on the VPS](https://streethosting.com.br/en/guides/vps/what-is-vps-overselling#sinais) * [Tests to run in the first days](https://streethosting.com.br/en/guides/vps/what-is-vps-overselling#testes) * [How to read the results without overreacting](https://streethosting.com.br/en/guides/vps/what-is-vps-overselling#interpretar) * [What to do if the signs appear](https://streethosting.com.br/en/guides/vps/what-is-vps-overselling#o-que-fazer) * [Where to run when predictability matters](https://streethosting.com.br/en/guides/vps/what-is-vps-overselling#onde-rodar) Quick answer **VPS overselling** is when a provider sells, adding up all its customers, more vCPU, memory, disk or bandwidth than the physical server can deliver at the same time. Some sharing is normal, because most VMs sit idle for a good part of the day. The problem starts when the contention reaches you as high steal, slow disk, memory that disappears or a network that drops at night. Simple tests with fio, sysbench and Geekbench, repeated at different times of day, show whether that is your case. ## What overselling is[](https://streethosting.com.br/en/guides/vps/what-is-vps-overselling#o-que-e) A physical server has a fixed amount of processor threads, memory, disk space and bandwidth. The provider splits those resources into VPS plans. Overselling is selling more than physically exists, adding up all the plans on the same host, on the bet that not everyone will use everything at the same time. The bet has a basis. Most VPS instances spend most of the day with an idle CPU: a small site serving a few requests per minute, a bot waiting for messages, a test environment left on and unused. Making use of that idle time is what makes affordable VPS plans possible, and the whole market works with some level of CPU sharing. Calling any sharing a problem would be like complaining that your internet provider does not have bandwidth for every customer downloading in the same second. What matters is the degree. When the ratio between what was sold and what exists gets too high, the moments when many customers use the hardware at once stop being rare, and the contention shows up inside your VPS. The useful question is not whether the provider shares, but whether you feel the sharing. That can be measured. ## Where overselling happens: CPU, memory, disk and network[](https://streethosting.com.br/en/guides/vps/what-is-vps-overselling#onde-acontece) Each resource can be sold beyond what physically exists in a different way, and each one leaves a different trace inside the VPS. | Resource | How it exceeds the physical limit | What you feel on the VPS | | ----------------- | ------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------ | | CPU | Sum of sold vCPUs far above the host's threads | High steal and performance that varies with the time of day | | Memory | RAM sold above physical RAM, reclaimed with ballooning, deduplication or swap on the host | Total memory that changes, sudden slowness with no swap in the VM, processes killed for lack of memory | | Disk, space | Thin-provisioned virtual disks, which only take up what was written, adding up to more than the real storage | Risk of write errors or a paused VM if the host's storage fills up | | Disk, performance | Many VMs on the same NVMe pool | Low IOPS and disk latency that fluctuates | | Network | 1 Gbps port advertised to many VMs on an uplink smaller than the sum | Good speed in the middle of the night and bad speed at peak hours | CPU is the most shared resource, and its signal is steal time, explained in detail in the guide on [CPU steal on a VPS](https://streethosting.com.br/en/guides/vps/what-is-cpu-steal-vps). Memory is the most delicate: missing CPU only slows things down, missing memory kills processes. That is why aggressive memory overselling tends to be easier with containers, where the limit is just a cgroup number, than with virtual machines. The difference between the two models is covered in [KVM vs LXC](https://streethosting.com.br/en/guides/vps/kvm-vs-lxc). ## Signs you can observe inside the VPS[](https://streethosting.com.br/en/guides/vps/what-is-vps-overselling#sinais) * **Recurring steal time:** the st field in top above a few percent, always at the same times. It is the most direct sign of a contended CPU. * **Slow disk in fio:** a random read test that delivers far less at peak hours than in the middle of the night, or with very high tail latency. * **Unstable IOPS:** the same disk test giving very different results from one day to the next, with no change on your side. * **Memory ballooning:**the virtio balloon driver lets the host take back part of the VM's memory. The driver being present proves nothing on its own, because many providers load it just to read statistics. The sign is the total memory reported by the system changing over time or sitting below what you purchased. * **Slowness with no internal cause:**idle VM CPU, no swap in use, no disk wait, and yet everything is slow. The host may be using swap for the virtual machines' memory. * **Little transparency:** a generic CPU model, an undisclosed virtualization type and a price far below the market do not prove overselling, but they call for more testing before you put anything important in production. To keep track of memory, write down the output of these commands on different days. The MemTotal number should not change while the VM is running: `grep MemTotal /proc/meminfo free -h lsmod | grep virtio_balloon` ## Simple tests to run in the first days[](https://streethosting.com.br/en/guides/vps/what-is-vps-overselling#testes) A single test proves nothing. What reveals contention is the variation. Run each test at three moments, in the middle of the night, in the afternoon and at peak hours, between 8 PM and 11 PM, and compare. On lightly contended hardware the numbers stay similar; on contended hardware, they drop exactly when everyone is using it. ### CPU with sysbench[](https://streethosting.com.br/en/guides/vps/what-is-vps-overselling#sysbench) `sudo apt update && sudo apt install -y sysbench sysbench cpu --threads=1 --time=30 run sysbench cpu --threads=$(nproc) --time=30 run` Write down the events per second value from both runs. Small variations between times of day are normal. As a practical rule of thumb, a drop of more than about 15% that repeats at the same time of day, together with high st in top, points to CPU contention. ### Disk with fio[](https://streethosting.com.br/en/guides/vps/what-is-vps-overselling#fio) `sudo apt install -y fio # random read in 4 KB blocks fio --name=leitura --filename=/root/teste.fio --size=2G --rw=randread --bs=4k --iodepth=32 --ioengine=libaio --direct=1 --runtime=60 --time_based --group_reporting # random write in 4 KB blocks fio --name=escrita --filename=/root/teste.fio --size=2G --rw=randwrite --bs=4k --iodepth=32 --ioengine=libaio --direct=1 --runtime=60 --time_based --group_reporting rm /root/teste.fio` In the output, look at the IOPS value on the read or write line and at the clat percentiles block, especially the 99th percentile, which shows how long the slowest operations take. There is no universal number, because each provider may cap IOPS per plan, and that is a declared policy, not overselling. What gives contention away is the same test delivering half as much at peak hours, or the 99th percentile jumping to tens of milliseconds. The guide on the [difference between HDD, SSD and NVMe](https://streethosting.com.br/en/guides/infrastructure/hdd-vs-ssd-vs-nvme) helps you understand what each type of disk delivers. Fio really writes data. Always run it against a test file, as in the example, never pointing at the disk device. Avoid your own application's peak hours, because the test competes with it for disk, and delete the file when you are done. ### Geekbench to compare against a reference[](https://streethosting.com.br/en/guides/vps/what-is-vps-overselling#geekbench) Geekbench runs a battery of CPU tests and produces a single-core and a multi-core score. The Linux version is downloaded from the official site, extracted and run directly in the terminal. The advantage is comparing against public results for the same processor model: if your VPS's single-core score sits well below what is expected for that chip, and does so consistently, the vCPU is getting less than it should. In the free version the result is published on the Geekbench site, so do not run it on a machine whose hardware you would rather not expose. ### Network[](https://streethosting.com.br/en/guides/vps/what-is-vps-overselling#rede) For the network, an iperf3 test against a known server, at different times of day, shows whether the port delivers what the plan promises. The step by step is in [how to test your VPS network speed](https://streethosting.com.br/en/guides/vps/test-vps-network-speed). ## How to read the results without reaching the wrong conclusion[](https://streethosting.com.br/en/guides/vps/what-is-vps-overselling#interpretar) * **Rule out your own load.** Run the tests with your application stopped or at a time when it is barely used. Otherwise you are measuring your application competing for resources with the test itself. * **A declared limit is not overselling.** A plan that advertises an IOPS, traffic or CPU limit is being transparent. The problem is when a promised resource vanishes without notice. * **One episode is not a pattern.** Maintenance on the host or a neighbor with a one-off spike produces bad numbers for a few hours. A pattern is what repeats for days. * **Compare against what was sold.** A 2 vCPU VPS does not perform like the whole processor. The fair comparison is between times of day and against what is expected for the stated CPU model. None of this is a reason to distrust every provider or to accuse anyone based on one test. The numbers are for talking to support with facts and for deciding calmly. The general buying criteria, beyond performance, are in [how to choose a VPS in Brazil](https://streethosting.com.br/en/guides/vps/how-to-choose-a-vps-in-brazil). ## What to do if the signs appear[](https://streethosting.com.br/en/guides/vps/what-is-vps-overselling#o-que-fazer) 1. **Keep the results with date and time,** including the time zone and what the application felt at the same moment. 2. **Open a ticket with numbers:** sysbench, fio, steal history from sar and the times of the episodes. A vague report like the VPS is slow is hard to investigate; a table with timestamps is not. 3. **Ask what can be done,** such as redistributing the load on the host or adjusting the plan, and set a deadline to measure again. 4. **If the pattern continues, move.** Another line, another plan or exclusive hardware. When the bill gets close to the price of a dedicated server, the comparison in [dedicated server vs VPS](https://streethosting.com.br/en/guides/infrastructure/dedicated-server-vs-vps) helps you decide. Run the tests in the first week of any new VPS and keep the numbers as a baseline. Months later, if something feels slow, you have something to compare against instead of relying on impressions. ## Where to run when predictability matters[](https://streethosting.com.br/en/guides/vps/what-is-vps-overselling#onde-rodar) The advice applies to any provider, StreetHosting included: run the tests in this guide in the first days and keep the results. If something falls outside what you expect, open a ticket with the numbers, and support can cross-check them against the host's load. The [Ryzen 9 9950X VPS](https://streethosting.com.br/en/vps/ryzen) uses KVM virtualization, names the processor model and comes with the vCPU, DDR5 memory and NVMe defined in each plan, from R$ 40.00 with 1 vCPU and 2 GB to R$ 846.00 with 14 vCPU and 64 GB. A game server or an API in production usually starts at 4 vCPU and 8 GB for R$ 118.00. All the lines are gathered on the [VPS](https://streethosting.com.br/en/vps) page, with a datacenter in São Paulo, Anti-DDoS and root access. When no sharing is acceptable, a [dedicated server](https://streethosting.com.br/en/dedicated) takes the neighbors out of the equation. The AMD Budget SM, with a Ryzen 9 5900XT and 64 GB DDR4, costs R$ 1,499.00 per month, and the Extreme SM, with a Ryzen 9 9950X and 128 GB DDR5, costs R$ 2,229.00. Both have 2 TB of NVMe, a dedicated 10 Gbps port and delivery within 6 days. In this guide * [What overselling is](https://streethosting.com.br/en/guides/vps/what-is-vps-overselling#o-que-e) * [CPU, memory, disk and network](https://streethosting.com.br/en/guides/vps/what-is-vps-overselling#onde-acontece) * [Signs you can observe on the VPS](https://streethosting.com.br/en/guides/vps/what-is-vps-overselling#sinais) * [Tests to run in the first days](https://streethosting.com.br/en/guides/vps/what-is-vps-overselling#testes) * [How to read the results without overreacting](https://streethosting.com.br/en/guides/vps/what-is-vps-overselling#interpretar) * [What to do if the signs appear](https://streethosting.com.br/en/guides/vps/what-is-vps-overselling#o-que-fazer) * [Where to run when predictability matters](https://streethosting.com.br/en/guides/vps/what-is-vps-overselling#onde-rodar) ## Frequently asked questions What is VPS overselling? It is when a provider sells, adding up all the customers on one physical server, more vCPU, memory, disk or bandwidth than the hardware can deliver at the same time. It works as long as only a few customers use everything at once. When many do, the contention shows up as slowness, high steal and performance that changes with the time of day. Does every VPS provider oversell? Every VPS provider shares hardware, and some CPU sharing is common practice, because most virtual machines sit idle for a good part of the day. What separates a good service from a bad one is the degree. If you do not feel the contention in your tests or in your application, the sharing is sized well. How can I tell if my VPS is oversold? Measure at different times of day. High, recurring steal in top, a sysbench score that drops at peak hours, fio with unstable IOPS and latency, and total memory that changes are the most objective signs. A single result proves nothing; a pattern that repeats for days is what points to contention. Is a very cheap VPS a sign of overselling? Not necessarily, but a price far below the market for the same hardware calls for more testing. Be wary when the low price comes with an unnamed CPU model, an undisclosed virtualization type and memory that is too generous for the money. In those cases, test before putting anything important in production. Does a dedicated server solve overselling? It does, because no other customer shares the hardware: the processor, memory, disk and network port are entirely yours. In exchange, the cost is much higher than a VPS, so a dedicated server makes sense when the load is already large or when predictability is worth more than savings. Next step See Ryzen VPS Ryzen 9 9950X VPS in São Paulo with root access, NVMe and gamer Anti-DDoS. [See Ryzen VPS](https://streethosting.com.br/en/vps/ryzen) [See dedicated servers Exclusive hardware in São Paulo with NVMe and Anti-DDoS.](https://streethosting.com.br/en/dedicated) [See VPS plans Root VPS in Brazil with NVMe and Anti-DDoS.](https://streethosting.com.br/en/vps) ## Related guides [VPS Intermediate CPU steal on a VPS: what it is, how to measure it, what to do Steal time is the most direct sign that your virtual machine is competing for CPU with others on the same host. Learn to measure it, tell noise from a real problem and build a ticket that support can actually investigate. 9 min Read guide](https://streethosting.com.br/en/guides/vps/what-is-cpu-steal-vps) [VPS Intermediate KVM vs LXC: difference between a full VM and a container KVM gives you an entire virtual computer with its own kernel. LXC gives you an isolated space inside the host's operating system. See what that changes for Docker, VPN, swap and security, and how to find out which of the two your VPS runs on. 10 min Read guide](https://streethosting.com.br/en/guides/vps/kvm-vs-lxc) [VPS Beginner How to choose a VPS in Brazil: complete guide A VPS that is too cheap usually hides overselling and slow disks. This guide turns what matters into a practical checklist for anyone hosting games, APIs or automation. 3 min Read guide](https://streethosting.com.br/en/guides/vps/how-to-choose-a-vps-in-brazil) [← Back to the Guide Center](https://streethosting.com.br/en/guides)