> ## Documentation Index
> Fetch the complete documentation index at: https://help.nops.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Delete Idle GCP Cloud NAT

> Delete Cloud NAT gateways in a project and region that processed no traffic for 30 days.

Cloud NAT gives private VMs outbound internet access and is billed for its uptime as well as for the data it processes. nOps finds projects and regions where Cloud NAT uptime was billed every day for 30 days but no NAT data was processed at all, and estimates the saving from deleting those gateways.

| | |
| - | - |
| **Cloud** | Google Cloud |
| **Category** | Networking |
| **Service** | Cloud NAT |
| **Action** | Delete |
| **Effort** | Low |
| **Source** | nOps |

## Why it matters

A NAT gateway is often left behind after the workload that needed it is moved or deleted, and keeps billing for uptime with nothing using it.

## How nOps finds it

Google's billing does not identify individual Cloud NAT gateways, so nOps checks each project and region as a whole. It is flagged when Cloud NAT uptime was billed on all of the last 30 days, and in the last 2 days, and there was no Cloud NAT data processing in that project and region in that time. The saving is all Cloud NAT charges there over the last 7 days, scaled to a month, net of discounts and excluding credits, and must be at least \$5 a month. Projects whose spend on the service is at least 90% paid by credits or promotions are left out.

## Before you start

Confirm no VM, GKE cluster or serverless connector in the project and region needs outbound internet access through Cloud NAT.

## How to implement

1. In the console, open **Network services → Cloud NAT** and list the gateways in the project and region.
2. Check which subnets each gateway serves and whether anything there needs outbound internet access, including patching and image pulls.
3. Delete the gateway: `gcloud compute routers nats delete NAT_NAME --router=ROUTER_NAME --region=REGION`.
4. If the Cloud Router exists only for this NAT, you can delete it too.
5. Remove the NAT from Terraform so it is not recreated.

## Risks and considerations

* Private VMs in those subnets lose outbound internet access, which can break updates or calls to external APIs that happen less often than every 30 days.
* If the project and region has several gateways, the saving covers all of them; check each one.
* To roll back, recreate the NAT gateway with the same settings. Any reserved NAT IP addresses you release are gone for good.

## FAQs

> [accordion] Why does nOps check 30 days instead of 14?
>
> Some outbound traffic, such as monthly updates, happens rarely. Waiting 30 days avoids flagging gateways that are used only occasionally.

## Related

* [Release Idle GCP Static IP Address](https://help.nops.io/inform/supported-recommendations/release-idle-gcp-static-ip-address)
* [Delete Idle NAT Gateway](https://help.nops.io/inform/supported-recommendations/delete-idle-nat-gateway)
* [Supported recommendations](https://help.nops.io/inform/supported-recommendations.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.