AS54646 HARDYNET - Hardy Telecommunications

🇺🇸

ARINassigned

Announced Prefixes (BGP)

8total

7 IPv41 IPv6

IPv4 Addresses

Allocated (RIR)7,168

Announced (BGP)8,704

IPv6 Addresses

Allocated (RIR)7.9×10²⁸

Announced (BGP)7.9×10²⁸

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

RIR

Status

assigned

Allocated

2012-04-17

Announced Prefixes

(BGP)8

Prefix	RPKI	IRR	Last Seen
63.67.238.0/24	No ROA	ARIN	2026-10-10
63.67.240.0/23	No ROA	ARIN	2026-10-10
63.92.148.0/23	No ROA	ARIN	2026-10-10
65.209.25.0/24	No ROA	ARIN	2026-10-10
131.162.152.0/21	Valid	ARIN	2026-10-10
172.111.4.0/22	Valid	ARIN	2026-10-10
198.41.48.0/20	Valid	ARIN	2026-10-10
2604:bfc0::/32	Valid	ARIN	2026-10-10

(RIR)4

Prefix	Country	RIR	Status
131.162.152.0/21	🇺🇸 US	ARIN	allocated
172.111.4.0/22	🇺🇸 US	ARIN	allocated
198.41.48.0/20	🇺🇸 US	ARIN	allocated
2604:bfc0::/32	🇺🇸 US	ARIN	allocated

(seen in AS paths)

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

Networks whose own prefixes AS54646 passes on: usually its customers.

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 AS54646 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/54646" | jq