Check AWS subnet IP usage: free addresses per subnet and overlapping VPCs
Each subnet’s free IPv4 addresses are in its AvailableIpAddressCount, which you compare with the block size minus the 5 addresses AWS reserves. CloudConsole’s VPC IP usage does that for every subnet of every VPC, flags subnets 80% full or more, and finds CIDR blocks that overlap between VPCs, saying whether a peering connection or transit gateway makes the overlap a problem today.


What it checks
Open Services → Tools → VPC IP usage. Each VPC is listed with its subnets, and for each subnet:
- CIDR block and Availability Zone, with its name tag.
- Free against usable: AWS’s
AvailableIpAddressCountagainst the block size minus the 5 addresses AWS keeps in every subnet, so a /24 reads “248 free of 251 usable (256 – 5 reserved)”, with a bar. - A flag at 80% or more. A full subnet is an outage waiting for a deploy: new instances, Lambda network interfaces and Fargate tasks can’t launch there, and Auto Scaling quietly fails to add capacity in that Availability Zone.
It then compares every VPC’s CIDR blocks, primary and secondary, in this region or with All regions or All accounts, across them. For each overlap it says what it means today:
- Both attached to the same transit gateway: a route for the shared range can point at only one VPC, so traffic meant for the other ends up in the wrong place.
- Peered: only the parts of the ranges that don’t overlap can be routed.
- Not connected yet: fine for now, but AWS won’t peer them, and connecting them later through a transit gateway or VPN needs readdressing first.
Subnets fill up for reasons that don’t show on a diagram: every interface endpoint, NAT gateway, load balancer node, VPC-attached Lambda function and EKS pod using the VPC CNI takes addresses. Seeing usage per subnet, rather than per VPC, is what tells you which tier to grow before the next scale-out.
How it works, and what it can read
Four EC2 reads per region; nothing is changed.
| What it reads | IAM actions |
|---|---|
| VPCs and their CIDR blocks | ec2:DescribeVpcs |
| Subnets and free addresses | ec2:DescribeSubnets |
| Which VPCs are connected | ec2:DescribeVpcPeeringConnections, ec2:DescribeTransitGatewayVpcAttachments |
If the peering or transit gateway read is denied, usage and overlaps still show; only the “does it matter today” note is missing.
All of these reads are in the AWS managed ReadOnlyAccess policy. ViewOnlyAccess leaves some out; Recommended permissions lists the extras. If one call is denied, the rest of the tool still works and says which permission is missing.
Nothing leaves your phone. The app signs each request with your own credentials, which stay in the iOS Keychain or Android Keystore, and sends it straight to AWS. There is no CloudConcur server in between, so we never see your resources or the results.
Free to look, Pro to fix. Every check only reads, so it works on the free plan (one account) and in the built-in demo. Where the tool offers a fix, it is the app’s usual action: it needs Pro, goes through the confirmation you set for that account and is recorded in the activity log on your phone.
Do it without the app
The numbers are one call away; the work is reading them for every region and comparing ranges by hand. Free addresses per subnet:
aws ec2 describe-subnets \
--query 'Subnets[].[VpcId,SubnetId,CidrBlock,AvailabilityZone,AvailableIpAddressCount]' \
--output table
Usable addresses are 2(32 − prefix) − 5, so a /20 has 4,091; divide to get the share used. Every VPC’s CIDR blocks, to look for overlaps:
aws ec2 describe-vpcs \
--query 'Vpcs[].[VpcId,CidrBlockAssociationSet[].CidrBlock]' --output json
Repeat with --region for each region and with each account’s profile. Amazon VPC IP Address Manager
(IPAM) can monitor subnet utilisation across an organization too; check its pricing tiers before turning it on. The
subnet calculator on this site plans new subnets and checks a pasted list for
overlaps.
Related free tool on this site:
- AWS subnet calculator (free, in your browser)
Questions
Why does AvailableIpAddressCount never reach the subnet size?
AWS reserves 5 addresses in every subnet (network, VPC router, DNS, future use and broadcast), so an empty /24 shows 251 available, not 256. The tool measures usage against those 251.
What should I do when a subnet is nearly full?
You can’t resize a subnet. Add a new subnet in the same Availability Zone, from free space in the VPC or from a secondary CIDR block, and point new capacity (Auto Scaling groups, Lambda, ECS services) at it.
Does it check IPv6?
Usage is for IPv4, where running out happens. IPv6 subnets are /64 and effectively never fill.
Try it on your own account
CloudConsole is on the App Store for iPhone and Google Play for Android. Every tool also works in the built-in demo, if you’d rather look around before connecting an account.
Details: Tools for your AWS account in the help centre.