AS1797 Uruguay

🇺🇾

Org handle: 11703

LACNICallocated

Announced Prefixes (BGP)

24total

23 IPv41 IPv6

IPv4 Addresses

Allocated (RIR)65,536

Announced (BGP)80,640

IPv6 Addresses

Allocated (RIR)7.9×10²⁸

Announced (BGP)7.9×10²⁸

Prefix Limit (IPv4)

100

Prefix Limit (IPv6)

Country

RIR

Status

allocated

Allocated

1994-04-14

Announced Prefixes

(BGP)24

Prefix	RPKI	IRR	Last Seen
164.73.0.0/16	No ROA	Other IRR	2026-10-11
164.73.20.0/23	No ROA	-	2026-10-11
164.73.28.0/23	No ROA	-	2026-10-11
164.73.32.0/20	No ROA	-	2026-10-11
164.73.52.0/22	No ROA	-	2026-10-11
164.73.66.0/23	No ROA	-	2026-10-11
164.73.80.0/21	No ROA	-	2026-10-11
164.73.108.0/24	No ROA	-	2026-10-11
164.73.112.0/24	No ROA	-	2026-10-11
164.73.116.0/24	No ROA	-	2026-10-11

1-10 of 24

1 / 3

(RIR)2

Prefix	Country	RIR	Status
164.73.0.0/16	🇺🇾 UY	LACNIC	assigned
2001:1328::/32	🇺🇾 UY	LACNIC	assigned

(seen in AS paths)

Networks AS1797 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 AS1797 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/1797" | jq