Skip to main content

AS272022

272022

Autonomous System AS272022 from CL-ZASP-LACNIC

Registry

Authoritative registration data

AS number
272022
Name
272022
Organisation
Autonomous System AS272022 from CL-ZASP-LACNIC
Country
RIR
LACNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

6

Total announced

13

Announced prefixes

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

Prefixes announced by AS272022
149.78.188.0/23 IPv4 /23 not checked
149.78.188.0/24 IPv4 /24 not checked
149.78.189.0/24 IPv4 /24 not checked
149.78.191.0/24 IPv4 /24 not checked
201.234.118.0/24 IPv4 /24 not checked
38.250.4.0/24 IPv4 /24 not checked
38.250.5.0/24 IPv4 /24 not checked
2801:161:1::/48 IPv6 /48 not checked
2801:161:3::/48 IPv6 /48 not checked
2801:161:4::/48 IPv6 /48 not checked
2801:161:7::/48 IPv6 /48 not checked
2801:161:8::/48 IPv6 /48 not checked
2801:161::/48 IPv6 /48 not checked

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 AS272022
Address families
NAP.EC - GYE 100,000 Mbps IPv4 · IPv6
NAP.EC - UIO 100,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 AS272022 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS272022 in AS paths

Observed upstreams
Families
AS3356 LEVEL3 357 1,330
v4 v6
AS3549 352 992
v4 v6
AS14522 488 666
v4
AS263702 263702 257 658
v4
AS28663 ASN28663 270 366
v4 v6
AS12956 TELXIUS 218 293
v6
AS22356 15 19
v4
AS6057 6057 2 8
v4 v6
AS7195 7195 3 5
v4 v6

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS272022 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS36236 NETACTUATE 1 4
v4 v6
AS49544 i3Dnet 1 4
v4 v6
AS269956 1 4
v4 v6
AS270014 1 4
v4 v6
AS51185 MAINSTREAMING-AS 1 2
v4

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.