High-performance storage for workloads requiring rapid I/O.
Select the storage type that’s right for you: up to 40 TB of highly affordable HDD,
or up to 10 TB of blazing fast NVMe SSD.
All servers on your account are billed hourly up to the monthly rate cap. The hourly rate is determined by dividing the monthly rate by 672 hours (28 days). If your server is online for more than 672 hours in a calendar month, you will only be billed the monthly rate. Accumulated charges are invoiced to your account on the 1st of every month.
If you upgrade your instance to a larger plan, the instance will appear on separate invoice line items in the month you upgraded. Each line item will bill at the hourly rate associated with the plan for the actual number of hours during that period of time. Because of this, you may be billed more than 672 hours (up to the actual number of hours in that month) during a month that you have upgraded your instance.
View billing model
You can attach a block storage volume through the Vultr control panel or API. Once attached, the instance recognizes it as a new disk, which you can format and mount using standard tools in your OS (Linux or Windows). More information regarding the usage of block storage with our Linux and Windows instances can be found here.
Yes, instances in a stopped state continue to reserve dedicated system resources (RAM, SSD storage, IP aliases, vCPU) and therefore incur charges until you destroy the instance. If you wish to no longer accumulate charges for a virtual machine, please use the DESTROY button in the customer portal.
Yes, you can modify the size for your block storage within the members area. Please note that this will require a reboot of the instance in which your block storage is attached.
No. Block storage can only be attached to instances deployed in the same region.
No, because of potential data loss you cannot perform an in-place downgrade of block storage, but you can use these steps to migrate your files to a smaller block storage subscription.
Yes. Vultr block storage is designed with redundancy across infrastructure to ensure high durability and uptime. Your data is replicated to help prevent data loss in the event of hardware failure.
Block storage behaves like a traditional hard drive, ideal for mounting as a filesystem and used for applications like databases or OS boot disks. Object storage stores data as objects and is better suited for large-scale static data like backups, media files, and archives.
Yes. Vultr allows you to increase the size of your block storage volume. After resizing, you can expand your filesystem within your OS to take advantage of the additional space.
Vultr Block Storage is built on high-speed SSDs and NVMe technology, offering consistent performance for read/write operations. Performance may vary based on instance type, I/O patterns, and volume size.
Data stored on Vultr block storage is encrypted in transit and at rest. You can also implement additional encryption at the application or operating system level for enhanced security.
Vultr Block Storage leverages high-speed SSD and NVMe backends to deliver consistent performance for IOPS-intensive workloads. It supports parallel I/O operations and can scale performance with larger volume sizes, making it well-suited for databases, log processing, and real-time analytics.
Yes. You can configure multiple Vultr Block Storage volumes in software RAID arrays (e.g., RAID 0, 1, 5, 10) within your operating system. This enables enhanced performance, redundancy, or both, depending on your configuration needs.
While local instance storage may offer slightly lower latency due to its physical proximity, Vultr Block Storage delivers competitive low-latency performance through its NVMe-based infrastructure and distributed backend, which is ideal for most performance-sensitive workloads.
Yes. Vultr offers a Terraform provider and a fully documented API, enabling you to automate the provisioning, attachment, resizing, and deletion of block storage volumes as part of your infrastructure-as-code workflows.
All servers on your account are billed hourly up to the monthly rate cap. The hourly rate is determined by dividing the monthly rate by 672 hours (28 days). If your server is online for more than 672 hours in a calendar month, you will only be billed the monthly rate. Accumulated charges are invoiced to your account on the 1st of every month.
If you upgrade your instance to a larger plan, the instance will appear on separate invoice line items in the month you upgraded. Each line item will bill at the hourly rate associated with the plan for the actual number of hours during that period of time. Because of this, you may be billed more than 672 hours (up to the actual number of hours in that month) during a month that you have upgraded your instance.
View billing model