Home ASN LookupAS39371

AS39371 acknowledge-bc Acknowledge Benelux B.V.

🇳🇱

Org handle: ORG-ABB5-RIPE

RIPE NCCallocated

Announced Prefixes (BGP)

4total

2 IPv42 IPv6

IPv4 Addresses

Allocated (RIR)2,048

Announced (BGP)2,048

IPv6 Addresses

Allocated (RIR)1.2×10³⁰

Announced (BGP)1.2×10³⁰

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

🇳🇱 NL

RIR

RIPE NCC

Status

allocated

Allocated

2019-09-13

Announced Prefixes

(BGP)4

Prefix	RPKI	IRR	Last Seen
45.129.60.0/22	Valid	RIPE	2026-10-11
185.99.204.0/22	Valid	RIPE	2026-10-11
2a06:1480::/29	Valid	RIPE	2026-10-11
2a0e:44c0::/29	Valid	RIPE	2026-10-11

Allocated Prefixes

(RIR)4

Prefix	Country	RIR	Status
45.129.60.0/22	🇳🇱 NL	RIPENCC	allocated
185.99.204.0/22	🇳🇱 NL	RIPENCC	allocated
2a06:1480::/29	🇳🇱 NL	RIPENCC	allocated
2a0e:44c0::/29	🇳🇱 NL	RIPENCC	allocated

All 4 announced prefixes of AS39371 →

BGP Neighbours

(seen in AS paths)

Upstreams (2)

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

AS24785JOINTTRANSIT Broadband Hosting B.V3
AS8455ATOM86 BV1

Transfer History

Registry transfers of AS39371 between organisations.

AS39371Transfer · 2022-08-23
Comaxx B.V.
RIPE NCC
→
Acknowledge Benelux B.V.
RIPE NCC

Date	Resource	From	To	Type
2022-08-23	AS39371	Comaxx B.V. RIPE NCC	Acknowledge Benelux B.V. RIPE NCC	Transfer

ASPA

No ASPA

Abuse Contact

External Links

RIPE Whois RIPEstat

Learn more

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 AS39371 should publish an ASPA object
IPv4 transfers in the RIPE NCC regionMonthly volume and the latest registry transfers
ASN data in AI agents and SIEMMCP server and API integrations

API

Open

GEThttps://api.ipctl.io/v1/asn/39371

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

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