Skip to main content

AS273026

273026

Autonomous System AS273026 from PE-NESA22-LACNIC

Registry

Authoritative registration data

AS number
273026
Name
273026
Organisation
Autonomous System AS273026 from PE-NESA22-LACNIC
Country
RIR
LACNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

3

Total announced

5

Announced prefixes

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

Prefixes announced by AS273026
38.52.182.0/23 IPv4 /23 not checked
177.221.147.0/24 IPv4 /24 not checked
2803:b390::/32 IPv6 /32 not checked
2803:b390:100::/40 IPv6 /40 not checked
2803:b390:100::/44 IPv6 /44 not checked

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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 AS273026 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS273026 in AS paths

Observed upstreams
Families
AS273067 500 957
v4 v6
AS273976 20 56
v4
AS6057 6057 2 6
v4 v6
AS7195 7195 2 2
v6

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS273026 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 1
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.