Table of Contents
An earlier version of this URL reported a CPU score of 4,100, a disk read of 50K IOPS, and 950 Mbps, framed as six months of tests across 9 US datacenters. None of those figures were measured here, and they have been removed.
1. The $5 row and the two hourlies
vc2-1c-1gb is the $5 plan. The API object prints monthly_cost 5, hourly_cost 0.007, invoice_type monthly, 1 vCPU, ram 1024, disk 25, disk_type SSD, bandwidth 1024, cpu_vendor Intel and vcpu_type thread. The id token 1gb is the pricing page's "1 GB Memory". That page labels the same row "25 GB Storage" and "1.00 TB Bandwidth". The bandwidth integer 1024 divided by 1024 is 1.00, which matches the label. monthly_cost_preemptible is 5 and hourly_cost_preemptible is 0.007, the same pair as the base fields on this id.
The billing article says other server types, including Cloud Compute, are "Billed up to 672 hours per month." 672 × $0.007 = $4.704. The monthly field on this object is 5. The $4.704 figure is arithmetic on the hourly field and the 672-hour cap. It is not a second sticker Vultr prints.
The Regular Performance table on the pricing page agrees with the API on the $5 hourly: both print $0.007. It does not agree on every larger row. The $10 row is $0.015/hr on the pricing page and 0.014 on the API. 672 × $0.015 = $10.08, and 672 × $0.014 = $9.408. The $15 row is $0.022 against 0.021. The $20 row is $0.03 against 0.027. The $40 row is $0.06 against 0.055. From $80 upward on this ladder the two hourlies match ($0.11, $0.219, $0.438, $0.877). Monthly prices match on every row in the table. Where the hourlies differ, both are shown. Neither one is a correction of the other.
| Plan id | Memory | Storage | Bandwidth | Monthly | Pricing-page hourly | API hourly |
|---|---|---|---|---|---|---|
| vc2-1c-0.5gb-v6 | 0.5 GB | 10 GB | 0.50 TB | $2.50/mo | $0.004 | 0.003 |
| vc2-1c-0.5gb | 0.5 GB | 10 GB | 0.50 TB | $3.50/mo | $0.005 | 0.005 |
| vc2-1c-1gb | 1 GB | 25 GB | 1.00 TB | $5.00/mo | $0.007 | 0.007 |
| vc2-1c-2gb | 2 GB | 55 GB | 2.00 TB | $10.00/mo | $0.015 | 0.014 |
| vc2-2c-2gb | 2 GB | 65 GB | 3.00 TB | $15.00/mo | $0.022 | 0.021 |
| vc2-2c-4gb | 4 GB | 80 GB | 3.00 TB | $20.00/mo | $0.03 | 0.027 |
| vc2-4c-8gb | 8 GB | 160 GB | 4.00 TB | $40.00/mo | $0.06 | 0.055 |
| vc2-6c-16gb | 16 GB | 320 GB | 5.00 TB | $80.00/mo | $0.11 | 0.11 |
| vc2-8c-32gb | 32 GB | 640 GB | 6.00 TB | $160.00/mo | $0.219 | 0.219 |
| vc2-16c-64gb | 64 GB | 1280 GB | 10.00 TB | $320.00/mo | $0.438 | 0.438 |
| vc2-24c-96gb | 96 GB | 1600 GB | 15.00 TB | $640.00/mo | $0.877 | 0.877 |
The $2.50 row is labeled IPv6 Only on the pricing page, at $0.004/hr. The API id vc2-1c-0.5gb-v6 prints hourly_cost 0.003. The $3.50 row matches: $0.005 on the page and 0.005 on vc2-1c-0.5gb. Storage and bandwidth in this table use the pricing page's GB and TB labels. The API prints those disk and bandwidth values as integers.
2. Four 1 GB plan ids
A 1 GB label on Vultr is four ids, not one machine. Regular is vc2-1c-1gb at monthly_cost 5. High Frequency is vhf-1c-1gb at 6. High Performance is two ids, vhp-1c-1gb-amd and vhp-1c-1gb-intel, both at monthly_cost 6. The pricing page prints a single High Performance row at $6.00/mo and $0.009/hr. The $0.009 in the table is that one row, repeated on both ids. Keep the two API ids apart. The Cloud Compute section describes these machines as running on shared vCPUs. vcpu_type on all four ids is thread.
Disk labels stay with the source that printed them. The API disk_type values are SSD, HIGHFREQUENCY, AMDHIGHPERF and INTELHIGHPERF. The Regular Performance line says previous-generation Intel CPUs and regular SSD. The High Frequency line says "Powered by 3GHz+ Intel Xeon CPUs and NVMe SSD." The High Performance line says new AMD EPYC or Intel Xeon CPUs and NVMe SSD. The NVMe words are that page's. The API field is still the disk_type string in the table.
| Plan id | Family | API monthly / hourly | Pricing-page hourly | disk_type | Storage | Bandwidth | cpu_vendor | Locations |
|---|---|---|---|---|---|---|---|---|
| vc2-1c-1gb | Regular | 5 / 0.007 | $0.007 | SSD | 25 GB | 1.00 TB | Intel | 31 |
| vhf-1c-1gb | High Frequency | 6 / 0.008 | $0.009 | HIGHFREQUENCY | 32 GB | 1.00 TB | Intel | 31 |
| vhp-1c-1gb-amd | High Performance | 6 / 0.008 | $0.009 | AMDHIGHPERF | 25 GB | 2.00 TB | AMD | 31 |
| vhp-1c-1gb-intel | High Performance | 6 / 0.008 | $0.009 | INTELHIGHPERF | 25 GB | 2.00 TB | Intel | 32 |
The hourly gap continues up those ladders. On vhf-1c-2gb the API prints monthly_cost 12 and hourly_cost 0.016, and the pricing page prints $12.00/mo and $0.018/hr, with 64 GB storage and 2.00 TB. 672 × $0.016 = $10.752, and 672 × $0.018 = $12.096. The monthly field is 12. Same pattern: the cap times either hourly is a different number from the monthly field.
3. São Paulo's location price
On vc2-1c-1gb the location_cost object has one key, sao: monthly_cost 7.5 and hourly_cost 0.01. The other 30 locations on that id use the base 5 and 0.007. 5 × 1.5 = 7.5, so the São Paulo monthly is 1.5 times the plan monthly on this id. The hourly is not 1.5 times the base hourly: 0.007 × 1.5 = 0.0105, and the object prints 0.01. 672 × $0.01 = $6.72, which is not 7.5.
| Plan id | Base monthly / hourly | São Paulo monthly / hourly |
|---|---|---|
| vc2-1c-1gb | $5.00 / $0.007 | $7.50 / $0.010 |
| vhf-1c-1gb | $6.00 / $0.008 | $9.00 / $0.012 |
| vhp-1c-1gb-amd | $6.00 / $0.008 | $9.00 / $0.012 |
| vhp-1c-1gb-intel | $6.00 / $0.008 | $9.00 / $0.012 |
Among the 38 vc2, vhf and vhp plans in this response, 26 have a location_cost object, and the city id in that object is sao. On those 26, the São Paulo monthly_cost is 1.5 times the plan monthly_cost. vc2-1c-2gb is the next one up: base 10, São Paulo 15. The pricing-page tables do not print a São Paulo column. The $7.50 figure is the API object.
Twelve of those 38 plans have no location_cost object, and sao is not in their locations array: vc2-1c-0.5gb-free, vc2-1c-0.5gb-v6, vc2-1c-0.5gb, vc2-16c-64gb, vc2-24c-96gb, vhf-2c-4gb, vhf-3c-8gb, vhf-4c-16gb, vhf-6c-24gb, vhf-8c-32gb, vhf-12c-48gb and vhf-16c-58gb. They do not get a São Paulo price from this response. The regions list still includes São Paulo.
4. Cities, the small plans, and the $0 id
The regions API lists 33 cities. Nine of them are in the United States: New Jersey, Chicago, Dallas, Los Angeles, Seattle, Atlanta, Miami, Silicon Valley and Honolulu. vc2-1c-1gb lists 31 of the 33 and omits Honolulu and Milan. The other eight US cities are on that id. vhf-1c-1gb and vhp-1c-1gb-amd match that omission. vhp-1c-1gb-intel has 32 locations, includes Honolulu, and still omits Milan.
The $2.50 id, vc2-1c-0.5gb-v6, lists New Jersey and Atlanta. The pricing page marks that row IPv6 Only. The $3.50 id, vc2-1c-0.5gb, lists New Jersey. Deploying either one means reading that short location list, not the 31-city list on the $5 id.
vc2-1c-0.5gb-free prints monthly_cost 0, hourly_cost 0, 512 MB of memory, disk 10, bandwidth 0, disk_type SSD, and three locations: Seattle, Frankfurt and Miami. It is not a row on the Regular Performance table read for this page. Its bandwidth field is 0. The account article's 2 TB, below, is a per-account sentence and is not a field on this id.
5. The row's 1.00 TB and the account's 2 TB
The $5 row's own bandwidth label is 1.00 TB. That is the plan. Separately, the bandwidth-cap article says "Vultr provides 2 TB of free bandwidth per account, allocated monthly." That allocation resets at the start of each calendar month and does not carry over. Adding 2 TB to 1.00 TB and calling the sum the plan's allowance mixes an account pool with a row.
Instance bandwidth accrues by the hour while the instance is running. The same article treats the month as 672 hours for that accrual. The overage article prices usage past the allocated quota at $0.01 per GB, and the monitoring sentence on that page is about outbound data transfer. 100 GB × $0.01 = $1, labelled arithmetic on the printed rate, not a second plan price.
A stopped server and a running server are different sentences. Hourly charges continue if the server is stopped and not destroyed. The bandwidth accrual sentence is about an instance that is running. Read them as two rules.
6. Stop, backups, and refunds
The billing article says hourly charges begin when a server is deployed, powered on or off, and that the minimum unit is one hour. "To stop billing for a server, you must destroy it from your account." Stopping it leaves compute, storage and IP charges running. Invoices are generated on the 1st of each month for the previous period.
Automatic backups are optional. The backups article says an instance with them enabled has a 20% higher base monthly/hourly fee, that Vultr stores the two most recent backups, and that backups do not include attached block storage. The schedule on that page can be daily, every other day, weekly or monthly. Twenty percent of the $5 sticker is $1, so $5 × 1.20 = $6 of arithmetic, and $0.007 × 1.20 = $0.0084 of arithmetic. Those products are not fields on vc2-1c-1gb. The plan's monthly_cost stays 5 until backups are turned on.
The refund article says Vultr does not offer refunds for services. Payments are final, and credits are non-refundable. That article was updated 16 December 2025. A billing dispute goes through a support ticket in the Vultr console, which is the path that article names.
7. What stays off the $5 row
The VX1 section of the pricing page says "VX1 instances are billed on actual hours used each month and are not capped at 672 hours." That sentence is VX1. The 672-hour cap in the billing article names Cloud Compute, Optimized Cloud Compute and Bare Metal. GPU instances on that article are capped at 730 hours. vc2-1c-1gb stays under the 672-hour sentence. The plans response also returned 51 optimized (voc) plans and 11 GPU (vcg) plans. Their prices are not in the tables above.
A port speed for vc2, vhf and vhp is not in the plans payload. The "up to 50 Gbps" line sits in the VX1 section, so read it with a VX1 order. An IOPS number is not on the plans payload or on the Cloud Compute rows read here. The storage page already treats the API disk_type as a label. Windows prices were not in the unfiltered plans list opened today. The plans endpoint has an os=windows filter. Read that filter before you price a Windows image.
The unexpected-charge article says an invoice can include applicable taxes or fees. Vultr's tax article says VAT, sales tax, or consumption tax is not included in the base prices on the platform. The rate depends on the billing address and the service location, and the rate list stays on that article. Read it with the invoice. The Vultr review is a separate page. Use this one for the plan id and the two price fields.