ResearchRouting table, RPKI, IRR & looking glass

AS28001 LACNIC - Latin American and Caribbean IP address

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

5
IPv4 prefixes
1
IPv6 prefixes
1,024
IPv4 addresses
100%
RPKI valid

Who holds AS28001

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

AS number
AS28001
Handle
AS28001
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 00:04:32 (-03 -03:00)

aut-num:     AS28001
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:     20080902
changed:     20240917

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 AS28001 announces

Prefixes originated by AS28001 in the RouteViews table (refreshed every four hours), each checked against the RPKI (every ten minutes) and the IRR (daily).

IPv4 prefixes
5
IPv6 prefixes
1
IPv4 addresses
1,024 (4 /24s)
RPKI valid
6 100%
RPKI invalid
0
RPKI not found
0
ROAs naming AS28001
6
With an IRR route object
3 50%

Announced prefixes

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

IPv4 (5)
IPv6 (1)

RPKI valid   RPKI invalid   no ROA covers it

Who AS28001 is reached through

The AS just before AS28001 in the paths our looking glass collectors hold, for 6 of its prefixes. Usually a transit provider, sometimes a peer. The number is how many of those prefixes it was seen on.

Routing registry objects

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

Sourceas-nameMaintained by
LACNICAS28001MNT-UY-LACN-LACNIC
RADBLACNIC-ASN-28001MAINT-LACNIC

Route objects with origin AS28001: LACNIC 6 · RADB 4 · ALTDB 1

as-sets that list AS28001 (16)