All Vultr plans

Last price check: 2026-10-16 简体中文 · 繁體中文 · Deutsch · Português

Vultr was founded in 2014 and offers 20 data centres. This site lists 4 of its plans (2 Main server, 2 Relay); routes: Standard route. Refund: billed hourly. All listed plans are currently in stock.

All plans

Sorted by monthly price, lowest first, including out-of-stock plans. Figures in the table are checked by hand. Test IPs and latency on the three carriers for each data centre are in the test IP table below.

Monthly price Vendor Buy Use Route Test IP Specs Port Traffic List price and billing Refund Claude Available countries and regions
$5.00VultrRelay (China-optimised route)Standard route108.61.201.151
29 more data centres in the table below
1 vCPU / 1G / 25GB SSDnot published1TB
$5/mo, billed hourly ($0.007/hr, capped at 672 hours a month)Same price on renewal
Billed hourly
SupportedUnited States, Canada, Mexico, Brazil, Chile, United Kingdom, Germany, France, Netherlands, Sweden, Spain, Poland, Italy, Japan, South Korea, Singapore, India, Australia, Israel, South Africa
$7.50VultrRelay (China-optimised route)Standard route216.238.98.1181 vCPU / 1G / 25GB SSDnot published1TB
$7.50/mo (São Paulo price, 50% more than other data centres), billed hourly ($0.01/hr, capped at 672 hours a month)Same price on renewal
Billed hourly
SupportedUnited States, Canada, Mexico, Brazil, Chile, United Kingdom, Germany, France, Netherlands, Sweden, Spain, Poland, Italy, Japan, South Korea, Singapore, India, Australia, Israel, South Africa
$40.00VultrMain server (8G)Standard route108.61.201.151
28 more data centres in the table below
4 vCPU / 8G / 160GB SSDnot published4TB
$40/mo, billed hourly ($0.055/hr, capped at 672 hours a month)Same price on renewal
Billed hourly
SupportedUnited States, Canada, Mexico, Brazil, Chile, United Kingdom, Germany, France, Netherlands, Sweden, Spain, Poland, Italy, Japan, South Korea, Singapore, India, Australia, Israel, South Africa
$60.00VultrMain server (8G)Standard route216.238.98.1184 vCPU / 8G / 160GB SSDnot published4TB
$60/mo (São Paulo price, 50% more than other data centres), billed hourly ($0.082/hr, capped at 672 hours a month)Same price on renewal
Billed hourly
SupportedUnited States, Canada, Mexico, Brazil, Chile, United Kingdom, Germany, France, Netherlands, Sweden, Spain, Poland, Italy, Japan, South Korea, Singapore, India, Australia, Israel, South Africa

Test IPs and latency on the three carriers

Each test IP is pinged 4 times by up to 12 public measurement probes on each of mainland China's Telecom, Unicom and Mobile, and the results are averaged. Each hour one vendor takes its turn; this vendor is measured two or three times a day and the day's runs are averaged. This table was measured on 2026-10-16. Loss of 20% or more is marked in orange: such a latency is only the average of the packets that came back, and the connection will lag in real use. “no reply” means that carrier's probes could not reach the IP. Click an IP to open a multi-node ping across China on itdog and test it yourself.

Fastest data centre per carrier: Telecom Cloud Compute Regular 1GB(vc2-1c-1gb)(硅谷) 161 ms; Unicom Cloud Compute Regular 1GB (vc2-1c-1gb) 107 ms; Mobile Cloud Compute Regular 1GB (vc2-1c-1gb) 157 ms.

