bgpreport

Network · data from 2026-11-12

AS328486 Old Mutual Life Assurance Company (South Africa) Limited

Registry name: Old Mutual Life Assurance Company (South Africa) Limited - Old Mutual Life Assurance Company (South Africa) Limited, ZA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS328486, 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.
160.123.196.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 70
160.123.197.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 70
160.123.238.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 70
160.123.239.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 70
160.123.255.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 70
160.123.198.0/24 No ROA Other IRR onlyNTTCOM, RADB 670 100% 67
160.123.240.0/24 No ROA Other IRR onlyNTTCOM, RADB 670 100% 67
160.123.241.0/24 No ROA Other IRR onlyNTTCOM, RADB 670 100% 67
160.123.236.0/23 No ROA Other IRR onlyNTTCOM, RADB 41 6%low visibility 18
160.123.236.0/24 No ROA Other IRR onlyNTTCOM, RADB 41 6%low visibility 18
160.123.237.0/24 No ROA Other IRR onlyNTTCOM, RADB 41 6%low visibility 18

AS-SET

AS328486'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 24 are in fix.csv.

  • ROA: none11
  • Route object: RIR11
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none160.123.196.0/24No ROA covers it. Add a ROA for AS328486, maxLength 24.673 of 673
Route object: RIR160.123.196.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none160.123.197.0/24No ROA covers it. Add a ROA for AS328486, maxLength 24.673 of 673
Route object: RIR160.123.197.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none160.123.238.0/24No ROA covers it. Add a ROA for AS328486, maxLength 24.673 of 673
Route object: RIR160.123.238.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none160.123.239.0/24No ROA covers it. Add a ROA for AS328486, maxLength 24.673 of 673
Route object: RIR160.123.239.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none160.123.255.0/24No ROA covers it. Add a ROA for AS328486, maxLength 24.673 of 673
Route object: RIR160.123.255.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none160.123.198.0/24No ROA covers it. Add a ROA for AS328486, maxLength 24.670 of 673
Route object: RIR160.123.198.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
ROA: none160.123.240.0/24No ROA covers it. Add a ROA for AS328486, maxLength 24.670 of 673
Route object: RIR160.123.240.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
ROA: none160.123.241.0/24No ROA covers it. Add a ROA for AS328486, maxLength 24.670 of 673
Route object: RIR160.123.241.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
ROA: none160.123.236.0/23No ROA covers it. Add a ROA for AS328486, maxLength 23.41 of 673
Route object: RIR160.123.236.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.41 of 673
ROA: none160.123.236.0/24No ROA covers it. Add a ROA for AS328486, maxLength 24.41 of 673
Route object: RIR160.123.236.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.41 of 673
ROA: none160.123.237.0/24No ROA covers it. Add a ROA for AS328486, maxLength 24.41 of 673
Route object: RIR160.123.237.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.41 of 673

Route objects not announced

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

160.123.0.0/16NTTCOM, RADBNo ROA
160.123.196.0/23NTTCOM, RADBNo ROA

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.