Skip to main content

AS328024

ORG-JMC1-AFRINIC

JACQCO MANAGEMENT CC

Registry

Authoritative registration data

AS number
328024
Name
ORG-JMC1-AFRINIC
Organisation
JACQCO MANAGEMENT CC
Country
—
RIR
AFRINIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

1

Total announced

3

Announced prefixes

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

Prefixes announced by AS328024
160.119.120.0/22 IPv4 /22 not checked
164.160.36.0/22 IPv4 /22 not checked
2c0f:f3f0::/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 AS328024
Address families
DINX: DINX Peering 20,000 Mbps IPv4 · IPv6
JINX: JINX Peering 10,000 Mbps IPv4 · IPv6
NAPAfrica IX Durban 1,000 Mbps IPv4 · IPv6
NAPAfrica IX Johannesburg: Peering 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 AS328024 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS328024 in AS paths

Observed upstreams
Families
AS37100 261 793
v4 v6
AS6939 HURRICANE 69 125
v4 v6
AS3741 47 116
v4
AS37497 1 6
v4
AS327782 ORG-MN2-AFRINIC 1 6
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS328024 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

15 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS37239 1 8
v4
AS327983 1 7
v4 v6
AS37680 1 6
v4
AS917 MISAKA 1 2
v4
AS24482 SGGS-AS-AP 1 2
v4
AS32653 1 2
v4
AS36236 NETACTUATE 1 2
v4
AS36924 1 2
v4
AS37697 1 2
v4
AS37721 ORG-VTS1-AFRINIC 1 2
v4
AS199524 GCORE 1 2
v4
AS327804 1 2
v4
AS327960 1 2
v4
AS328137 1 2
v4
AS328206 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.