Test IPPlan (data centre)TelecomUnicomMobileTest date
108.61.201.151Cloud Compute Regular 1GB (vc2-1c-1gb), Cloud Compute Regular 8GB (vc2-4c-8gb)201 ms
loss 2%
107 ms157 ms
loss 8%
2026-10-16
64.176.34.94Cloud Compute Regular 1GB (vc2-1c-1gb) (Osaka), Cloud Compute Regular 8GB (vc2-4c-8gb) (Osaka)211 ms
loss 7%
204 ms194 ms
loss 3%
2026-10-16
141.164.34.61Cloud Compute Regular 1GB (vc2-1c-1gb) (Seoul), Cloud Compute Regular 8GB (vc2-4c-8gb) (Seoul)218 ms
loss 14%
213 ms
loss 3%
158 ms
loss 10%
2026-10-16
45.32.100.168Cloud Compute Regular 1GB (vc2-1c-1gb) (Singapore), Cloud Compute Regular 8GB (vc2-4c-8gb) (Singapore)363 ms
loss 13%
243 ms247 ms
loss 10%
2026-10-16
108.61.210.117Cloud Compute Regular 1GB (vc2-1c-1gb) (Frankfurt), Cloud Compute Regular 8GB (vc2-4c-8gb) (Frankfurt)199 ms192 ms
loss 8%
293 ms2026-10-16
108.61.198.102Cloud Compute Regular 1GB (vc2-1c-1gb) (Amsterdam), Cloud Compute Regular 8GB (vc2-4c-8gb) (Amsterdam)251 ms
loss 3%
213 ms268 ms
loss 5%
2026-10-16
108.61.196.101Cloud Compute Regular 1GB (vc2-1c-1gb) (London), Cloud Compute Regular 8GB (vc2-4c-8gb) (London)258 ms
loss 3%
207 ms229 ms
loss 2%
2026-10-16
64.176.178.136Cloud Compute Regular 1GB (vc2-1c-1gb) (Manchester), Cloud Compute Regular 8GB (vc2-4c-8gb) (Manchester)265 ms
loss 5%
210 ms264 ms
loss 9%
2026-10-16
108.61.209.127Cloud Compute Regular 1GB (vc2-1c-1gb) (Paris), Cloud Compute Regular 8GB (vc2-4c-8gb) (Paris)253 ms208 ms246 ms
loss 2%
2026-10-16
208.76.222.30Cloud Compute Regular 1GB (vc2-1c-1gb) (Madrid), Cloud Compute Regular 8GB (vc2-4c-8gb) (Madrid)281 ms
loss 3%
236 ms281 ms
loss 7%
2026-10-16
70.34.194.86Cloud Compute Regular 1GB (vc2-1c-1gb) (Stockholm), Cloud Compute Regular 8GB (vc2-4c-8gb) (Stockholm)221 ms
loss 8%
213 ms273 ms2026-10-16
70.34.242.24Cloud Compute Regular 1GB (vc2-1c-1gb) (Warsaw), Cloud Compute Regular 8GB (vc2-4c-8gb) (Warsaw)279 ms
loss 6%
213 ms
loss 3%
269 ms
loss 2%
2026-10-16
108.61.219.200Cloud Compute Regular 1GB (vc2-1c-1gb) (Los Angeles), Cloud Compute Regular 8GB (vc2-4c-8gb) (Los Angeles)203 ms262 ms287 ms
loss 7%
2026-10-16
108.61.149.182Cloud Compute Regular 1GB (vc2-1c-1gb) (New Jersey), Cloud Compute Regular 8GB (vc2-4c-8gb) (New Jersey)242 ms
loss 10%
251 ms275 ms
loss 3%
2026-10-16
104.156.230.107Cloud Compute Regular 1GB (vc2-1c-1gb) (Silicon Valley), Cloud Compute Regular 8GB (vc2-4c-8gb) (Silicon Valley)161 ms
loss 3%
166 ms183 ms
loss 3%
2026-10-16
108.61.194.105Cloud Compute Regular 1GB (vc2-1c-1gb) (Seattle), Cloud Compute Regular 8GB (vc2-4c-8gb) (Seattle)215 ms
loss 3%
268 ms189 ms
loss 5%
2026-10-16
107.191.51.12Cloud Compute Regular 1GB (vc2-1c-1gb) (Chicago), Cloud Compute Regular 8GB (vc2-4c-8gb) (Chicago)206 ms240 ms241 ms2026-10-16
108.61.224.175Cloud Compute Regular 1GB (vc2-1c-1gb) (Dallas), Cloud Compute Regular 8GB (vc2-4c-8gb) (Dallas)263 ms
loss 3%
270 ms
loss 8%
246 ms
loss 3%
2026-10-16
108.61.193.166Cloud Compute Regular 1GB (vc2-1c-1gb) (Atlanta), Cloud Compute Regular 8GB (vc2-4c-8gb) (Atlanta)224 ms
loss 3%
232 ms
loss 3%
258 ms
loss 3%
2026-10-16
104.156.244.232Cloud Compute Regular 1GB (vc2-1c-1gb) (Miami), Cloud Compute Regular 8GB (vc2-4c-8gb) (Miami)224 ms
loss 5%
264 ms
loss 10%
251 ms2026-10-16
149.248.50.81Cloud Compute Regular 1GB (vc2-1c-1gb) (Toronto), Cloud Compute Regular 8GB (vc2-4c-8gb) (Toronto)226 ms
loss 3%
250 ms248 ms2026-10-16
216.238.66.16Cloud Compute Regular 1GB (vc2-1c-1gb) (Mexico City), Cloud Compute Regular 8GB (vc2-4c-8gb) (Mexico City)223 ms
loss 3%
246 ms272 ms
loss 2%
2026-10-16
64.176.2.7Cloud Compute Regular 1GB (vc2-1c-1gb) (Santiago (Chile)), Cloud Compute Regular 8GB (vc2-4c-8gb) (Santiago (Chile))359 ms
loss 2%
371 ms377 ms
loss 2%
2026-10-16
108.61.212.117Cloud Compute Regular 1GB (vc2-1c-1gb) (Sydney), Cloud Compute Regular 8GB (vc2-4c-8gb) (Sydney)386 ms256 ms
loss 3%
210 ms
loss 3%
2026-10-16
67.219.110.24Cloud Compute Regular 1GB (vc2-1c-1gb) (Melbourne), Cloud Compute Regular 8GB (vc2-4c-8gb) (Melbourne)307 ms262 ms278 ms
loss 5%
2026-10-16
65.20.66.100Cloud Compute Regular 1GB (vc2-1c-1gb) (Mumbai), Cloud Compute Regular 8GB (vc2-4c-8gb) (Mumbai)258 ms
loss 2%
248 ms214 ms
loss 3%
2026-10-16
139.84.130.100Cloud Compute Regular 1GB (vc2-1c-1gb) (Bangalore), Cloud Compute Regular 8GB (vc2-4c-8gb) (Bangalore)352 ms
loss 3%
224 ms180 ms
loss 3%
2026-10-16
139.84.162.104Cloud Compute Regular 1GB (vc2-1c-1gb) (Delhi)249 ms229 ms196 ms
loss 5%
2026-10-16
64.176.162.16Cloud Compute Regular 1GB (vc2-1c-1gb) (Tel Aviv), Cloud Compute Regular 8GB (vc2-4c-8gb) (Tel Aviv)333 ms
loss 2%
311 ms
loss 3%
364 ms2026-10-16
139.84.226.78Cloud Compute Regular 1GB (vc2-1c-1gb) (Johannesburg), Cloud Compute Regular 8GB (vc2-4c-8gb) (Johannesburg)322 ms
loss 2%
391 ms386 ms2026-10-16
216.238.98.118Cloud Compute Regular 1GB São Paulo (vc2-1c-1gb), Cloud Compute Regular 8GB São Paulo (vc2-4c-8gb)331 ms
loss 9%
353 ms368 ms2026-10-16

