KVM · NVMe · DDoS mitigation · IPv4 + IPv6
What every HourlyVPS server runs on, how CPU is shared or reserved, and what happens to your traffic, your addresses and attacks against them. Where we have not published a figure yet, this page says so instead of rounding up.
| Virtualization | KVM, full hardware virtualization |
|---|---|
| Host CPUs | Intel Xeon Platinum |
| Memory | DDR4 ECC registered |
| Storage | Enterprise NVMe SSDDisk size per plan, see pricing |
| DDoS mitigation | Always on, inline, 1.2 Tbps capacity |
| IP addresses | 1 dedicated IPv4 + IPv6 |
| Port speed | 1 Gbps (Quartz) · 25 Gbps (Chrono) |
| Access | Full root, VNC console, REST API |
| Images | Ubuntu, Debian, AlmaLinux, Rocky LinuxCustom ISO on request |
The plan family decides how your virtual CPUs get time on the host. Memory, NVMe storage, DDoS mitigation and the IP addresses work the same way in both.
shared vCPU
Your vCPUs are scheduled on host cores that other servers use too. Most workloads are bursty: web apps, development boxes, small databases, bots. Shared vCPU handles them well and costs less.
Under sustained full load, speed can vary with what else runs on the host. If a Quartz server holds its vCPUs at full load for long periods, our Acceptable Use Policy lets us contact you and limit its CPU allocation.
Q1 · Q2 · Q4 · Q8 · Q16 · 1 Gbps port
dedicated vCPU
Each vCPU is pinned to host CPU capacity reserved for your server, so other customers’ load does not compete for it. Chrono is built for work that keeps the CPU busy: compiling, encoding, CI under load, game servers, simulations.
C8 · C16 · C32 · C64 · 25 Gbps port
Cryptocurrency mining is not allowed on either family. See the Acceptable Use Policy.
Every server sits behind always-on, inline mitigation with 1.2 Tbps of capacity. Inline means incoming traffic is filtered on its way to your server all the time, not diverted to a scrubbing service after an attack has been noticed. It is part of every plan; there is nothing to order or switch on.
If an attack is bigger than that capacity, or threatens other customers, we may filter or null-route the attacked IP address for a while to protect the network. Our Service Level Agreement explains how such measures count.
Every server comes with one dedicated IPv4 address and IPv6, included in the plan price.
Istanbul plans include the monthly traffic allowance listed for each plan, prorated for a server that exists for part of a billing period.
| Plan | Istanbul |
|---|---|
| Quartz Q1 | 2 TB/month |
| Quartz Q2 | 3 TB/month |
| Quartz Q4 | 4 TB/month |
| Quartz Q8 | 5 TB/month |
| Quartz Q16 | 6 TB/month |
| Chrono C8 | 6 TB/month |
| Chrono C16 | 8 TB/month |
| Chrono C32 | 10 TB/month |
| Chrono C64 | 12 TB/month |
If a server in a location with an allowance uses more than its share, we may limit its port speed for the rest of the period. We charge for extra transfer only if an overage rate is published on the pricing page at the time.
Unmetered transfer is not counted against a quota. Fair use means traffic in line with normal use of a server that size. If a server’s sustained traffic affects the network or other customers, we contact you first, and may limit the port speed if it continues.
Both rules are part of our Terms of Service.
Take a snapshot in the control panel before a risky change, and roll back if it goes wrong. A snapshot protects you from a bad upgrade, not from losing your data.
We do not back up the contents of your server. Copy anything you cannot afford to lose to storage outside HourlyVPS.
Deleting a server deletes its disk and cannot be undone. The Security page explains what happens to the storage afterward.
The hardware and policies on this page apply wherever servers can be ordered. A city marked “coming soon” is not open for orders yet.
Some details that network-minded customers look for are not published yet. We add them when they are final rather than guess:
Each one we add gets a dated entry in our changelog. Need one of these now, for example to allow-list our ranges? Email [email protected].
Your side of the work: hardening a new server, retiring it cleanly, and picking the city it runs in.
Security · 17 min read
Nine steps in an order that always keeps a way back in, plus the cloud-init and Docker traps.
Security · 19 min read
Get the data off, revoke keys and cut DNS before you delete, so billing really stops.
VPS explained · 18 min read
Why distance sets a latency floor, a 6-step checklist and an Istanbul vs New York latency table.