Skip to main content

AS52234

52234

Autonomous System AS52234 from CL-NICH-LACNIC

Registry

Authoritative registration data

AS number
52234
Name
52234
Organisation
Autonomous System AS52234 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 AS52234
200.7.4.0/24 IPv4 /24 not checked
2001:1398:274::/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 AS52234 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS52234 in AS paths

Observed upstreams
Families
AS39839 DK-PUNKTUM 148 182
v4 v6
AS25192 CZNIC-AS 71 96
v4 v6
AS27678 27678 53 60
v4 v6
AS3132 3132 6 6
v6
AS22894 22894 4 5
v4
AS6057 6057 2 4
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS52234 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

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