bgpreport

Network · data from 2026-11-12

AS21739 MAJUBA TECHNOLOGIES

Registry name: MAJUBA TECHNOLOGIES(PTY) Limited t/a T-SOL - MAJUBA TECHNOLOGIES(PTY) Limited t/a T-SOL, ZA · PeeringDB

4IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS21739, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS21739, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
196.202.250.0/23 Valid RIR databaseAFRINIC 673 100% 66
196.202.250.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 673 100% 66
196.202.251.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 673 100% 66
196.202.248.0/23 Valid RIR databaseAFRINIC, NTTCOM 672 100% 66
2c0f:980::/32 Valid RIR databaseAFRINIC 635 100% 67

AS-SET

AS21739's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 2 are in fix.csv.

  • Route object: not announced2

Route objects not announced

Route objects with origin AS21739 whose prefix no peer sees AS21739 announce. Many are kept on purpose (backup routes, space announced only in some places).

196.202.248.0/22AFRINICValid
196.202.248.0/24AFRINICValid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.