Skip to main content

AS272021

272021

Autonomous System AS272021 from PY-ITBI1-LACNIC

Registry

Authoritative registration data

AS number
272021
Name
272021
Organisation
Autonomous System AS272021 from PY-ITBI1-LACNIC
Country
—
RIR
LACNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

3

Total announced

10

Announced prefixes

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

Prefixes announced by AS272021
179.63.8.0/22 IPv4 /22 not checked
179.63.10.0/23 IPv4 /23 RPKI valid
179.63.8.0/23 IPv4 /23 not checked
179.63.10.0/24 IPv4 /24 not checked
179.63.11.0/24 IPv4 /24 RPKI valid
179.63.8.0/24 IPv4 /24 RPKI valid
179.63.9.0/24 IPv4 /24 RPKI valid
2801:1a1::/44 IPv6 /44 not checked
2801:1a1:8::/46 IPv6 /46 RPKI valid
2801:1a1:c::/46 IPv6 /46 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 AS272021
Address families
IX.br (PTT.br) Foz do Iguaçu: ATM/MLPA 10,000 Mbps IPv4 · IPv6
IX.br (PTT.br) São Paulo: ATM/MPLA 1,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 AS272021 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS272021 in AS paths

Observed upstreams
Families
AS3356 LEVEL3 313 951
v4 v6
AS27895 27895 367 708
v4 v6
AS28103 28103 388 686
v4
AS53062 ASN53062 151 649
v4 v6
AS6939 HURRICANE 97 271
v4 v6
AS6057 6057 2 16
v4 v6
AS137409 GSLNETWORKS-AS-AP 4 10
v4
AS61626 ASN61626 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS272021 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

18 adjacencies that may be an artefact of collector peering

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.