CloudConsole

AWS IP address lookup: which service and region owns this IP?

Free, in your browser · IPv4 and IPv6 · AWS data published 17 November 2026, 19:07 UTC

Look up an IP address

Data: AWS ip-ranges.json published 17 November 2026, 19:07 UTC (syncToken 1794942425), 10,759 IPv4 and 7,055 IPv6 entries. The lookup runs in your browser against a copy served from this site; the addresses you enter aren’t sent anywhere.

Short answer

Enter an IP address and the tool checks it against ip-ranges.json, the list of public IP ranges AWS publishes, showing every matching prefix with its service, region and network border group. A match means the address is AWS-owned address space, such as an EC2, S3 or CloudFront range; it doesn’t tell you which AWS customer is using it.

How to read the result

  • Most specific prefix first. One address usually matches several prefixes: a large block listed under AMAZON and a smaller one listed under a service. The smallest block (longest prefix) is the most precise answer.
  • AMAZON is the superset. Every range listed for any service is also listed under AMAZON, and some ranges appear only there. “AMAZON only” means AWS owns the address but the file doesn’t attribute it to a narrower service.
  • Service codes can overlap. When one service runs on another’s infrastructure, a range can be listed under both. AWS’s example: some ranges are listed under both S3 and EC2 but are used only by S3. To find addresses used only by EC2, take the EC2 ranges that aren’t also under S3.
  • Some codes are one-directional. API_GATEWAY ranges are egress only, and CLOUDFRONT_ORIGIN_FACING is the set CloudFront uses to reach your origin, not the addresses viewers connect to.
  • Region and border group. The region is where the range is used, or GLOBAL for services such as CloudFront and Global Accelerator. The network border group is the set of Availability Zones or Local Zones that advertise it; a Local Zone range names its zone group, like us-west-2-lax-1.

What a match does and doesn’t tell you

A match means the address belongs to AWS. It doesn’t identify the AWS account or the person behind it: an EC2 public IPv4 address is reassigned to another customer when an instance releases it, and AWS doesn’t publish which customer holds an address at any time. If traffic from an AWS address is abusive, report it to AWS through its abuse reporting process with the address, timestamps and logs.

If you think the address is one of yours, search your own accounts. For EC2 and anything else with a network interface, aws ec2 describe-network-interfaces --filters Name=association.public-ip,Values=203.0.113.25 finds the interface that has that public IP in the current region; the find an EC2 instance by IP guide covers private addresses and the console too.

No match doesn’t always mean “not AWS”. AWS publishes ranges for the services customers most often filter on, not for every service, and addresses brought to AWS with BYOIP aren’t in the file.

AWS IP ranges by service

How many prefixes AWS lists for each service code in the copy used on this page (10,759 IPv4 and 7,055 IPv6 entries across 42 regions plus GLOBAL, published 17 November 2026, 19:07 UTC).

Service codeIPv4 prefixesIPv6 prefixes
AMAZON6,1123,284
EC21,9052,585
S3487664
ROUTE53_RESOLVER6380
IVS_REALTIME104150
CLOUDFRONT21735
API_GATEWAY2160
EFS10194
GLOBALACCELERATOR13447
WORKSPACES_GATEWAYS7343
EBS1050
KINESIS_VIDEO_STREAMS1050
DYNAMODB960
CLOUDFRONT_ORIGIN_FACING5238
EC2_INSTANCE_CONNECT3737
CODEBUILD610
MEDIA_PACKAGE_V2600
ROUTE53_HEALTHCHECKS3126
AMAZON_APPFLOW480
CLOUD9440
AURORA_DSQL2121
ROUTE532614
ROUTE53_HEALTHCHECKS_PUBLISHING390
AMAZON_CONNECT2115
CHIME_VOICECONNECTOR240
CHIME_MEETINGS11
IVS_LOW_LATENCY11

Use the AWS IP ranges yourself

Download the file with curl -O https://ip-ranges.amazonaws.com/ip-ranges.json and filter it with jq. These examples follow the AWS documentation:

# when this version of the file was published
jq .createDate < ip-ranges.json

# IPv4 ranges for one service in one region
jq -r '.prefixes[] | select(.region=="us-east-1" and .service=="S3") | .ip_prefix' < ip-ranges.json

# all IPv6 ranges for CloudFront
jq -r '.ipv6_prefixes[] | select(.service=="CLOUDFRONT") | .ipv6_prefix' < ip-ranges.json

To find out when the ranges change, subscribe to the Amazon SNS topic arn:aws:sns:us-east-1:806199016981:AmazonIpSpaceChanged (in us-east-1); every notification means a new file. For security groups and route tables, prefer an AWS-managed prefix list where one exists, such as com.amazonaws.global.cloudfront.origin-facing for CloudFront: AWS keeps it current, so you don’t have to copy ranges by hand.

Questions

How do I check if an IP address belongs to AWS?

Look it up in ip-ranges.json, the list of public IP ranges AWS publishes at https://ip-ranges.amazonaws.com/ip-ranges.json. If any prefix contains the address, it is AWS address space. The tool above does that lookup in your browser for IPv4 and IPv6.

Can I find out which AWS customer is using an IP address?

No. ip-ranges.json says which AWS service subset and region a range belongs to, not which account is using an address. AWS doesn’t publish that. If the address is attacking or spamming you, report it to AWS through its abuse reporting process; if you think it’s one of your own resources, search your accounts’ network interfaces for it.

Why does an IP show both AMAZON and another service like EC2?

AMAZON is the superset: every range listed for any service is also listed under AMAZON, and some ranges are only listed under AMAZON. The more specific service code, such as EC2, S3 or CLOUDFRONT, tells you which part of AWS uses the range.

Why isn’t an address I know is on AWS found?

AWS doesn’t publish ranges for every service, and addresses customers bring to AWS with BYOIP aren’t in the file. The lookup also uses the copy of the file shown on this page, so a range added since then won’t appear until the next update.

What is a network border group?

The set of Availability Zones or Local Zones from which AWS advertises the addresses, or GLOBAL for services such as CloudFront whose traffic can come from many locations. For most ranges it is the same as the region; for Local Zones it names the zone group, such as us-west-2-lax-1.

How do I know when AWS IP ranges change?

Subscribe to the Amazon SNS topic arn:aws:sns:us-east-1:806199016981:AmazonIpSpaceChanged. AWS publishes a notification whenever ip-ranges.json changes, and the file’s syncToken and createDate tell you which version you have.

Your AWS accounts, from your phone

CloudConsole puts alarms, logs, costs and resources from every AWS account and region on your iPhone or Android phone, with credentials that never leave the device.

About the app →

Sources