AS50326 IPTELECOM-AS INTERNET PROTOCOL TELECOM LTD

🇮🇪

Org handle: ORG-IPTL5-RIPE

RIPE NCCallocated

Announced Prefixes (BGP)

7total

7 IPv40 IPv6

IPv4 Addresses

Allocated (RIR)3,584

Announced (BGP)4,352

IPv6 Addresses

Allocated (RIR)6.3×10²⁹

Announced (BGP)0

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

RIR

Status

allocated

Allocated

2009-12-19

Announced Prefixes

(BGP)7

Prefix	RPKI	IRR	Last Seen
45.158.176.0/22	Valid	RIPE	2026-10-11
185.101.240.0/22	Valid	RIPE	2026-10-11
185.101.243.0/24	Valid	RIPE	2026-10-11
185.227.220.0/22	Valid	RIPE	2026-10-11
195.191.28.0/23	Valid	RIPE	2026-10-11
195.191.28.0/24	Valid	RIPE	2026-10-11
195.191.29.0/24	Valid	RIPE	2026-10-11

(RIR)5

Prefix	Country	RIR	Status
45.158.176.0/22	🇮🇪 IE	RIPENCC	allocated
185.101.240.0/22	🇮🇪 IE	RIPENCC	allocated
185.227.220.0/22	🇮🇪 IE	RIPENCC	allocated
195.191.28.0/23	🇮🇪 IE	RIPENCC	assigned
2a0c:ce00::/29	🇮🇪 IE	RIPENCC	allocated

(seen in AS paths)

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

ASPA

No ASPA

Abuse Contact

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 AS50326 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

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

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