Skip to main content

AS272026

272026

Autonomous System AS272026 from PY-HSTE-LACNIC

Registry

Authoritative registration data

AS number
272026
Name
272026
Organisation
Autonomous System AS272026 from PY-HSTE-LACNIC
Country
—
RIR
LACNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

6

IPv6 prefixes

1

Total announced

7

Announced prefixes

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

Prefixes announced by AS272026
190.93.184.0/22 IPv4 /22 not checked
167.250.236.0/23 IPv4 /23 not checked
177.11.254.0/23 IPv4 /23 not checked
190.93.184.0/23 IPv4 /23 not checked
190.93.186.0/24 IPv4 /24 not checked
190.93.187.0/24 IPv4 /24 not checked
2803:6510::/32 IPv6 /32 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 AS272026
Address families
IX.br (PTT.br) São Paulo: ATM/MPLA 10,000 Mbps IPv4 · IPv6
IXpy: ISPs 10,000 Mbps IPv4 · IPv6
PIT Paraguay 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 AS272026 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS272026 in AS paths

Observed upstreams
Families
AS270052 270052 384 1,249
v4 v6
AS61624 ASN61624 363 1,208
v4 v6
AS137409 GSLNETWORKS-AS-AP 2 3
v6
AS6057 6057 2 2
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS272026 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

12 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.