Home ASN LookupAS39455

AS39455 Tlapnet-SK-AS Jiri Tlapak

🇨🇿

Org handle: ORG-JT76-RIPE

RIPE NCCallocated

Announced Prefixes (BGP)

1total

1 IPv40 IPv6

IPv4 Addresses

Allocated (RIR)1,024

Announced (BGP)1,024

IPv6 Addresses

Allocated (RIR)0

Announced (BGP)0

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

🇨🇿 CZ

RIR

RIPE NCC

Status

allocated

Allocated

2015-01-29

Announced Prefixes

(BGP)1

Prefix	RPKI	IRR	Last Seen
185.85.36.0/22	Valid	RIPE	2026-10-09

Allocated Prefixes

(RIR)1

Prefix	Country	RIR	Status
185.85.36.0/22	🇨🇿 CZ	RIPENCC	allocated

All 1 announced prefix of AS39455 →

BGP Neighbours

(seen in AS paths)

Upstreams (1)

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

AS47232ISPAlliance ISP Alliance A.S1

Downstreams (1)

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

AS205164SzariAS AIR Optic Solutions S.R.O1

Transfer History

Registry transfers of AS39455 between organisations.

AS39455Transfer · 2023-10-23
KALIANT s.r.o.
RIPE NCC
→
Jiri Tlapak
RIPE NCC

Date	Resource	From	To	Type
2023-10-23	AS39455	KALIANT s.r.o. RIPE NCC	Jiri Tlapak 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 AS39455 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/39455

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

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