Skip to main content

AS273211

273211

Autonomous System AS273211 from PE-IASA10-LACNIC

Registry

Authoritative registration data

AS number
273211
Name
273211
Organisation
Autonomous System AS273211 from PE-IASA10-LACNIC
Country
—
RIR
LACNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

0

Total announced

1

Announced prefixes

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

Prefixes announced by AS273211
45.68.58.0/24 IPv4 /24 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 AS273211
Address families
IX ANDESPARK SAC 10,000 Mbps IPv4 · IPv6
JumboIX Peru 10,000 Mbps IPv4 · IPv6
PIT - Peru - Lima: Main 100,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 AS273211 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS273211 in AS paths

Observed upstreams
Families
AS3356 LEVEL3 801 1,485
v4 v6
AS21575 21575 132 184
v6
AS6057 6057 6 10
v4 v6
AS7195 7195 4 6
v4 v6
AS273882 2 2
v6

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS273211 in AS paths

Observed downstreams
Families
AS271900 694 1,351
v4 v6
AS273906 1 1
v6

No rows match “”.

Showing – of

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.