Explains Vultrs billing policy for instances that are stopped but not destroyed, confirming charges continue while resources remain allocated.
Yes. Stopping an instance does not halt billing because the instance continues to reserve critical resources such as CPU, RAM, SSD storage, and IP addresses. These reserved resources remain allocated exclusively to your instance and are therefore billable.
To stop incurring charges, you must destroy the instance from the Vultr Console, or by using the Vultr API or CLI. Destroying an instance releases the associated resources and permanently deletes its data.
Stopped instances are useful when you plan to resume activity soon. If you're unsure, consider creating a snapshot before destroying the instance for backup or migration purposes.
0 Comments
Be the first to comment and share your perspective with the community.