ResearchRouting table, RPKI, IRR & looking glass

AS52224 LACNIC - Latin American and Caribbean IP address

AS52224 (AS52224) is registered to LACNIC - Latin American and Caribbean IP address in UY, through LACNIC. It originates 6 prefixes in the global routing table.

3
IPv4 prefixes
3
IPv6 prefixes
768
IPv4 addresses
100%
RPKI valid

Who holds AS52224

Names from RIPE NCC’s daily list of every allocated AS number. The ASN lookup fetches the full WHOIS record live.

AS number
AS52224
Handle
AS52224
Organization
LACNIC - Latin American and Caribbean IP address
Country
UY
Registry
LACNIC
ASPA
None published
WHOIS recordLACNIC
% IP Client: 2607:e580:0:141:0:0:0:100
 
% Joint Whois - whois.lacnic.net
%  This server accepts single ASN, IPv4 or IPv6 queries

% LACNIC resource: whois.lacnic.net


% Copyright LACNIC lacnic.net
%  The data below is provided for information purposes
%  and to assist persons in obtaining information about or
%  related to AS and IP numbers registrations
%  By submitting a whois query, you agree to use this data
%  only for lawful purposes.
%  2026-10-12 03:22:26 (Z Z)

aut-num:     AS52224
owner:       LACNIC - Latin American and Caribbean IP address
ownerid:     UY-LACN-LACNIC
responsible: Ernesto Majó
address:     Rambla República de México, 6125, Esquina 6 de Abril
address:     11400 - Montevideo - Montevideo
country:     UY
phone:       +598  26042222 [4401]
owner-c:     AIL
routing-c:   AIL
abuse-c:     AIL
created:     20100212
changed:     20100212

nic-hdl:     AIL
person:      Carlos M Martínez
e-mail:      ipadmin@lacnic.net
address:     Rambla Rep. de México, 6125, Casa de Internet
address:     11400 - Montevideo - Montevideo
country:     UY
phone:       +598  26042222 [4401]
created:     20080125
changed:     20260926

% whois.lacnic.net accepts only direct match queries.
% Types of queries are: POCs, ownerid, CIDR blocks, IP
% and AS numbers.

What AS52224 announces

Prefixes originated by AS52224 in the routing table our collectors hold (kept current as routes change), each checked against the RPKI (every ten minutes) and the IRR (daily).

IPv4 prefixes
3
IPv6 prefixes
3
IPv4 addresses
768 (3 /24s)
RPKI valid
6 100%
RPKI invalid
0
RPKI not found
0
ROAs naming AS52224
6
With an IRR route object
6 100%

Announced prefixes

Each opens its own page: who announces it, the paths our collectors see, its ROAs and route objects.

IPv4 (3)
IPv6 (3)

RPKI valid   RPKI invalid   no ROA covers it

Who AS52224 buys transit from

Inferred from the AS paths in the RouteViews tables and our own collectors’ feeds, refreshed every 4 hours, most-seen first. 3 upstreams.

Who buys transit from AS52224

None seen: AS52224 does not appear to provide transit to anyone.

Routing registry objects

From the mirrored IRR databases (RADB, the five RIRs and more). Look it up live.