Orphaned Disk Snapshot (GCP)
CostLens finds Compute Engine snapshots whose source persistent disk no longer exists — a backup of something already deleted.
CostLens finds orphaned disk snapshots — Compute Engine snapshots whose source persistent disk no longer exists. These silently accrue storage charges long after the disk they backed up was deleted. This is a CostLens custom check that covers a gap in Google's Recommender.
Deletion is irreversible
Deleting a snapshot permanently destroys it. CostLens shows this as an irreversible fix and cannot roll it back. Keep it if it's a deliberate long-term backup.
How it works
Snapshots are enumerated
CostLens lists snapshots via the Compute API and resolves each snapshot's sourceDisk.
Orphans are flagged
Snapshots whose source disk no longer exists are surfaced, priced at their stored size.
What to do
- Confirm the snapshot isn't part of a retention policy or DR plan you still rely on.
- Delete it to stop the charge — via CostLens Apply Fix (irreversible) once write access is granted, or in the Cloud Console.
Severity levels
| Severity | Estimated monthly savings |
|---|---|
| critical | >$500 |
| high | $100–$500 |
| medium | $20–$100 |
| low | <$20 |
Required permissions
- Detect: Compute read (snapshot + disk list) — see GCP Accounts.
- Apply Fix (delete): a write role with
compute.snapshots.delete.
Limitations
- Only snapshots whose source disk is confirmed missing are flagged; snapshots of existing disks are left alone.