Skip to main content

AS328803

ORG-RWL1-AFRINIC

Radiospoor Welkom (Pty) Ltd

Registry

Authoritative registration data

AS number
328803
Name
ORG-RWL1-AFRINIC
Organisation
Radiospoor Welkom (Pty) Ltd
Country
—
RIR
AFRINIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

2

Total announced

9

Announced prefixes

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

Prefixes announced by AS328803
102.215.20.0/24 IPv4 /24 not checked
102.215.21.0/24 IPv4 /24 not checked
102.215.22.0/24 IPv4 /24 not checked
102.220.232.0/24 IPv4 /24 not checked
102.220.233.0/24 IPv4 /24 not checked
102.220.234.0/24 IPv4 /24 not checked
102.220.235.0/24 IPv4 /24 not checked
2c0f:1480:4000::/34 IPv6 /34 RPKI valid
2c0f:1480::/34 IPv6 /34 RPKI valid

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 AS328803
Address families
NAPAfrica IX Cape Town 10,000 Mbps IPv4 · IPv6
NAPAfrica IX Durban 10,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 AS328803 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS328803 in AS paths

Observed upstreams
Families
AS37100 ORG-SL75-AFRINIC 201 1,119
v4 v6
AS3741 ORG-DD1-AFRINIC 141 335
v4 v6
AS37468 ORG-AC4-AFRINIC 2 16
v4 v6
AS327782 ORG-MN2-AFRINIC 1 4
v4
AS37497 ORG-NPL3-AFRINIC 2 3
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS328803 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

12 adjacencies that may be an artefact of collector peering

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.