IP to ASN (Deep) Database

Overview

The IP to ASN (Deep) 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 Deep-only fields and integration patterns for graph analytics, SIEM/SOAR enrichment, and capacity planning.

Available Database Formats

CSV

File Size: 215.97 MB

Entries: 32.8M

Fields: 15

Last Updated: Yesterday

Documentation

MMDB

File Size: 62.49 MB

Entries: 32.8M

Fields: 15

Last Updated: Yesterday

Documentation

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 (Deep) CSV database archive, you'll find the following files (with their types noted):

db-asn-details.csv.gz

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

File Size: 17.24 MB

Entries: 131.1K

Fields: 14

db-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: 198.73 MB

Entries: 32.8M

Fields: 3

README.md

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

File Size: 6.26 KB

checksum.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 (Deep) 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.

Field	Type	Description	Can be empty?	Example
start_ip	string	The starting IP address of the range in IPv4 or IPv6 format.	No	192.168.0.1
end_ip	string	The ending IP address of the range in IPv4 or IPv6 format.	No	192.168.0.255
id	number	The unique identifier for the ASN details.	No	1

I. Example Records

Example

start_ip,end_ip,asn_details_id
60.68.68.117,60.68.68.117,11458
77.131.193.0,77.131.193.255,109650
86.64.61.72,86.64.61.75,109650
124.105.48.237,124.105.48.237,87316
71.232.160.26,71.232.160.26,64614
176.113.74.47,176.113.74.47,86220
24.189.57.25,24.189.57.25,46769
109.79.36.5,109.79.36.5,109735
136.142.159.2,136.142.159.2,13200
93.11.239.0,93.11.239.69,109650

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.

Field	Type	Description	Can be empty?	Example
id	number	The unique identifier for the ASN details.	No	1
as_number	number	The Autonomous System Number (ASN), exported as a bare integer without the AS prefix.	No	29355
as_name	string	The name of the Autonomous System (AS).	No	GOOGLE
organization	string	The organization associated with the ASN.	No	Google LLC
country	string	The country where the ASN is registered.	No	US
type	string	The type of network associated with the ASN (e.g., business, residential, etc.).	No	business
domain	string	The domain associated with the ASN.	Yes	google.com
allocation_status	string	The allocation status of the ASN.	No	ASSIGNED
whois_host	string	The WHOIS host for the ASN.	Yes	whois.arin.net
peers	string	Comma-separated list of peer ASNs.	Yes	AS57950, AS58289, AS48502, AS9198
upstreams	string	Comma-separated list of upstream ASNs.	Yes	AS9009, AS174, AS64073, AS212024
downstreams	string	Comma-separated list of downstream ASNs.	Yes	AS9009, AS174, AS64073, AS212024
routes	string	Comma-separated list of announced route prefixes in CIDR notation.	Yes	164.40.102.0/24, 2.78.47.0/24, 164.0.212.0/24, 2.76.168.0/21
date_allocated	string	The date when the ASN was allocated.	Yes	1999-03-15

I. Example Records

Example

