Skip to main content

AS328391

ORG-RCP1-AFRINIC

Rocking Connect PTY (LTD)

Registry

Authoritative registration data

AS number
328391
Name
ORG-RCP1-AFRINIC
Organisation
Rocking Connect PTY (LTD)
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 AS328391
102.130.236.0/22 IPv4 /22 not checked
102.130.236.0/24 IPv4 /24 not checked
2c0f:ec18::/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 AS328391
Address families
NAPAfrica IX Cape Town 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 AS328391 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS328391 in AS paths

Observed upstreams
Families
AS37271 323 800
v4 v6
AS32437 ORG-WCTC1-AFRINIC 201 259
v4
AS37468 ORG-AC4-AFRINIC 2 2
v6
AS37497 ORG-NPL3-AFRINIC 2 2
v4 v6

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS328391 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
AS37239 1 3
v4 v6
AS37721 ORG-VTS1-AFRINIC 1 2
v6
AS37680 1 1
v6
AS327983 1 1
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.