Probe cities: Telecom: Guilin, Xi'an, Nanjing, Guangzhou, Changsha, Dongguan; Unicom: Guilin, Wuhu, Changsha, Xi'an; Mobile: Beijing, Taishan, Kunming, Shanghai, Zhengzhou, Nanning. Probes change from day to day; figures are for reference only.

Where the test IPs and latency figures come from

A test IP is a machine the vendor publishes for this data centre and this route. Before buying you can ping it to see how fast your own network reaches it. Clicking an IP opens a multi-node ping across China on itdog, which you can break down by province and carrier.

Where the IPs come from
The vendor's website or Looking Glass page, or the vendor's reply to a support ticket; a few come from third-party reviews. When an IP published by the vendor no longer answers, we replace it with the reachable address with the lowest latency in the same subnet.
Who measures the latency
Probes in mainland China from two public measurement networks. Each hour one vendor takes its turn, so each vendor is measured in two or three time slots a day, by day and at night, and the day's runs are averaged. Each run uses up to 12 probes on each of Telecom, Unicom and Mobile (6 per network; when a network has fewer that day, we use what it has), and each probe pings 4 times.
How to read it
“Telecom 18 · Unicom 22 · Mobile 37 ms” is the latency on each of the three carriers; hover to see the probe cities and loss rate. When a carrier shows 20% loss or more, it is spelt out, e.g. “Telecom 99 (loss 55%)”. That latency figure is only the average of the packets that came back, and in real use the connection will lag; the “My network” filter and sorting do not count it as reachable. We have cross-checked such loss over TCP ports: the handshake time grows several-fold, so it is the path from that carrier to the data centre that drops packets, not the server rate-limiting ping. Sorting by the column uses the fastest of the three carriers.
No reply and unreachable
“no reply” on one carrier means that probe could not reach the IP. “Test IP unreachable” means probes both inside and outside China could not reach it, usually because the IP has been retired; it does not mean the route or the server is unavailable. IPs that block ping are tested on TCP port 80/443 instead.
How accurate is it
For reference only. Each run uses at most 12 probes per carrier, pinging 4 times each; the probes change every run, most sit in data centres rather than on home broadband, and bandwidth and the evening peak are not measured.

What the route names mean

The route is which carrier's network, and which of its networks, carries traffic between mainland China and the data centre. The closer to China and the better the route, the smoother SSH and web pages feel, and the steadier things are at the evening peak.

CN2 GIA
China Telecom's premium network (AS4809), with CN2 both ways. Low latency, stable at the evening peak, the most expensive. The first choice for Telecom users.
CN2 GT
The standard version of Telecom CN2: the international leg uses CN2, the domestic leg uses the ordinary 163 backbone. Cheaper than GIA, a little less stable at the evening peak.
CN2
The vendor only says CN2, without stating GIA or GT; it is safer to expect GT-level performance.
9929
China Unicom's premium network (AS9929, also called Unicom A network or CUII). Works best for Unicom users.
4837
China Unicom's standard backbone (AS4837). Cheap, plentiful bandwidth; may be congested at the evening peak.
CMIN2
China Mobile's premium network (AS58807). Works best for Mobile users.
CMI
China Mobile International's standard outbound route (AS58453): better than a standard route for Mobile users, worse than CMIN2.
All 3 carriers optimised
The vendor states that return traffic for all of Telecom, Unicom and Mobile goes over optimised routes, so it will not be too bad whichever broadband you use.
Standard route
A standard international route, not optimised for mainland China; may slow down noticeably at the evening peak. Suitable as a Main server, reached through a Relay.

This site labels routes as each vendor states them and does not run route tests. Real-world results depend on your broadband carrier; test with the test IP before buying.