AS397451 ZEROBOUNCE - ZeroBounce

🇺🇸

ARINassigned

Announced Prefixes (BGP)

8total

7 IPv41 IPv6

IPv4 Addresses

Allocated (RIR)9,728

Announced (BGP)10,240

IPv6 Addresses

Allocated (RIR)0

Announced (BGP)1.2×10²⁴

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

RIR

Status

assigned

Allocated

2019-04-02

Announced Prefixes

(BGP)8

Prefix	RPKI	IRR	Last Seen
45.67.100.0/24	Valid	RIPE	2026-10-11
64.43.192.0/19	Valid	ARIN	2026-10-11
85.204.196.0/23	Valid	RIPE	2026-10-11
85.204.196.0/24	Valid	RIPE	2026-10-11
85.204.197.0/24	Valid	RIPE	2026-10-11
89.46.112.0/23	Valid	RIPE	2026-10-11
185.25.156.0/24	Valid	RIPE	2026-10-11
2a09:e880::/48	Valid	RIPE	2026-10-11

(RIR)5

Prefix	Country	RIR	Status
64.43.192.0/19	🇺🇸 US	ARIN	allocated
85.204.196.0/23	🇷🇴 RO	RIPENCC	allocated
85.204.196.0/24	🇺🇸 US	RIPE	assigned
85.204.197.0/24	🇺🇸 US	RIPE	assigned
89.46.112.0/23	🇷🇴 RO	RIPENCC	allocated

(seen in AS paths)

Networks AS397451 hands its own prefixes to: transit providers, or peers at an exchange.

ASPA

No ASPA

External Links

What is an ASN?Autonomous systems, ASN ranges and how they are assigned
RPKI and route origin validationWhat the RPKI badges on the prefix list mean
ASPA explainedWhy AS397451 should publish an ASPA object
IPv4 transfers in the ARIN regionMonthly volume and the latest registry transfers
ASN data in AI agents and SIEMMCP server and API integrations

API

Returns ASN details, announced prefixes, and BGP routing data.

curl -s "https://api.ipctl.io/v1/asn/397451" | jq