Skip to main content

AS273847

273847

Autonomous System AS273847 from PY-PANE-LACNIC

Registry

Authoritative registration data

AS number
273847
Name
273847
Organisation
Autonomous System AS273847 from PY-PANE-LACNIC
Country
RIR
LACNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

3

Total announced

4

Announced prefixes

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

Prefixes announced by AS273847
181.41.199.0/24 IPv4 /24 not checked
2803:c550::/32 IPv6 /32 not checked
2803:c550:8000::/33 IPv6 /33 not checked
2803:c550::/33 IPv6 /33 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 AS273847 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS273847 in AS paths

Observed upstreams
Families
AS61624 ASN61624 271 982
v4 v6
AS270052 205 401
v4 v6
AS137409 GSLNETWORKS-AS-AP 2 12
v4 v6
AS6057 6057 2 8
v4 v6

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS273847 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

14 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 8
v4 v6
AS51185 MAINSTREAMING-AS 1 5
v4 v6
AS22548 1 4
v4 v6
AS35280 F5 1 4
v4 v6
AS36236 NETACTUATE 1 4
v4 v6
AS52873 ASN52873 1 4
v4 v6
AS61573 1 4
v4 v6
AS263152 1 4
v4 v6
AS263237 1 4
v4 v6
AS264479 1 4
v4 v6
AS28624 ASN28624 1 3
v6
AS28634 ASN28634 1 2
v4
AS271253 ASN271253 1 2
v4
AS262427 ASN262427 1 1
v4

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.