Before you start
Record the plan, protocol, test time, destination and corresponding CPU and disk measurements. Use only destinations you are authorised to test and reasonable volumes. This guide provides neither a CubixServ benchmark nor a load-generation command for a customer server.
Read bits and bytes correctly
1 Gbit/s equals 1,000 Mbit/s in decimal units. Because a byte contains eight bits, the theoretical equivalent is 125 MB/s before protocol overhead. This is a unit conversion, not a measured download result. Tools reporting MiB/s use a different unit. Compare complete units before interpreting a lower-looking number as a performance problem or a configuration error.
Separate port limits, throughput and traffic
A configured maximum limits the rate, rather than the amount of data stored or transferred during a month. No monthly traffic quota does not turn the port into a dedicated or guaranteed connection to every destination. Remote hosts, internet routes, packet loss and protocols affect actual results. Several IPv4 on one VPS share the VPS limit; adding addresses does not multiply bandwidth.
Understand the upgrade price
At the 27 October 2026 review, the included maximum is 1 Gbit/s, with options up to 6 Gbit/s under the service conditions. Each additional Gbit/s costs €49/month. Going from 1 to 2 therefore adds €49/month; going from 1 to 6 adds €245/month. The estimator combines these options with the actual selected VPS term price without reserving or activating capacity.
Find the limiting component
Busy storage, CPU load, encryption, many small files or a slow remote server can constrain a transfer. Compare CPU, disk activity and transfer behaviour together. One download cannot measure every capability of a VM. Do not randomly change MTU, routing or security rules to increase a counter. Establish a verifiable cause before assuming the configured port limit is responsible.
Prepare a repeatable diagnosis
Record source, destination, protocol, file sizes and duration, separating startup from sustained transfer. Compare similar conditions at different times without generating excessive traffic. Keep useful observations for support and remove credentials or secrets. Packet loss, a remote cap and saturated storage need different responses; paying for more bandwidth does not automatically repair them. Retain the details of the test rather than a speed figure alone.
Separate connectivity from DDoS protection
Peeryx’s 15 Tbps+ describes upstream mitigation network capacity, not a VPS port or download rate. L3/L4 filtering concerns covered network attacks; it does not guarantee uninterrupted service under every attack. CPU, memory and storage remain those of the plan. After delivery, review the service conditions and Network & IP workflow before requesting an option suited to the measured requirement.
For your situation
| Situation | Next check |
|---|---|
| Slow download | Compare storage, CPU, protocol and destination before increasing bandwidth. |
| A genuine 2 Gbit/s requirement | Estimate one added Gbit/s at the monthly unit rate, then confirm conditions. |
| Several IPv4 | Keep one bandwidth limit for the whole VPS rather than assuming one per address. |
Official sources
These documents describe the relevant protocols and software. Your service terms and configuration still need to be checked.