Home ASN LookupAS52029

AS52029 ASNOVOSEDLY Palanet s.r.o.

🇨🇿

Org handle: ORG-PALA1-RIPE

RIPE NCCallocated

Announced Prefixes (BGP)

9total

9 IPv40 IPv6

IPv4 Addresses

Allocated (RIR)2,048

Announced (BGP)4,096

IPv6 Addresses

Allocated (RIR)0

Announced (BGP)0

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

🇨🇿 CZ

RIR

RIPE NCC

Status

allocated

Allocated

2010-12-17

Announced Prefixes

(BGP)9

Prefix	RPKI	IRR	Last Seen
46.174.32.0/21	No ROA	RIPE	2026-10-10
46.174.32.0/24	No ROA	-	2026-10-10
46.174.33.0/24	No ROA	-	2026-10-10
46.174.34.0/24	No ROA	-	2026-10-10
46.174.35.0/24	No ROA	-	2026-10-10
46.174.36.0/24	No ROA	-	2026-10-10
46.174.37.0/24	No ROA	-	2026-10-10
46.174.38.0/24	No ROA	-	2026-10-10
46.174.39.0/24	No ROA	-	2026-10-10

Allocated Prefixes

(RIR)1

Prefix	Country	RIR	Status
46.174.32.0/21	🇨🇿 CZ	RIPENCC	assigned

All 9 announced prefixes of AS52029 →

BGP Neighbours

(seen in AS paths)

Upstreams (1)

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

AS28725CETIN A.S9

Transfer History

Registry transfers of AS52029 between organisations.

AS52029Transfer · 2019-11-21
Ing. Petr Lukes
RIPE NCC
→
Palanet s.r.o.
RIPE NCC

Date	Resource	From	To	Type
2019-11-21	AS52029	Ing. Petr Lukes RIPE NCC	Palanet s.r.o. 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 AS52029 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/52029

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

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