Global IP to ASN & Network Range Intelligence

NEWAPI32 v0.2 uses the IPtoASN hourly snapshot, published under the PDDL 1.0 public-domain dedication. The public API at IPtoASN was discontinued; this Actor downloads the current compressed TSV file once per run and performs local lookups. It does not access PeeringDB or RIPEstat.

What it does

Find the ASN and source network description for up to 50 input IPv4/IPv6 addresses; alternatively filter by up to 150 ASNs or a two-letter IP-range country. All supplied filters are combined. One output item represents a unique ASN, with the number of matched source ranges, up to 20 example ranges, country codes in those ranges and matching input IPs. No input filter defaults to a small two-IP example: 1.1.1.1 and 8.8.8.8, which typically completes well within five minutes.

The country is the snapshot's label for an IP range, not a facility location, operator domicile, or proof of service availability there. network_name is the source's AS description. The range count covers the records matching the supplied filters and the selected ASN; maxResults selects the first distinct ASNs encountered in the source's range order. The sample ranges are not a complete range export. Not-routed rows with ASN 0 are ignored.

This source does not provide website, network type, traffic capacity, data center, network-to-facility presence or POC contact fields. The Actor never invents these. A physical facility relationship cannot be inferred from an IP address or ASN. The previous PeeringDB prototype is archived under releases/0.1-peeringdb-blocked and is not part of the current Actor image.

Input and output

{"ipAddresses":["1.1.1.1","8.8.8.8"],"maxResults":5,"sampleRangesPerAsn":3}

Fields: ipAddresses (at most 50), asns (at most 150), country (two letters), maxResults (1–100, default 5), sampleRangesPerAsn (1–20, default 5). Leave ipAddresses empty when searching by ASN or country. The output includes asn, network_name, country_codes, range_count, ip_range_sample, optionally matched_ip_addresses, source URL and license, SHA-256 and the HTTP Last-Modified header when supplied. The SHA-256 identifies the compressed source snapshot, and is not a guarantee that every line is accurate.

The Apify Dataset is available as JSON through .../items and CSV through .../items?format=csv. Apify flattens nested arrays and objects in CSV, producing columns such as country_codes/0 and ip_range_sample/0/range_start. Clay and n8n can use JSON for structured samples or map these CSV columns directly.

Source handling

One HTTPS download per run. A 32 MB compressed size ceiling, 40-second request timeout, three backoff attempts, full streamed TSV parsing, a 240-second processing deadline, IP normalization, deduplication and result limit are applied. The source updates hourly, but the run's Last-Modified header is the authority for that particular response. Data is community/registry-derived and can lag live routing; it is not a BGP route monitor or security verdict. The Actor sends a named User-Agent and logs no secrets.

Pricing

The configured Apify Pay-per-Event setting is one synthetic apify-default-dataset-item event at $0.0065 per unique ASN record ($6.50 per 1,000). Source ranges, retries and repeated IPs do not create extra dataset items. There is no separate startup event. The Store price is authoritative. Owner-run usage may show zero charged events even while the event is configured; this does not establish what a buyer is charged. User max-charge limits are handled by the Python SDK's ChargeResult.

Verification

Run python3 -m unittest discover -s tests -v, then docker build -t newapi32:0.2 . on adf-netcup-01. The fixture tests do not hit the network. A two-IP live Apify run completed in 8.4 seconds with two unique ASN records. Source: IPtoASN. This independent Actor is not affiliated with IPtoASN.