The default TCP TIME_WAIT timeout for Cloud NAT is scheduled to decrease from 120 seconds to 30 seconds, across all regions, as follows:

• From June 30 to September 29, 2026: new Cloud NAT gateways will use either the 120-second or 30-second default, depending on when the update is deployed in a specific region.
• On or after September 30, 2026: all new Cloud NAT gateways in all regions will use the 30-second default.

Impact on gateways

• New gateways: after the update is deployed in a region, all new Cloud NAT gateways created in that region will use the 30-second default. This change also applies if a pre-update gateway is deleted and then recreated.

• Existing gateways: Cloud NAT gateways created before the regional update will retain the 120-second default. You can adjust this value by using the --tcp-time-wait-timeout flag at any time.

  Cloud NAT gateways configured with a custom TIME_WAIT value aren't affected and will continue to use your configured custom value.

The following table outlines the applicable default timeout for new gateways throughout the deployment timeline.

General Availability: Private NAT supports Cloud Run. For more information, see Supported resources.

Preview: Cloud NAT gateways for Public NAT support source-based NAT rules for IPv4 addresses.

General Availability: Cloud NAT gateways for Public NAT support IPv6 to IPv4 network address translation. For more information, see NAT64 in Public NAT.

Preview: Private NAT supports Cloud Run. For more information, see Supported resources.

Preview: Cloud NAT gateways for Public NAT support IPv6 to IPv4 network address translation. For more information, see NAT64 in Public NAT.

Hybrid NAT is in General Availability.

Hybrid NAT supports Cloud Interconnect in Preview.

Hybrid NAT is available in Preview.

Cloud NAT support for inter-VPC communication is in General Availability.

In some cases, it is possible to create multiple NAT gateway configurations that include the same subnet. For some of these configurations, VMs that are attached to that subnet are not allocated NAT ports, and therefore can't access resources on the internet.

For more information about this issue and a workaround, see VMs can't reach the internet.

Cloud NAT support for inter-VPC communication is in Preview.

Cloud NAT support for Standard Tier egress is in General Availability.

Cloud NAT support for Standard Tier egress is available in Preview.

Dynamic port allocation for Cloud NAT is in General Availability.

Cloud NAT rules are in General Availability.

Dynamic port allocation for Cloud NAT is available in Preview.

Cloud NAT rules are available in Preview. NAT rules let you create access rules that define how Cloud NAT is used to connect to the internet. NAT rules support source NAT based on destination address.

Enabling or disabling endpoint-independent mapping for your gateway is in General Availability.

Organization policy constraints for Cloud NAT are in General Availability.

Enabling or disabling endpoint-independent mapping for your gateway is available in Preview.

Organization policy constraints for Cloud NAT are available in Beta.

Cloud NAT monitoring is in General Availability.

Cloud NAT monitoring is available in Beta.

Draining NAT IP addresses is in General Availability.

Cloud NAT logging is in General Availability.

Cloud NAT logging is available in Beta.

Cloud NAT is in General Availability.

Cloud NAT is available in Beta.

Cloud NAT is available in Alpha.