๐ BGP.Tools-OpenDB provides daily updated BGP data packages for researchers, developers, and network engineers.
Data is sourced from bgp.tools HTTP API, processed and packaged in multiple formats using Node.js.
็ฎไฝไธญๆ | English version
- Release Versions: Use both
.xz(high compression ratio) and.gz(fast decompression) formats - Auto-update Branch: Uses only
.gzformat to balance storage space and update efficiency
-
Data Content: All prefix-to-origin ASN mappings from the global routing table
-
Data Fields:
CIDR: IP prefix (IPv4/IPv6)ASN: Origin AS numberHits: Number of occurrences in BGP routing table
-
Data Source: https://bgp.tools/table.jsonl
-
Sample Data:
{"CIDR":"2a0c:2f07:d::/48","ASN":206924,"Hits":509} {"CIDR":"2a0c:2f07:f::/48","ASN":206924,"Hits":508} {"CIDR":"185.230.223.0/24","ASN":206924,"Hits":1862}
- Use Case: Fast IP โ ASN lookup
- Technical Features:
- Based on MaxMind DB (MMDB) format
- Supports both IPv4/IPv6 dual-stack queries
-
Data Fields:
asn: AS number (format: AS+number)name: AS registered nameclass: AS type classification (Unknown/Eyeball/Transit, etc.)cc: Country code (IATA 3166-1 alpha-2)
-
Typical Applications: ASN information display, network attribution analysis
-
Sample Data:
asn,name,class,cc AS1,"Level 3 Parent, LLC",Unknown,US AS10,CSNET Coordination and Information Center (CSNET-CIC),Unknown,US AS100,FMC Central Engineering Laboratories,Unknown,US AS10000,Nagasaki Cable Media Inc.,Eyeball,JP
-
Data Format: One tag definition per line, format:
tag_name,data_count -
Typical Tag Categories:
- Network Types:
dsl,mobile,satnet - Service Types:
cdn,vpn,anycast - Organizations:
gov,uni,corp
- Network Types:
-
Sample Data:
perso,1337 dsl,2735 cdn,107 a10k,1315 vpn,769
-
Data Format: One ASN record per line, format:
ASN,AS_name -
Typical Applications: Filtering and analysis of specific ASN types
-
Sample Data (CDN tags):
AS13335,"Cloudflare, Inc." AS395403,NSONE Inc AS16276,OVH SAS AS19551,Incapsula Inc
- Update Frequency: Daily automatic packaging at
UTC 00:30 - Data Source: Pulls latest data from
auto-updatebranch
The auto-update branch is a moving snapshot of the latest generated data. Its
history is intentionally rewritten on each sync so repeated large data updates do
not grow the Git repository. Historical daily archives are published as GitHub
Release assets instead.
-
Update Frequency: Every 2 hours
-
Version Retention: Latest snapshot only
-
Metadata Fields:
{ "timestamp": 1735689600, "version": "1.0", "hash_list": { "ipv4.jsonl": "<SHA256 Hash>", "ipv6.jsonl": "<SHA256 Hash>" } }
- Update Frequency: Daily
- Version Retention: Latest snapshot only
- Metadata Fields: Similar structure as routing table data
- Update Frequency: Daily
- Version Retention: Latest snapshot only
- Metadata Fields: Similar structure as above, with individual metadata for each tag category
- Node.js >= 20.0.0
- pnpm >= 8.0.0
# Install dependencies
pnpm install
# Fetch routing table data (approximately 2-3 minutes)
pnpm fetch:table
# Fetch ASN mapping data (approximately 30 seconds)
pnpm fetch:asns
# Fetch all tags data (approximately 1 minute)
pnpm fetch:tags
# Fetch all data (recommended)
pnpm fetch:allpnpm dev # Watch mode with automatic updates