Skip to main content

AS329654

ORG-CSL6-AFRINIC

Cortech Systems Limited

Registry

Authoritative registration data

AS number
329654
Name
ORG-CSL6-AFRINIC
Organisation
Cortech Systems Limited
Country
—
RIR
AFRINIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

0

Total announced

3

Announced prefixes

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

Prefixes announced by AS329654
102.204.12.0/23 IPv4 /23 not checked
102.204.12.0/24 IPv4 /24 not checked
102.204.13.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 AS329654
Address families
KIXP - Nairobi: Peering LAN 10,000 Mbps IPv4 · IPv6
LINX Nairobi 10,000 Mbps IPv4

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 AS329654 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS329654 in AS paths

Observed upstreams
Families
AS9129 ORG-VSA1-AFRINIC 251 318
v4
AS6939 HURRICANE 44 98
v4
AS58453 CMI-INT-HK 1 2
v4
AS60171 AFRIX-AS 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS329654 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS36236 NETACTUATE 1 2
v4
AS328977 ORG-WISP2-AFRINIC 1 2
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.