IP ASN Database Extended


Overview

The IP to ASN Extended Database adds full routing context on top of standard ASN resolution—focusing on routes, peers, upstreams, and downstreams to model real-world topology. Built from live BGP collectors and route servers, it surfaces provider/customer relationships, peer sets, and active announcements to power peering strategy, leak/hijack detection, and path policy validation.

Designed for NetOps and security analytics, each record can include neighbor lists, relationship types, active routes with prefix scope, and change signals. If you only need basic ASN identity or prefixes, use the Lite dataset; this page documents the Extended-only fields and integration patterns for graph analytics, SIEM/SOAR enrichment, and capacity planning.


Available Database Formats

CSV
CSVCSV
  • File Size: 200.15 MB
  • Entries: 30.7M
  • Fields: 15
  • Last Updated: Today
MMDB
MMDBMMDB
  • File Size: 59.79 MB
  • Entries: 30.7M
  • Fields: 15
  • Last Updated: Today
Important
If you require our IP to ASN Extended Database in a different format, such as Parquet or any custom structure, please feel free to reach out to us via our Contact form. We are happy to accommodate specific format requests to meet your needs.

CSV Database Documentation


1. Overview

The CSV version is a set of Gzip-compressed CSV files containing IP ranges and their extended ASN information. Designed for bulk imports and integration into relational databases.


2. Archive Content

After downloading and extracting the IP to ASN Extended CSV database archive, you'll find the following files (with their types noted):

db-asn-details.csv.gz
db-asn-details.csv.gzdb-asn-details.csv.gz

Gzip-compressed CSV provides ASN info: number, organization, domain, type, and country.

  • File Size: 16.50 MB
  • Entries: 129.8K
  • Fields: 14
db-ip-asn.csv.gz
db-ip-asn.csv.gzdb-ip-asn.csv.gz

Each start_ip, end_ip links to the ASN details ID that is related to the asn-details file.

  • File Size: 183.65 MB
  • Entries: 30.7M
  • Fields: 3
README.md
README.mdREADME.md

Documentation for dataset contents, schema, usage, and support.

  • File Size: 4.55 KB
checksum.txt
checksum.txtchecksum.txt

SHA-256 checksums for verifying file integrity.

  • File Size: 247 Bytes

Schema

This section describes the schema of each file included in the IP to ASN Extended Database archive. For every file, you'll find its purpose, field definitions, and examples to help with integration.


1. db-ip-asn.csv.gz

This file contains IP address ranges linked to ASN information. It maps each IP block to a unique asn_details_id, which in turn corresponds to the AS's organization, domain, type, routes, peers, upstreams, downstreams, and country.

FieldTypeDescriptionCan be empty?Example
start_ipstringThe starting IP address of the range in IPv4 or IPv6 format.No192.168.0.1
end_ipstringThe ending IP address of the range in IPv4 or IPv6 format.No192.168.0.255
idnumberThe unique identifier for the ASN details.No1
Tip
asn_details_id joins to db-asn-details.id to get ASN information for IP.

I. Example Records

Example
start_ip,end_ip,asn_details_id
89.242.196.55,89.242.196.55,80550
24.18.213.248,24.18.213.248,64333
2a02:8424:6ec1:2601:799c:6ee2:d430:0,2a02:8424:6ec1:2601:799c:6ee2:d430:ffff,109068
181.134.171.22,181.134.171.22,81167
100.11.137.30,100.11.137.30,29255
189.46.112.0,189.46.112.54,79607
158.220.98.151,158.220.99.48,64940
67.4.67.103,67.4.67.103,26155
182.53.124.114,182.53.124.114,21099
205.178.90.51,205.178.90.51,46089

2. db-asn-details.csv.gz

This file contains detailed Autonomous System Number (ASN) information. Each entry links a unique ID to an AS number, organization, domain, routes, peers, upstreams, downstreams, type, and country.

FieldTypeDescriptionCan be empty?Example
idnumberThe unique identifier for the ASN details.No1
as_numberstringThe Autonomous System Number (ASN).NoAS15169
as_namestringThe name of the Autonomous System (AS).NoGOOGLE
organizationstringThe organization associated with the ASN.NoGoogle LLC
countrystringThe country where the ASN is registered.NoUS
typestringThe type of network associated with the ASN (e.g., business, residential, etc.).Nobusiness
domainstringThe domain associated with the ASN.Yesgoogle.com
allocation_statusstringThe allocation status of the ASN.Noallocated
whois_hoststringThe WHOIS host for the ASN.Yeswhois.arin.net
peersnumberThe number of peer ASNs.No150
upstreamsnumberThe number of upstream ASNs.No50
downstreamsnumberThe number of downstream ASNs.No30
routesnumberThe number of routes announced by the ASN.No2000
date_allocatedstringThe date when the ASN was allocated.Yes1999-03-15
Tip
id in the db-asn-details.csv.gz file joins to the asn_details_id field in db-ip-asn.csv.gz

I. Example Records

