AS52322 TELCOCOM

🇦🇷

Org handle: 74189

LACNICallocated

Announced Prefixes (BGP)

24total

23 IPv41 IPv6

IPv4 Addresses

Allocated (RIR)5,120

Announced (BGP)10,496

IPv6 Addresses

Allocated (RIR)7.9×10²⁸

Announced (BGP)7.9×10²⁸

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

RIR

Status

allocated

Allocated

2011-05-04

Announced Prefixes

(BGP)24

Prefix	RPKI	IRR	Last Seen
38.51.26.0/24	No ROA	-	2026-10-11
190.14.156.0/22	Valid	LACNIC	2026-10-11
190.14.156.0/24	Valid	-	2026-10-11
190.14.157.0/24	Valid	-	2026-10-11
190.14.158.0/24	Valid	-	2026-10-11
190.14.159.0/24	Valid	-	2026-10-11
191.97.32.0/20	Valid	LACNIC	2026-10-11
191.97.32.0/24	Valid	-	2026-10-11
191.97.33.0/24	Valid	-	2026-10-11
191.97.34.0/24	Valid	-	2026-10-11

1-10 of 24

1 / 3

(RIR)3

Prefix	Country	RIR	Status
190.14.156.0/22	🇦🇷 AR	LACNIC	allocated
191.97.32.0/20	🇦🇷 AR	LACNIC	allocated
2803:f200::/32	🇦🇷 AR	LACNIC	allocated

(seen in AS paths)

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

ASPA

No ASPA

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 AS52322 should publish an ASPA object
IPv4 transfers in the LACNIC 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/52322" | jq