How fast cloud servers deploy

New servers ordered 2026-10-26 to 2026-11-15, updated monthly

Hetzner is the fastest: a new server is running in about 20 s and takes an SSH login in about 35 s. Linode is the slowest at about 75 s to running and about 100 s to login. Numbers come from about 880 real deploys between 2026-10-26 and 2026-11-15.

For CI runners, test boxes and short GPU jobs, the minute between clicking deploy and logging in is part of the cost. These are real deploys of real customer orders, not a synthetic benchmark.

Time to a working server, by cloud

CloudRunning (median)Login ready (median)Slowest 1 in 10, login
Hetznerabout 20 sabout 35 sabout 40 s
DigitalOceanabout 35 sabout 70 sabout 85 s
Vultrabout 45 sabout 70 sabout 4 min
Linodeabout 75 sabout 100 sabout 2.5 min

Running: the cloud reports the server active with an IPv4 address. Login ready: the SSH port (RDP on Windows) accepts a connection.

By city

Median seconds to running, cities with 5 or more deploys. Rounded to 5 seconds.

Hetzner

CityRunning (median)
Frankfurtabout 20 s
Helsinkiabout 20 s
Nurembergabout 20 s

DigitalOcean

CityRunning (median)
New Jerseyabout 30 s
Londonabout 35 s
Singaporeabout 35 s
Bangaloreabout 40 s
Amsterdamabout 40 s
Frankfurtabout 45 s

Vultr

CityRunning (median)
São Pauloabout 35 s
Tel Avivabout 45 s
Parisabout 45 s
Dallasabout 45 s
Frankfurtabout 45 s
Amsterdamabout 45 s
Chicagoabout 50 s
Tokyoabout 55 s
New Jerseyabout 55 s
Seoulabout 55 s
Mexico Cityabout 80 s

Linode

CityRunning (median)
Chicagoabout 55 s
Stockholmabout 65 s
Frankfurtabout 75 s
Dallasabout 75 s
Tokyoabout 75 s
Amsterdamabout 75 s
New Jerseyabout 75 s
São Pauloabout 80 s
Londonabout 85 s
Singaporeabout 85 s

Exact numbers: deploy-time.csv (CC BY 4.0, cite NoctHost). Also on GitHub and Zenodo, DOI 10.5281/zenodo.24249955.

How we measured

Every new server ordered through NoctHost between 2026-10-26 and 2026-11-15, about 880 in total. The clock starts when we send the create request to the cloud. It stops when the cloud reports the server active with an address, checked every 10 seconds, so a single result is accurate to about 10 seconds. A second clock stops when the login port first accepts a connection; it was recorded for a part of the servers. Restores from snapshots are left out because they copy a whole disk.

Frequently asked questions

Which cloud deploys a VPS the fastest?

Hetzner: the median new server is running in about 20 s. DigitalOcean follows at about 35 s, Vultr at about 45 s and Linode at about 75 s.

What is the difference between running and login ready?

Running means the cloud reports the instance as active with an IPv4 address. Login ready means the SSH port (RDP on Windows) actually accepts connections, after the operating system has booted. The gap is the boot time, usually 15 to 35 seconds.

How often is a deploy much slower than the median?

On Vultr, 1 deploy in 10 takes about 4 min or more before SSH answers. On the other clouds the slowest 10% stay within about two and a half minutes.

Does the city matter?

Less than the cloud. Hetzner is about 20 seconds in all three of its European cities. On Vultr most cities are 35 to 55 seconds, with Mexico City slower at about 80.

How was this measured?

From our own order log: every new server ordered through NoctHost between 2026-10-26 and 2026-11-15, excluding restores from snapshots. The clock starts when we send the create request and stops when the cloud reports the server active (polled every 10 seconds), and separately when the login port first answers.

Pick the cloud and the city in one form

All four clouds from one account, billed by the hour. See what you can deploy right now and pricing.

Get started