bgpreport

Network · data from 2026-11-12

AS36986 Africom

Registry name: Africom Pvt Ltd - Africom Pvt Ltd, ZW · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS36986, 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.
41.57.64.0/23 No ROA RIR databaseAFRINIC 673 100% 67
41.57.66.0/23 No ROA RIR databaseAFRINIC 673 100% 67
41.57.68.0/24 No ROA RIR databaseAFRINIC 673 100% 67
41.221.144.0/24 No ROA RIR databaseAFRINIC 673 100% 67
41.221.146.0/24 No ROA RIR databaseAFRINIC 673 100% 67
41.221.147.0/24 No ROA RIR databaseAFRINIC 673 100% 67
41.221.148.0/24 No ROA RIR databaseAFRINIC 673 100% 67
41.221.150.0/23 No ROA RIR databaseAFRINIC, RIPE-NONAUTH 673 100% 67
41.221.152.0/23 No ROA RIR databaseAFRINIC, RIPE-NONAUTH 673 100% 67
41.221.154.0/23 No ROA RIR databaseAFRINIC, RIPE-NONAUTH 673 100% 67
41.221.156.0/23 No ROA RIR databaseAFRINIC, RIPE-NONAUTH 673 100% 67
41.221.158.0/23 No ROA RIR databaseAFRINIC, RIPE-NONAUTH 673 100% 67

AS-SET

AS36986'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: none12
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none41.57.64.0/23No ROA covers it. Add a ROA for AS36986, maxLength 23.673 of 673
ROA: none41.57.66.0/23No ROA covers it. Add a ROA for AS36986, maxLength 23.673 of 673
ROA: none41.57.68.0/24No ROA covers it. Add a ROA for AS36986, maxLength 24.673 of 673
ROA: none41.221.144.0/24No ROA covers it. Add a ROA for AS36986, maxLength 24.673 of 673
ROA: none41.221.146.0/24No ROA covers it. Add a ROA for AS36986, maxLength 24.673 of 673
ROA: none41.221.147.0/24No ROA covers it. Add a ROA for AS36986, maxLength 24.673 of 673
ROA: none41.221.148.0/24No ROA covers it. Add a ROA for AS36986, maxLength 24.673 of 673
ROA: none41.221.150.0/23No ROA covers it. Add a ROA for AS36986, maxLength 23.673 of 673
ROA: none41.221.152.0/23No ROA covers it. Add a ROA for AS36986, maxLength 23.673 of 673
ROA: none41.221.154.0/23No ROA covers it. Add a ROA for AS36986, maxLength 23.673 of 673
ROA: none41.221.156.0/23No ROA covers it. Add a ROA for AS36986, maxLength 23.673 of 673
ROA: none41.221.158.0/23No ROA covers it. Add a ROA for AS36986, maxLength 23.673 of 673

Route objects not announced

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

41.57.64.0/20AFRINIC, RIPE-NONAUTHNo ROA
41.57.69.0/24AFRINICNo ROA
41.57.70.0/23AFRINICNo ROA
41.57.72.0/23AFRINICNo ROA
41.57.74.0/23AFRINICNo ROA
41.221.144.0/20AFRINIC, RIPE-NONAUTHNo ROA
41.221.145.0/24AFRINICNo ROA
41.221.146.0/23RIPE-NONAUTHNo ROA
41.221.148.0/23RIPE-NONAUTHNo ROA
41.221.149.0/24AFRINICNo ROA
41.221.152.0/22RIPE-NONAUTHNo ROA
41.221.156.0/22RIPE-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.