Home ASN LookupAS44712

AS44712 eHAMnet-AS eHAMnet, s.r.o.

🇨🇿

Org handle: ORG-es128-RIPE

RIPE NCCallocated

Announced Prefixes (BGP)

3total

2 IPv41 IPv6

IPv4 Addresses

Allocated (RIR)4,352

Announced (BGP)2,560

IPv6 Addresses

Allocated (RIR)6.3×10²⁹

Announced (BGP)6.3×10²⁹

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

🇨🇿 CZ

RIR

RIPE NCC

Status

allocated

Allocated

2012-08-21

Announced Prefixes

(BGP)3

Prefix	RPKI	IRR	Last Seen
151.249.104.0/21	Valid	RIPE	2026-10-11
151.249.110.0/23	Valid	-	2026-10-11
2a01:a8c0::/29	Valid	RIPE	2026-10-11

Allocated Prefixes

(RIR)6

Prefix	Country	RIR	Status
151.249.104.0/21	🇨🇿 CZ	RIPENCC	allocated
151.249.106.0/24	🇨🇿 CZ	RIPE	assigned
151.249.110.0/23	🇨🇿 CZ	RIPE	assigned
185.91.204.0/22	🇨🇿 CZ	RIPENCC	allocated
185.91.204.0/23	🇨🇿 CZ	RIPE	assigned
2a01:a8c0::/29	🇨🇿 CZ	RIPENCC	allocated

All 3 announced prefixes of AS44712 →

BGP Neighbours

(seen in AS paths)

Upstreams (1)

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

AS39392SuperNetwork SH.Cz S.R.O3

Downstreams (1)

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

AS207231FuturNET FuturNET, S.R.O2

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 AS44712 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/44712

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

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