Example
id,as_number,as_name,organization,country,type,domain,allocation_status,whois_host,peers,upstreams,downstreams,routes,date_allocated
29255,701,UUNET,Verizon Business,US,ISP,verizonbusiness.com,,ARIN,"AS23351, AS4196, AS6648, AS13993","AS6830, AS174, AS286, AS4837","AS4196, AS63434, AS27570, AS398118","68.161.7.0/24, 141.154.0.0/16, 199.222.0.0/16, 71.255.32.0/20",1990-08-03
46089,6079,RCN-AS,RCN,US,ISP,rcn.com,,ARIN,"AS13379, AS14537, AS53777, AS19318","AS6830, AS34549, AS22356, AS286","AS19794, AS394534, AS13379, AS27514","65.86.216.0/21, 154.199.53.0/24, 198.170.16.0/20, 165.20.236.0/24",2001-04-04
109068,15557,LDCOMNET,Societe Francaise Du Radiotelephone SFR SA,FR,ISP,gaoland.net,ASSIGNED,RIPE,"AS208719, AS34224, AS34177, AS14537","AS15943, AS34177, AS30844, AS174","AS57584, AS207806, AS211556, AS42117","93.191.80.0/21, 195.234.41.0/24, 88.140.0.0/15, 82.101.0.0/18",2002-09-19
80550,13285,OPALTELECOM-AS,TalkTalk Communications Limited,GB,ISP,pxc.co.uk,ASSIGNED,RIPE,"AS16097, AS45629, AS59865, AS48070","AS34177, AS9009, AS174, AS212024","AS8586, AS47474","89.240.0.0/14, 89.240.0.0/15, 89.242.0.0/15, 217.8.0.0/19",2002-09-19
64333,7922,COMCAST-7922,"Comcast Cable Communications, LLC",US,ISP,comcast.com,,ARIN,"AS17035, AS395856, AS7018, AS22697","AS6830, AS36498, AS174, AS286","AS7366, AS17035, AS33652, AS7979","68.167.26.0/24, 107.0.0.0/14, 24.0.0.0/12, 24.104.128.0/19",1997-02-14
64940,51167,CONTABO,Contabo GmbH,DE,HOSTING,contabo.de,ASSIGNED,RIPE,"AS174, AS50968, AS208417, AS3356","AS13768, AS174, AS1299, AS3356",,"95.111.244.0/23, 193.34.144.0/23, 85.190.254.0/24, 38.242.144.0/21",2010-06-11
79607,27699,02.558.157/0001-62,TELEF�NICA BRASIL S.A,BR,BUSINESS,telefonica.com,,lacnic,"AS10429, AS18881, AS19182, AS10429","AS10429, AS19182, AS26599",,"187.56.0.0/16, 187.56.0.0/15, 189.46.0.0/16, 177.9.0.0/17",2003-08-25
21099,23969,TOT-NET,TOT Public Company Limited,TH,BUSINESS,ntplc.co.th,,APNIC,"AS23974, AS56120, AS24482, AS147027","AS38040, AS4651","AS133919, AS136737, AS135012, AS17827","101.51.48.0/22, 101.109.144.0/20, 182.53.18.0/24, 118.172.24.0/21",
81167,13489,CO-EPME1-LACNIC,UNE EPM TELECOMUNICACIONES S.A.,CO,ISP,tigo.com.co,,lacnic,"AS1239, AS14537, AS267842, AS174","AS3303, AS15830, AS6762, AS22356","AS267842, AS174, AS271833, AS272020","138.97.56.0/22, 2801:16:d800::/48, 2801:12:f800::/48, 2801:1a:d800::/48",1999-06-18
26155,209,CENTURYLINK-US-LEGACY-QWEST,"CenturyLink Communications, LLC",US,ISP,centurylink.com,,ARIN,"AS395696, AS26058, AS22266, AS46137",AS3356,"AS395696, AS46137, AS62520, AS40390","209.144.137.0/24, 65.40.156.0/24, 69.69.244.0/24, 74.4.48.0/20",1998-11-13

3. File Relationship Diagram

The diagram below illustrates the relationships between the various files included in the CSV database package. It shows how the main CSV file connects to reference table for asn details, ensuring accurate data linkage and integrity.

Image

File Format & Encoding

All IP to ASN Extended CSV datasets are provided in UTF-8 encoding, comma-separated, and compressed with Gzip (.csv.gz). Each file includes a header row listing the field names for clarity and consistency.

Field values are unquoted by default, with quotes applied only in the following cases:

  • Line breaks within text fields.
  • Commas inside a value (e.g., addresses).
  • Lists of values (e.g., languages).
  • Spaces that may be auto-quoted by export tools.

MMDB Database Documentation


1. Overview

MMDB version of the database consists of three files: one MMDB file containing all ASN information, a README file, and a checksum file, all compressed together in a ZIP file for easy delivery.


2. Archive Content

After downloading and extracting the IP to ASN Extended MMDB database archive, you'll find the following files (with their types noted):

db-ip-asn.mmdb
db-ip-asn.mmdbdb-ip-asn.mmdb

