Skip to main content

AS52330

52330

Autonomous System AS52330 from CO-SCSA20-LACNIC

Registry

Authoritative registration data

AS number
52330
Name
52330
Organisation
Autonomous System AS52330 from CO-SCSA20-LACNIC
Country
RIR
LACNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

12

IPv6 prefixes

1

Total announced

13

Announced prefixes

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

Prefixes announced by AS52330
168.227.104.0/24 IPv4 /24 not checked
168.227.105.0/24 IPv4 /24 not checked
168.227.106.0/24 IPv4 /24 not checked
168.227.107.0/24 IPv4 /24 not checked
190.184.200.0/24 IPv4 /24 not checked
190.184.201.0/24 IPv4 /24 not checked
190.184.202.0/24 IPv4 /24 not checked
190.184.203.0/24 IPv4 /24 not checked
190.184.204.0/24 IPv4 /24 not checked
190.184.205.0/24 IPv4 /24 not checked
190.184.206.0/24 IPv4 /24 not checked
190.184.207.0/24 IPv4 /24 not checked
2803:8340::/32 IPv6 /32 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 AS52330
Address families
NAP Colombia: Main 10,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 AS52330 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS52330 in AS paths

Observed upstreams
Families
AS7195 7195 524 3,324
v4 v6
AS18678 18678 72 488
v4 v6
AS262589 ASN262589 233 416
v4 v6
AS262191 262191 79 355
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS52330 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
AS52320 52320 1 12
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.