ipverse-asn-ip

IPv4 and IPv6 subnets (e.g. 100.2.30.0/22) organized by announcing autonomous systems. The subnets are aggregated to save space.

This repository is updated daily.

Use cases

• Firewalling, e.g. to ban all IP addresses from that notorious, Spam-friendly network provider
• Route advertisment check, see if/how the routes of a specific autonomous system are seen (even over time, thanks to Git's changelog)
• Find out more about a specific ASN (autonomous system number) using the provided lookup table (currently .csv format only) or use it in your own software project for bulk/offline use
• Statistical analysis purposes, e.g. the number of public IPv4 addresses currently announced vs unused/unassigned

How to use

To download the announced subnets for a specific autonomous system (AS1234 IPv4 adresses in this example), try:
$ curl https://raw.githubusercontent.com/ipverse/asn-ip/master/as/1234/ipv4-aggregated.txt

The same for all IPv6 subnets from AS1234:
$ curl https://raw.githubusercontent.com/ipverse/asn-ip/master/as/1234/ipv6-aggregated.txt

The data (IPv4 + IPv4 combined) is available in JSON format as well:
$ curl https://raw.githubusercontent.com/ipverse/asn-ip/master/as/1234/aggregated.json

The resulting JSON will look similar to this:

{
  "asn": 1234,
  "handle": "FORTUM",
  "description": "Fortum",
  "subnets": {
    "ipv4": [
      "132.171.0.0/16",
      "137.96.0.0/16",
      "193.110.32.0/21"
    ],
    "ipv6": [
      "2405:1800::/32"
    ]
  }
}

To download the latest lookup table used to enhance the generated route data:
$ curl https://raw.githubusercontent.com/ipverse/asn-ip/master/as.csv

If you plan to use the routing data for firewalling purposes, have a look at:

• ipset-blacklistlist ipset/iptables based Bash script, IPv4 only
• todo insert link to a popular project with nftables and IPv6 support

Yeah, but how to I get the ASN for an IP address?

Check out this excellent blog post: https://blog.jiayu.co/2018/10/quick-url-to-asn-lookups/