Stopped Instances (Still Billing) can create recurring waste in Vultr when ownership, usage, or lifecycle rules drift. Start with evidence, confirm the resource is no longer needed, and only then move to cleanup.

Manual console check

  1. Log in to the Vultr Console.
  2. Navigate to the Compute/Storage section.
  3. Filter for resources with status "Available" or "Unattached".
  4. Check age, attachment state, and owner notes before taking action.
  5. Review each candidate, confirm ownership and dependency risk, then clean it up through your normal change process.

Repeating this for every region is tedious, and the risk is higher when there is no evidence trail.

Local scan check

Cloud Waste Scanner scans locally and groups likely Stopped Instances (Still Billing) waste for review.

Cloud Waste Scanner scan results view
Review likely Stopped Instances (Still Billing) waste with scan evidence.

What this gives you

  • Review usage, ownership, and dependency signals before cleanup.
  • Scan multiple regions without switching console context.
  • Local-First: Your Vultr credentials never leave your computer.

Review before cleanup

Use the scan evidence to decide what is safe to change.

Download App

Common review questions

Should I delete every flagged Stopped Instances (Still Billing) item?

No. Treat every finding as a review candidate. Confirm ownership, usage history, dependency risk, and change approval before cleanup.

Why use a local scan before cleanup?

A local scan keeps credentials on your machine and gives the team evidence it can export, review, and attach to the cleanup decision.