bgpreport

Network · data from 2026-11-12

AS36999 Telecom Namibia - Telecom Namibia

Registry name: Telecom Namibia - Telecom Namibia, NA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS36999, 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.

197.188.29.0/24 Invalid: origin None 12 2%low visibility 6
197.188.30.0/24 Invalid: origin None 12 2%low visibility 6
197.188.32.0/21 Invalid: origin None 12 2%low visibility 6
197.188.40.0/21 Invalid: origin None 12 2%low visibility 6
197.188.104.0/24 Invalid: origin None 12 2%low visibility 6
197.188.105.0/24 Invalid: origin None 12 2%low visibility 6
41.190.96.0/19 No ROA Other IRR onlyRADB 673 100% 66
41.223.80.0/22 No ROA Other IRR onlyRADB, RIPE-NONAUTH 673 100% 66
197.233.0.0/16 No ROA Other IRR onlyRADB 673 100% 66

AS-SET

AS36999 isn't in PeeringDB, where networks name their 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: origin6
  • ROA: none3
  • Route object: none6
  • Route object: RIR3
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: origin197.188.29.0/24ROAs covering it name AS36996, not AS36999. If AS36999 should announce it, add a ROA for AS36999.12 of 673
Route object: none197.188.29.0/24No route object for it. Add a route object with origin AS36999 in the RIR database for the space.12 of 673
ROA: origin197.188.30.0/24ROAs covering it name AS36996, not AS36999. If AS36999 should announce it, add a ROA for AS36999.12 of 673
Route object: none197.188.30.0/24No route object for it. Add a route object with origin AS36999 in the RIR database for the space.12 of 673
ROA: origin197.188.32.0/21ROAs covering it name AS36996, not AS36999. If AS36999 should announce it, add a ROA for AS36999.12 of 673
Route object: none197.188.32.0/21No route object for it. Add a route object with origin AS36999 in the RIR database for the space.12 of 673
ROA: origin197.188.40.0/21ROAs covering it name AS36996, not AS36999. If AS36999 should announce it, add a ROA for AS36999.12 of 673
Route object: none197.188.40.0/21No route object for it. Add a route object with origin AS36999 in the RIR database for the space.12 of 673
ROA: origin197.188.104.0/24ROAs covering it name AS36996, not AS36999. If AS36999 should announce it, add a ROA for AS36999.12 of 673
Route object: none197.188.104.0/24No route object for it. Add a route object with origin AS36999 in the RIR database for the space.12 of 673
ROA: origin197.188.105.0/24ROAs covering it name AS36996, not AS36999. If AS36999 should announce it, add a ROA for AS36999.12 of 673
Route object: none197.188.105.0/24No route object for it. Add a route object with origin AS36999 in the RIR database for the space.12 of 673
ROA: none41.190.96.0/19No ROA covers it. Add a ROA for AS36999, maxLength 19.673 of 673
Route object: RIR41.190.96.0/19Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none41.223.80.0/22No ROA covers it. Add a ROA for AS36999, maxLength 22.673 of 673
Route object: RIR41.223.80.0/22Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space.673 of 673
ROA: none197.233.0.0/16No ROA covers it. Add a ROA for AS36999, maxLength 16.673 of 673
Route object: RIR197.233.0.0/16Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

41.190.96.0/21NTTCOM, RADB, RIPE-NONAUTHNo ROA
41.223.80.0/23RIPE-NONAUTHNo ROA
41.223.80.0/24NTTCOM, RADB, RIPE-NONAUTHNo ROA
41.223.82.0/23RIPE-NONAUTHNo ROA
41.223.82.0/24RIPE-NONAUTHNo ROA
41.223.83.0/24RIPE-NONAUTHNo 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.