Provides full ASN details for IP addresses: organization, domain, type, and country.

  • File Size: 59.78 MB
  • Entries: 30.7M
README.md
README.mdREADME.md

Documentation for dataset contents, schema, usage, and support.

  • File Size: 4.55 KB
checksum.txt
checksum.txtchecksum.txt

SHA-256 checksums for verifying file integrity.

  • File Size: 157 Bytes

Response Schema

This section describes the structure of the data returned from the IP to ASN Extended MMDB file. Each field is detailed with its type, meaning, and example values to help you interpret responses and integrate them into your applications.


1. db-ip-asn.mmdb

This file contains Autonomous System Number (ASN) mappings for both IPv4 and IPv6 address ranges. Below is an example of the structure you will encounter in the response.


2. Field Reference

The following reference lists all fields available in the MMDB response. Each entry includes the field path, its description, data type, and example value to help you understand how to parse and integrate the data.

Showing 0 of 13
Select a field to view details

I. Example Records

Example
{
  "asn": {
    "allocation_status": "ASSIGNED",
    "as_name": "OPALTELECOM-AS",
    "as_number": "13285",
    "country_code": "GB",
    "date_allocated": "2002-09-19",
    "domain": "pxc.co.uk",
    "downstreams": "AS85",
    "organization": "TalkTalk Communications Limited",
    "peers": "AS16",
    "routes": "89.2",
    "type": "ISP",
    "upstreams": "AS34",
    "whois_host": "RIPE"
  }
}

Database Integrity & Authenticity Verification

There are two methods of verifying the integrity and authenticity of our Database:


1. Using the Signature File (Recommended)

IPGeolocation.io signs every database release to ensure its authenticity and integrity. This allows customers to verify that a downloaded IP to ASN Extended database file originates directly from IPGeolocation.io and has not been altered, corrupted, or tampered with during transfer or storage.

Each database update includes a corresponding signature file, generated using our private signing key. Customers can validate the database using the provided public verification key. To verify a database file, you need:

  1. Database file (the downloaded archive)
  2. Signature file (the matching signature for that archive)
  3. Public key (public-key.pem)

These files are available via official IPGeolocation.io download endpoints and are also shared in database update notifications.

Note

The public key may be provided as PEM-encoded text. Save it to a file named public-key.pem

Ensure OpenSSL is installed on your system. If not, install it using the following commands

On Linux, if openssl is not installed

sudo apt install openssl

Verify OpenSSL installation:

openssl version

To verify the database file, run the following command, replacing the placeholders with your actual file paths:

openssl dgst -sha256 -verify <path-to-public-key.pem> -signature <path-to-signature-file.sig> <path-to-database-file.zip>

Example output:

Verified OK

if verification FAILED do not use the file, re-download the database and signature from official IPGeolocation endpoints. If the issue persists, please contact our support team.


2. Using the Checksum File (Legacy)

Each database archive includes a checksum.txt file containing the SHA-256 checksums for the files packaged in the archive. You can use this file to validate that the extracted contents are complete and unchanged.

Tip

Always verify downloaded files with the provided checksum before importing.

On Linux, if sha256sum is not installed, first run:

sudo apt-get install coreutils

Then check the archive files against the checksum file with:

sha256sum -c checksum.txt

Example output:

db-asn-details.csv.gz: OK
db-ip-asn.csv.gz: OK
README.md: OK

*your output may differ depending on the specific database archive you downloaded.

If a file's checksum does not match, FAILED will be shown instead of OK . If verification fails, first confirm that the download completed correctly; if the issue persists, please contact our support team.

Important
Signature verification confirms both authenticity and integrity. Checksum verification confirms integrity only (it detects corruption/modification, but does not independently prove who produced the file).

Data Format & Constraints

  • All fields defined in the schema are always present in the IP to ASN Extended MMDB response.
  • Fields may contain empty strings (""), but never null, so null checks are not required.
  • Place names such as countries, states, districts, and cities are available in multiple translations.
  • All text values are encoded in UTF-8.
  • Field names and response structure remain stable across updates for backward compatibility.

Database Updates & Delivery

When you subscribe to our IP to ASN Extended database, we'll send you static download links. These links never change, so you can use them both for your initial download and for all future updates. You will receive:

  1. Database Archive URL : downloads the latest release of your subscribed database (CSV, MMDB or requested formats).
  2. Signature File URL : downloads the matching signature file for the latest release (used for authenticity verification).
  3. Public Key URL : downloads the public verification key (used with the signature file).
  4. Status Endpoint URL : returns the database's most recent update timestamp.

Our databases are refreshed daily and weekly, ensuring you always have access to the most current data. Each time your subscribed dataset is updated, you'll also receive an email notification so you don't miss a release.

For automated workflows, you can check our status endpoint to see the last update timestamp. When the date changes, simply re-fetch the archive using your static download URL to pull the latest version into your system.

Subscribe Our Newsletter

Get the latest in geolocation tech, straight to your inbox.