Skip to main content

AS21739

ORG-TA22-AFRINIC

MAJUBA TECHNOLOGIES(PTY) Limited t/a T-SOL

Registry

Authoritative registration data

AS number
21739
Name
ORG-TA22-AFRINIC
Organisation
MAJUBA TECHNOLOGIES(PTY) Limited t/a T-SOL
Country
—
RIR
AFRINIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

1

Total announced

5

Announced prefixes

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

Prefixes announced by AS21739
196.202.248.0/23 IPv4 /23 not checked
196.202.250.0/23 IPv4 /23 not checked
196.202.250.0/24 IPv4 /24 not checked
196.202.251.0/24 IPv4 /24 not checked
2c0f:980::/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 AS21739
Address families
NAPAfrica IX Johannesburg: Peering 1,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 AS21739 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS21739 in AS paths

Observed upstreams
Families
AS32437 ORG-WCTC1-AFRINIC 381 1,169
v4
AS37100 ORG-SL75-AFRINIC 312 560
v4 v6
AS37468 ORG-AC4-AFRINIC 2 5
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS21739 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

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.