bgpreport

Network · data from 2026-11-12

AS36913 TELEKOM NETWORKS MALAWI LTD - TELEKOM NETWORKS MALAWI LTD

Registry name: TELEKOM NETWORKS MALAWI LTD - TELEKOM NETWORKS MALAWI LTD, MW · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS36913, 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.222.184.0/23 Valid Nonecovered by 41.222.184.0/22 673 100% 67
41.222.186.0/23 Valid Nonecovered by 41.222.184.0/22 673 100% 67
168.253.224.0/24 Valid Nonecovered by 168.253.224.0/20 673 100% 67
102.70.86.0/24 Valid Other origin onlycovered by 102.70.0.0/15 671 100% 68
2c0f:fac0:1::/48 Valid Nonecovered by 2c0f:fac0::/32 636 100% 67
2c0f:fac0:2::/48 Valid Nonecovered by 2c0f:fac0::/32 636 100% 67
2c0f:fac0:3::/48 Valid Nonecovered by 2c0f:fac0::/32 636 100% 67
2c0f:fac0:4::/48 Valid Nonecovered by 2c0f:fac0::/32 636 100% 67
41.222.184.0/22 Valid Other IRR onlyRIPE-NONAUTH 673 100% 67
41.222.184.0/24 Valid Other IRR onlyRIPE-NONAUTH 673 100% 67
41.222.185.0/24 Valid Other IRR onlyRIPE-NONAUTH 673 100% 67
41.222.188.0/22 Valid Other IRR onlyRIPE-NONAUTH 673 100% 67
41.222.188.0/24 Valid Other IRR onlyRIPE-NONAUTH 673 100% 67
41.222.189.0/24 Valid Other IRR onlyRIPE-NONAUTH 673 100% 67
41.222.190.0/24 Valid Other IRR onlyRIPE-NONAUTH 673 100% 67
41.222.191.0/24 Valid Other IRR onlyRIPE-NONAUTH 673 100% 67
168.253.240.0/20 Valid Other IRR onlyRIPE-NONAUTH 673 100% 67
41.222.187.0/24 Valid Other IRR onlyRIPE-NONAUTH 239 36% 54
41.222.186.0/24 Valid Other IRR onlyRIPE-NONAUTH 234 35% 53
168.253.245.0/24 Valid RIR databaseAFRINIC 673 100% 67
168.253.248.0/24 Valid RIR databaseAFRINIC 673 100% 67
196.216.8.0/23 Valid RIR databaseAFRINIC 673 100% 67
196.216.8.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 673 100% 67
196.216.9.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 673 100% 67
196.216.10.0/23 Valid RIR databaseAFRINIC 673 100% 67
196.216.10.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 673 100% 67
196.216.11.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 673 100% 67
196.216.12.0/22 Valid RIR databaseAFRINIC, RIPE-NONAUTH 673 100% 67
196.216.12.0/23 Valid RIR databaseAFRINIC 673 100% 67
196.216.12.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 673 100% 67
196.216.13.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 673 100% 67
196.216.14.0/23 Valid RIR databaseAFRINIC 673 100% 67
196.216.14.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 673 100% 67
196.216.15.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 673 100% 67
196.216.8.0/22 Valid RIR databaseAFRINIC, RIPE-NONAUTH 218 32% 53

AS-SET

AS36913 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 28 are in fix.csv.

  • Route object: none8
  • Route object: RIR11
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
Route object: none41.222.184.0/23No route object for it. A route object for 41.222.184.0/22 with origin AS36913 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36913 in the RIR database for the space.673 of 673
Route object: none41.222.186.0/23No route object for it. A route object for 41.222.184.0/22 with origin AS36913 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36913 in the RIR database for the space.673 of 673
Route object: none168.253.224.0/24No route object for it. A route object for 168.253.224.0/20 with origin AS36913 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36913 in the RIR database for the space.673 of 673
Route object: none102.70.86.0/24Route objects for it name AS37294. A route object for 102.70.0.0/15 with origin AS36913 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36913 in the RIR database for the space.671 of 673
Route object: none2c0f:fac0:1::/48No route object for it. A route object for 2c0f:fac0::/32 with origin AS36913 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36913 in the RIR database for the space.636 of 636
Route object: none2c0f:fac0:2::/48No route object for it. A route object for 2c0f:fac0::/32 with origin AS36913 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36913 in the RIR database for the space.636 of 636
Route object: none2c0f:fac0:3::/48No route object for it. A route object for 2c0f:fac0::/32 with origin AS36913 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36913 in the RIR database for the space.636 of 636
Route object: none2c0f:fac0:4::/48No route object for it. A route object for 2c0f:fac0::/32 with origin AS36913 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36913 in the RIR database for the space.636 of 636
Route object: RIR41.222.184.0/22Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.673 of 673
Route object: RIR41.222.184.0/24Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.673 of 673
Route object: RIR41.222.185.0/24Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.673 of 673
Route object: RIR41.222.188.0/22Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.673 of 673
Route object: RIR41.222.188.0/24Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.673 of 673
Route object: RIR41.222.189.0/24Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.673 of 673
Route object: RIR41.222.190.0/24Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.673 of 673
Route object: RIR41.222.191.0/24Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.673 of 673
Route object: RIR168.253.240.0/20Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.673 of 673
Route object: RIR41.222.187.0/24Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.239 of 673
Route object: RIR41.222.186.0/24Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.234 of 673

Route objects not announced

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

41.222.184.0/21RIPE-NONAUTHValid
102.70.0.0/15RADBValid
168.253.224.0/19RIPE-NONAUTHValid
168.253.224.0/20RIPE-NONAUTHValid
168.253.240.0/24AFRINICValid
168.253.248.0/22RIPE-NONAUTHValid
168.253.255.0/24AFRINICValid
196.216.8.0/21RIPE-NONAUTHValid
2c0f:fac0::/32RIPE-NONAUTHValid

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.