ResearchRouting table, RPKI, IRR & looking glass

AS3132 Red Cientifica Peruana

AS3132 (AS3132) is registered to Red Cientifica Peruana in PE, through LACNIC. It originates 118 prefixes in the global routing table.

115
IPv4 prefixes
3
IPv6 prefixes
103,936
IPv4 addresses
2%
RPKI valid

Who holds AS3132

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

AS number
AS3132
Handle
AS3132
Organization
Red Cientifica Peruana
Country
PE
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:37:57 (Z Z)

aut-num:     AS3132
owner:       Red Cientifica Peruana
ownerid:     PE-RCPE4-LACNIC
responsible: Ruben Rodriguez
address:     Jiron Gonzales Prada, 585, 
address:     L27 - Lima - 
country:     PE
phone:       +51 1 7020138
owner-c:     RUR4
routing-c:   RUR4
abuse-c:     RUR4
created:     19931119
changed:     20130910

nic-hdl:     RUR4
person:      Ruben Rodriguez
e-mail:      rubenrodriguezsolorzano@gmail.com
address:     Av. La Paz 1049, 585, -
address:     15074 - Lima, Miraflores - Lima
country:     PE
phone:       +51  17020138 [0000]
created:     20090722
changed:     20260811

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

What AS3132 announces

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

IPv4 prefixes
115
IPv6 prefixes
3
IPv4 addresses
103,936 (406 /24s)
RPKI valid
3 2%
RPKI invalid
0
RPKI not found
115
ROAs naming AS3132
6
With an IRR route object
18 15%

Announced prefixes

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

IPv4 (115)
38.41.186.0/2438.52.202.0/2438.56.109.0/2438.87.224.0/2438.250.114.0/2438.250.116.0/2438.250.136.0/2438.250.161.0/2438.250.162.0/2438.250.163.0/2438.250.168.0/2438.250.169.0/2438.250.170.0/2438.250.173.0/2438.250.174.0/2438.250.175.0/24149.34.48.0/24149.34.49.0/24149.34.50.0/24149.34.51.0/24161.132.0.0/16161.132.1.0/24161.132.2.0/24161.132.4.0/24161.132.5.0/24161.132.7.0/24161.132.8.0/24161.132.11.0/24161.132.12.0/24161.132.14.0/24161.132.15.0/24161.132.17.0/24161.132.18.0/24161.132.19.0/24161.132.20.0/24161.132.21.0/24161.132.32.0/24161.132.34.0/24161.132.35.0/24161.132.36.0/24161.132.37.0/24161.132.38.0/24161.132.39.0/24161.132.40.0/24161.132.41.0/24161.132.42.0/24161.132.43.0/24161.132.44.0/24161.132.45.0/24161.132.46.0/24161.132.47.0/24161.132.48.0/24161.132.49.0/24161.132.50.0/24161.132.51.0/24161.132.52.0/24161.132.53.0/24161.132.54.0/24161.132.55.0/24161.132.56.0/24161.132.57.0/24161.132.58.0/24161.132.61.0/24161.132.64.0/24161.132.65.0/24161.132.67.0/24161.132.68.0/24161.132.77.0/24161.132.81.0/24161.132.170.0/24161.132.187.0/24161.132.250.0/24161.132.253.0/24200.1.176.0/24200.1.178.0/24209.45.0.0/17209.45.3.0/24209.45.4.0/24209.45.16.0/24209.45.17.0/24209.45.28.0/24209.45.29.0/24209.45.30.0/24209.45.31.0/24209.45.32.0/24209.45.38.0/24209.45.39.0/24209.45.40.0/24209.45.41.0/24209.45.42.0/24209.45.44.0/24209.45.45.0/24209.45.46.0/24209.45.59.0/24209.45.64.0/24209.45.65.0/24209.45.66.0/24209.45.67.0/24209.45.68.0/24209.45.69.0/24209.45.73.0/24209.45.74.0/24209.45.75.0/24209.45.84.0/24209.45.85.0/24209.45.86.0/24209.45.87.0/24209.45.96.0/24209.45.100.0/24209.45.101.0/24209.45.106.0/24209.45.109.0/24209.45.110.0/24209.45.112.0/24209.45.127.0/24
IPv6 (3)

RPKI valid   RPKI invalid   no ROA covers it

Who AS3132 is reached through

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