Skip to main content

AS272059

272059

Autonomous System AS272059 from PE-CHCU2-LACNIC

Registry

Authoritative registration data

AS number
272059
Name
272059
Organisation
Autonomous System AS272059 from PE-CHCU2-LACNIC
Country
RIR
LACNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

2

Total announced

6

Announced prefixes

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

Prefixes announced by AS272059
181.174.224.0/22 IPv4 /22 not checked
181.174.224.0/23 IPv4 /23 not checked
181.174.226.0/23 IPv4 /23 not checked
181.174.227.0/24 IPv4 /24 not checked
2803:8310::/32 IPv6 /32 not checked
2803:8310::/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 AS272059
Address families
PIT - Peru - Lima: Main 10,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 AS272059 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS272059 in AS paths

Observed upstreams
Families
AS21575 671 2,007
v4 v6
AS6057 6057 2 14
v4 v6
AS7195 7195 3 11
v4 v6

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS272059 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS263702 263702 1 3
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.