Skip to main content

AS21575

21575

Autonomous System AS21575 from PE-MPSA3-LACNIC

Registry

Authoritative registration data

AS number
21575
Name
21575
Organisation
Autonomous System AS21575 from PE-MPSA3-LACNIC
Country
—
RIR
LACNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

62

IPv6 prefixes

4

Total announced

66

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS21575
186.160.0.0/14 IPv4 /14 RPKI valid
132.157.0.0/16 IPv4 /16 not checked
132.184.0.0/16 IPv4 /16 RPKI valid
132.191.0.0/16 IPv4 /16 RPKI valid
132.251.0.0/17 IPv4 /17 not checked
132.251.128.0/18 IPv4 /18 RPKI valid
132.251.192.0/19 IPv4 /19 RPKI valid
132.157.128.0/22 IPv4 /22 not checked
132.157.64.0/22 IPv4 /22 not checked
132.184.128.0/22 IPv4 /22 RPKI valid
132.184.64.0/22 IPv4 /22 RPKI valid
132.191.0.0/22 IPv4 /22 not checked
132.191.8.0/22 IPv4 /22 not checked
132.251.0.0/22 IPv4 /22 RPKI valid
132.251.8.0/22 IPv4 /22 RPKI valid
148.102.112.0/22 IPv4 /22 RPKI valid
186.160.224.0/22 IPv4 /22 RPKI valid
186.163.8.0/22 IPv4 /22 RPKI valid
200.110.0.0/22 IPv4 /22 not checked
132.157.154.0/23 IPv4 /23 RPKI valid
132.157.66.0/23 IPv4 /23 not checked
132.184.178.0/23 IPv4 /23 not checked
132.184.66.0/23 IPv4 /23 RPKI valid
132.191.10.0/23 IPv4 /23 not checked
132.191.130.0/23 IPv4 /23 not checked
132.251.10.0/23 IPv4 /23 RPKI valid
132.251.2.0/23 IPv4 /23 not checked
132.251.96.0/23 IPv4 /23 RPKI valid
148.102.112.0/23 IPv4 /23 RPKI valid
148.102.114.0/23 IPv4 /23 RPKI valid
186.160.208.0/23 IPv4 /23 not checked
186.160.222.0/23 IPv4 /23 not checked
186.160.224.0/23 IPv4 /23 not checked
186.160.226.0/23 IPv4 /23 not checked
186.163.10.0/23 IPv4 /23 RPKI valid
200.110.38.0/23 IPv4 /23 RPKI valid
132.251.0.0/24 IPv4 /24 RPKI valid
148.102.0.0/24 IPv4 /24 not checked
148.102.1.0/24 IPv4 /24 not checked
148.102.116.0/24 IPv4 /24 not checked
148.102.82.0/24 IPv4 /24 not checked
148.102.83.0/24 IPv4 /24 RPKI valid
186.160.223.0/24 IPv4 /24 not checked
186.160.226.0/24 IPv4 /24 RPKI valid
186.160.39.0/24 IPv4 /24 RPKI valid
186.163.20.0/24 IPv4 /24 RPKI valid
190.8.150.0/24 IPv4 /24 not checked
190.8.151.0/24 IPv4 /24 RPKI valid
190.8.154.0/24 IPv4 /24 RPKI valid
190.8.156.0/24 IPv4 /24 not checked
190.8.157.0/24 IPv4 /24 RPKI valid
190.8.158.0/24 IPv4 /24 RPKI valid
190.8.159.0/24 IPv4 /24 RPKI valid
200.110.24.0/24 IPv4 /24 not checked
200.192.105.0/24 IPv4 /24 not checked
201.131.121.0/24 IPv4 /24 RPKI valid
204.87.205.0/24 IPv4 /24 RPKI valid
207.248.121.0/24 IPv4 /24 RPKI valid
207.248.123.0/24 IPv4 /24 not checked
38.211.101.0/24 IPv4 /24 not checked
38.56.205.0/24 IPv4 /24 not checked
38.9.50.0/24 IPv4 /24 not checked
2803:7180:2000::/36 IPv6 /36 RPKI valid
2803:7180:4000::/36 IPv6 /36 RPKI valid
2803:7180:6000::/36 IPv6 /36 RPKI valid
2803:7180:7000::/36 IPv6 /36 RPKI valid

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS21575
Address families
PIT - Peru - Lima: Main 200,000 Mbps IPv4 · IPv6
PIT Santiago - PIT Chile: LAN 200,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS21575 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS21575 in AS paths

Observed upstreams
Families
AS12956 TELXIUS 1,101 9,635
v4 v6
AS3356 LEVEL3 1,632 8,087
v4 v6
AS6762 SEABONE-NET 979 5,778
v4 v6
AS6057 6057 40 698
v4 v6
AS6939 HURRICANE 49 580
v4
AS7195 7195 10 327
v4 v6
AS263229 263229 4 160
v4 v6
AS263702 263702 15 25
v6

No rows match “”.

Showing – of

Observed downstreams

18 networks seen after AS21575 in AS paths

Observed downstreams
Families
AS19180 19180 171 6,995
v4
AS272894 272894 408 2,787
v4 v6
AS270006 270006 548 1,564
v4
AS272059 272059 349 976
v4 v6
AS272838 272838 371 827
v4 v6
AS273192 273192 325 660
v4 v6
AS269803 269803 151 504
v4
AS273084 273084 267 437
v4 v6
AS27809 27809 155 171
v4
AS32034 NEWCOM-INTL 144 167
v4
AS273108 273108 62 136
v4
AS273211 273211 73 89
v6
AS263185 263185 31 84
v4
AS55195 CIRA-CLOUD1 3 54
v6
AS61482 61482 6 24
v4
AS273976 273976 6 18
v4
AS7195 7195 2 3
v6
AS273107 273107 2 2
v6

No rows match “”.

Showing – of

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 5 205
v4 v6
AS269956 269956 5 205
v4 v6
AS270014 270014 5 205
v4 v6

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.