Free calculator
AWS public IPv4 cost calculator
Since February 2024, every public IPv4 address costs $0.005 an hour, about $3.60 a month, in every region, whether it is attached to anything or not. Most accounts hold more of them than anyone remembers creating.
Elastic IPs, auto-assigned instance IPs, load balancer nodes, NAT gateways — they all bill.
Idle Elastic IPs, instances that could sit behind one load balancer, IPv6-capable endpoints.
You're paying now
$36.00/month
$432.00/year · ≈ £28/month
Potential saving
$14.40/month
$172.80/year · ≈ £11/month
Based on AWS’s $0.005/hour public IPv4 charge ($3.60/month at 730 hours). Same rate in every region.
Not sure how many public IPv4 addresses you actually have? Our free read-only scan counts them across every region — along with 70+ other cost checks.
Estimate the whole billWhere public IPv4 charges hide
- →Idle Elastic IPs. Allocated once for a migration or a test, never released. Still billing every hour.
- →One public IP per instance. Three web servers with three public IPs where one load balancer would do. That is two wasted addresses and a wider attack surface for no benefit.
- →Load balancer nodes. An internet-facing ALB bills one public IPv4 for every availability zone it is enabled in, so usually two or three rather than one.
- →NAT gateways. Each NAT gateway holds an Elastic IP. You cannot avoid that if you need the NAT, but it is worth knowing it is in the count.
- →Forgotten regions. An EIP left behind in a region you stopped using years ago bills exactly like one in production.
Frequently asked questions
How much does a public IPv4 address cost on AWS?
Since 1 February 2024, $0.005 an hour for every public IPv4 address in every region, which is about $3.60 a month or $43.80 a year. It bills whether the address is attached to a running resource or sitting idle.
Do idle Elastic IPs still cost money?
Yes, and they always did. An unattached Elastic IP bills the same $0.005 an hour as an attached one. If it is not pointing at anything you need, releasing it saves the money outright with no risk to any workload.
Which resources use public IPv4 addresses?
EC2 instances with auto-assigned public IPs, Elastic IPs, each availability-zone node of an internet-facing load balancer, NAT gateways, some RDS and OpenSearch configurations, and Global Accelerator. They each bill separately, so the count is usually higher than people expect.
How do I find every public IPv4 address in my account?
Public IP Insights, inside Amazon VPC IP Address Manager, lists them per region on the free tier. Our free read-only scan also counts them across every region and flags the idle ones, along with seventy plus other checks.
How do I reduce the public IPv4 charge?
Release the unattached Elastic IPs, put several instances behind one load balancer rather than giving each its own public IP, move internal services into private subnets, and turn on IPv6 wherever your clients support it, because AWS does not charge for IPv6 addresses.