id,as_number,as_name,organization,country,type,domain,allocation_status,whois_host,peers,upstreams,downstreams,routes,date_allocated
11458,17676,GIGAINFRA,SoftBank Corp.,JP,ISP,,,JPNIC,"AS63774, AS59116, AS9605, AS138968","AS41095, AS9009, AS286, AS2518","AS59116, AS63774, AS9605, AS131923","126.223.0.0/16, 126.93.0.0/16, 60.93.0.0/16, 126.227.0.0/16",
13200,4130,UPITT-AS,University of Pittsburgh,US,EDUCATION,pitt.edu,,ARIN,"AS399855, AS33154, AS46887, AS5050","AS399855, AS33154, AS46887, AS5050",,"2620:102:4000::/42, 2620:102:401e::/47, 192.52.240.0/24, 192.52.164.0/23",1994-12-01
109650,15557,LDCOMNET,Societe Francaise Du Radiotelephone SFR SA,FR,ISP,gaoland.net,ASSIGNED,RIPE,"AS208719, AS34224, AS14537, AS42117","AS15943, AS30844, AS174, AS1267","AS48613, AS57584, AS207806, AS211556","93.191.80.0/21, 195.234.41.0/24, 88.140.0.0/15, 82.101.0.0/18",2002-09-19
109735,15502,Vodafone-Ireland-ASN,Vodafone Ireland Limited,IE,ISP,vodafone.com,ASSIGNED,RIPE,"AS14537, AS39120, AS20562, AS12969","AS3303, AS8220, AS6204, AS20562","AS35928, AS202148, AS34912, AS201310","109.77.200.0/22, 109.79.64.0/21, 109.78.160.0/21, 109.77.192.0/21",1970-01-01
46769,6128,CABLE-NET-1,Cablevision Systems Corp.,US,ISP,cv.net,,ARIN,"AS55081, AS1239, AS15169, AS14537","AS41095, AS174, AS19108, AS6939","AS20940, AS54004, AS19720","24.44.0.0/14, 216.255.96.0/19, 144.62.128.0/17, 148.77.128.0/17",
87316,9299,IPG-AS-AP,Philippine Long Distance Telephone Co.,PH,ISP,pldt.net,,APNIC,"AS34224, AS44901, AS12735, AS56099","AS205103, AS44901, AS6777, AS212024","AS14499, AS17448, AS45941, AS141676","49.148.96.0/20, 122.52.224.0/19, 180.193.64.0/19, 112.207.96.0/19",
86220,9009,M247,M247 Europe SRL,RO,ISP,m247.ro,ASSIGNED,RIPE,"AS211415, AS33823, AS48070, AS59919","AS15943, AS12302, AS205103, AS61626","AS211415, AS8245, AS56443, AS58321","162.246.186.0/24, 31.56.135.0/24, 38.205.0.0/22, 81.180.139.0/24",2011-04-11
64614,7922,COMCAST-7922,"Comcast Cable Communications, LLC",US,ISP,comcast.com,,ARIN,"AS6949, AS17035, AS395856, AS7018","AS6830, AS36498, AS174, AS286","AS7366, AS17035, AS6949, AS33652","48.46.178.0/23, 48.47.40.0/23, 48.47.85.0/24, 48.45.249.0/24",1997-02-14

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.

File Format & Encoding

All IP to ASN (Deep) 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 (Deep) MMDB database archive, you'll find the following files (with their types noted):

db-ip-asn.mmdb

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

File Size: 62.48 MB

Entries: 32.8M

README.md

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

File Size: 4.92 KB

checksum.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 (Deep) 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": "",
    "as_name": "GIGAINFRA",
    "as_number": "17676",
    "country_code": "JP",
    "date_allocated": "",
    "domain": "",
    "downstreams": "AS59",
    "organization": "SoftBank Corp.",
    "peers": "AS63",
    "routes": "126.",
    "type": "ISP",
    "upstreams": "AS41",
    "whois_host": "JPNIC"
  }
}

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 (Deep) 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:

Database file (the downloaded archive)
Signature file (the matching signature for that archive)
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.

Data Format & Constraints

All fields defined in the schema are always present in the IP to ASN (Deep) 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 (Deep) 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:

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

Our databases are updated continuously and shipped on a daily or weekly cycle depending on your plan, 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.

IP to ASN (Deep) Database

Overview

Available Database Formats

CSV Database Documentation

1. Overview

2. Archive Content

Schema

1. db-ip-asn.csv.gz

I. Example Records

2. db-asn-details.csv.gz

I. Example Records

3. File Relationship Diagram

File Format & Encoding

MMDB Database Documentation

1. Overview

2. Archive Content

Response Schema

1. db-ip-asn.mmdb

2. Field Reference

I. Example Records

Database Integrity & Authenticity Verification

1. Using the Signature File (Recommended)

2. Using the Checksum File (Legacy)

Data Format & Constraints

Database Updates & Delivery

Subscribe to Our Newsletter