Buyer constraint
Hosting for high-egress workloads
Where the cheapest compute becomes the most expensive invoice.
The rule, stated before the list
A fixed 2 vCPU, 4 GB VPS sending 10,000 GB outbound in one month before any overage or throttle point.
A plan reaches the table below only if all of this is true of it:
- It is a VPS plan.
- It is a paid plan, not a free tier.
- It bills continuously, so the price is a standing monthly charge rather than a metered one.
- The vendor publishes a monthly price for it.
- It is exactly 2 vCPU and 4 GB, so every row on the page is the same machine.
- Either it includes at least 10 TB of transfer, or the vendor charges nothing per GB and says on its own page that instance traffic is included.
Plans that qualify
| Provider | Plan | vCPU | RAM | Disk | Transfer | Price | Checked |
|---|---|---|---|---|---|---|---|
| HostBrr | DE-3900-4GBrrCurrent: checked automatically2 vCPU · 4 GB · 30 GB10 TB transfer, checked 2026-07-25 | 2 | 4 GB | 30 GB | 10 TB | $5.50 | 2026-07-25 |
| HostBrr | Xeon-4GBrrCurrent: checked automatically2 vCPU · 4 GB · 30 GB10 TB transfer, checked 2026-07-25 | 2 | 4 GB | 30 GB | 10 TB | $5.50 | 2026-07-25 |
| HostBrr | 7950XD-4GBrrCurrent: checked automatically2 vCPU · 4 GB · 60 GB10 TB transfer, checked 2026-07-25 | 2 | 4 GB | 60 GB | 10 TB | $9.99 | 2026-07-25 |
| HostBrr | 9950X-4GBrrCurrent: checked automatically2 vCPU · 4 GB · 60 GB10 TB transfer, checked 2026-07-25 | 2 | 4 GB | 60 GB | 10 TB | $11.00 | 2026-07-25 |
| Hetzner | CX23Not ranked: the source check is too old2 vCPU · 4 GB · 40 GB20 TB transfer, checked 2026-07-25 | 2 | 4 GB | 40 GB | 20 TB | $6.49 | 2026-07-25 |
| HostBrr | EPYC Storage - 4TB - GermanyNot ranked: the source could not be checked, the source check is too old2 vCPU · 4 GB · 4,060 GB20 TB transfer, checked 2026-07-25 | 2 | 4 GB | 4,060 GB | 20 TB | $11.00 | 2026-07-25 |
| HostBrr | Premium StorageBrr 4GBNot ranked: the source could not be checked, the source check is too old2 vCPU · 4 GB · 560 GB10 TB transfer, checked 2026-07-25 | 2 | 4 GB | 560 GB | 10 TB | $12.00 | 2026-07-25 |
| OVHcloud | d2-4 1-month Savings PlanNot ranked: the source check is too old2 vCPU · 4 GB · 50 GBtransfer unknown, checked 2026-07-25 | 2 | 4 GB | 50 GB | unknown | $13.50 | 2026-07-25 |
| HostBrr | Storage-4GBrr - Germany IPv4 NATNot ranked: the source could not be checked, the source check is too old2 vCPU · 4 GB · 4,032 GB20 TB transfer, checked 2026-07-25 | 2 | 4 GB | 4,032 GB | 20 TB | $16.00 | 2026-07-25 |
| OVHcloud | d2-4 hourlyNot ranked: the source check is too old2 vCPU · 4 GB · 50 GBtransfer unknown, checked 2026-07-25 | 2 | 4 GB | 50 GB | unknown | $17.81 | 2026-07-25 |
| Hetzner | CPX22Not ranked: the source check is too old2 vCPU · 4 GB · 80 GB20 TB transfer, checked 2026-07-25 | 2 | 4 GB | 80 GB | 20 TB | $22.99 | 2026-07-25 |
| OVHcloud | c3-4 1-month Savings PlanNot ranked: the source check is too old2 vCPU · 4 GB · 50 GBtransfer unknown, checked 2026-07-25 | 2 | 4 GB | 50 GB | unknown | $29.54 | 2026-07-25 |
| OVHcloud | c3-4 hourlyNot ranked: the source check is too old2 vCPU · 4 GB · 50 GBtransfer unknown, checked 2026-07-25 | 2 | 4 GB | 50 GB | unknown | $39.42 | 2026-07-25 |
Caveats and plans that just miss
These came close enough to be worth knowing about. Some meet the broad rule above but fail a narrower use-case check; the failed column names that distinction. Publishing those exclusions makes it possible to tell a deliberate caveat from a plan nobody evaluated.
| Provider | Plan | Failed | Price |
|---|---|---|---|
| Amazon Web Services | Medium-4GB Linux with public IPv4 | full 10tb included | $24.00 |
| DigitalOcean | s-2vcpu-4gb | full 10tb included | $24.00 |
| HostBrr | DE-Performance-4GBrr IPv6 Only | full 10tb included, remaining egress price known | $3.50 |
| UpCloud | 2 CPU / 4 GB Cloud Native | did not meet the rule | $17.07 |
What actually decides this
High egress needs a workload number, not an adjective. This page fixes compute at 2 vCPU and 4 GB and asks whether the plan can send 10,000 GB before an overage or throttle point. A record qualifies when that volume fits inside a numeric allowance, or when a loaded regional term explicitly includes public traffic. This keeps a cheap CPU price from hiding a large delivery bill.
The cheapest exact-fit rows in the current table have no headroom and no published post-cap price or throttle rule. A slightly higher row with a larger numeric allowance can leave a full workload of margin. OVHcloud can also be attractive in France because public instance traffic is included there, but its record explicitly warns that APAC uses a different rule.
Near-misses are decision data. AWS Lightsail and DigitalOcean both require an overage calculation once this workload exceeds the included allowance; derive that total from the current compute, allowance, and per-gigabyte fields rather than copying an old result into prose. UpCloud records zero-cost egress but an unknown account-dependent Fair Transfer cap, so the workload is not proven suitable.
Use the expected outbound volume, a burst margin, and the exact deployment region. Confirm whether allowances pool across instances or accounts, reset monthly, roll over, or trigger billing, throttling, or suspension. Include CDN origin traffic, backups copied offsite, image pulls, replication, and migration traffic. If the workload can cache at the edge, price origin egress after the cache-hit assumption and state that assumption. If the provider publishes neither an overage price nor an enforcement rule, stop at the allowance instead of rendering zero.
How to check this yourself
Every price here is read from the vendor's own page and carries the date we read it, most recently 2026-07-25. The rule above lists every check applied, so you can disagree with the threshold rather than guess at it. The full method is here, and the dataset is downloadable if you would rather run your own.
Compare every provider on your own workload ·All VPS plans ·Report a wrong price