[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-08-20。"],[],[],null,["# IP address utilization insights\n\nThis page describes the Network Analyzer insights for IP address\nutilization. For information about all the insight types, see\n[Insight groups and types](/network-intelligence-center/docs/network-analyzer/insight-groups-types).\n\nIP address utilization insights show the IP address allocation percentage of\nsubnet ranges, which are calculated based on configurations that use IP\naddresses, such as VMs and load balancers. In the case of Shared VPC,\nNetwork Analyzer provides the IP address utilization insights of the host\nproject, and the information from service projects is automatically aggregated\nto derive the insight information.\n\nView insights in the Recommender API\n------------------------------------\n\nTo view these insights in the gcloud CLI or the Recommender API, use\nthe following insight type:\n\n- `google.networkanalyzer.vpcnetwork.ipAddressInsight`\n\nYou need the following permissions:\n\n- `recommender.networkAnalyzerIpAddressInsights.list`\n- `recommender.networkAnalyzerIpAddressInsights.get`\n\nFor more information about using the Recommender API for\nNetwork Analyzer insights, see\n[Use the Recommender CLI and API](/network-intelligence-center/docs/network-analyzer/use-cli-recommender-api).\n\nHigh IP address utilization of a subnet\n---------------------------------------\n\nThis insight indicates that the IP address utilization of a subnet is too high\n(the allocation ratio is higher than 75 percent). Such an issue can prevent\nautomation from creating new VMs or upgrading a GKE cluster. This\ninsight includes the following information:\n\n- **Subnetwork:** The name of the subnetwork.\n- **Secondary range name:** If the insight shows the primary range of the subnet, this field is not displayed.\n- **IP address range:** The IP address range of the subnetwork range.\n- **Allocation ratio:** The percentage of IP addresses from the range of the subnet that are allocated.\n- **Resources using this range:** The count of the number of resources of this type that have allocated IP addresses within the IP address range of the subnet. This attribute gives a summary of the number of IP addresses used by resources such as VMs and load balancers.\n\nThe allocation ratio of the primary range includes the\n[four unusable IP addresses](/vpc/docs/subnets#unusable-ip-addresses-in-every-subnet).\n\n### Recommendations\n\nYou have two options:\n\n- [Expand the subnet primary ranges](/vpc/docs/create-modify-vpc-networks#expand-subnet).\n- [Add more secondary ranges](/vpc/docs/create-modify-vpc-networks#edit-secondary).\n\nIP address utilization summary\n------------------------------\n\nThis insight gives a summary of the IP address utilization of subnet ranges in the\nanalyzed project. In the case of Shared VPC, Network Analyzer gives a\nsummary of the IP address utilization of all relevant subnet ranges of the host\nproject, and also provides the insights of the service projects. It includes the\nfollowing information:\n\n- All subnet ranges that have an allocation ratio more than zero.\n- **Secondary range name:** The secondary range name of a subnet. This field is not displayed for the primary range of a subnet.\n- **Subnet range prefix:** The IP address range of the subnetwork range in CIDR format.\n- **Allocation ratio:** The ratio (between 0 and 1, 1 being 100%) of IP addresses allocated from the range of the subnet compared to the total number of IP addresses in the subnet.\n\nThe allocation ratio of the primary range includes the\n[four unusable IP addresses](/vpc/docs/subnets#unusable-ip-addresses-in-every-subnet).\n\n### Related topics\n\nFor more information, see\n[High IP address utilization insight](/network-intelligence-center/docs/network-analyzer/insights/vpc-network/ip-utilization#ip-allocation-ratio-high).\n\nPrivate services access IP address utilization summary\n------------------------------------------------------\n\nThis insight gives a summary of the utilization of IP address ranges used for\n[private services access](/vpc/docs/private-services-access) in the analyzed\nprojects. Private services access IP address ranges are used by Google Cloud\nmanaged services such as Cloud SQL.\n\nWhen you use private services access, you create an [allocated\nrange](/vpc/docs/configure-private-services-access#allocating-range) that is\nused when you create a [private\nconnection](/vpc/docs/configure-private-services-access#creating-connection) to\nthe service. In Network Analyzer, allocated IP address ranges are referred\nto as *PSA ranges*.\n\nThe managed service producer creates a subnet in a service-managed\nVirtual Private Cloud (VPC) that is peered to your VPC network.\nThe service producer chooses an available IP address range for the subnet that\nfalls within the allocated IP address range. In Network Analyzer, the\nservice producer subnets are referred to as *PSA subnets*.\n\nThis insight includes the following information:\n\n- **PSA range prefix**: The prefix of the allocated IP address range (PSA range) reserved in your VPC network for managed services.\n- **PSA subnet prefix**: The prefix of the subnet that was created from the PSA range.\n- **PSA subnet region**: The region used by the managed service for this subnet.\n- **PSA subnet service** : The name of the managed service that uses this subnet. For more information about the services that support this field, see [Managed services supporting the name\n field](#managed-services-supporting-the-name-field).\n- **Allocation ratio** :\n - The allocation ratio of the PSA range corresponds to how much of the range is allocated to managed services. Each managed service you use reserves one or multiple ranges of varying size, depending on the service.\n - The allocation ratio of the PSA subnet corresponds to the number of IP addresses that are allocated from the range of the PSA subnet in the service-managed VPC network compared to the total number of IP addresses in the range.\n\nIn the case of Shared VPC, Network Analyzer provides this insight\nin the host project.\n\n### Managed services supporting the name field\n\nThe name field is populated for the following services:\n\n- AlloyDB for PostgreSQL\n- Apigee\n- Cloud Build\n- Cloud SQL\n- Memorystore for Memcached\n- Memorystore for Redis\n- Vertex AI managed notebooks\n\n### Recommendations\n\nReview the allocation ratio for your PSA ranges and consider [adding new\nallocated IP address\nranges](/vpc/docs/configure-private-services-access#modifying-connection) as\nsoon as the allocation ratio is greater than 50%."]]