Skip to main content

AS52305

52305

Autonomous System AS52305 from CL-NICH-LACNIC

Registry

Authoritative registration data

AS number
52305
Name
52305
Organisation
Autonomous System AS52305 from CL-NICH-LACNIC
Country
—
RIR
LACNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

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

Prefixes announced by AS52305
200.7.5.0/24 IPv4 /24 not checked
2001:1398:276::/48 IPv6 /48 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 AS52305 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS52305 in AS paths

Observed upstreams
Families
AS36236 NETACTUATE 334 526
v4 v6
AS27678 27678 88 120
v4 v6
AS22860 16 30
v4 v6
AS6057 6057 2 4
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS52305 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 1 2
v4 v6
AS269956 1 2
v4 v6
AS270014 1 2
v4 v6
AS51185 MAINSTREAMING-AS 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.