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
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% |
| 41.222.186.0/23 | Valid | Nonecovered by 41.222.184.0/22 | 673 100% |
| 168.253.224.0/24 | Valid | Nonecovered by 168.253.224.0/20 | 673 100% |
| 102.70.86.0/24 | Valid | Other origin onlycovered by 102.70.0.0/15 | 671 100% |
| 2c0f:fac0:1::/48 | Valid | Nonecovered by 2c0f:fac0::/32 | 636 100% |
| 2c0f:fac0:2::/48 | Valid | Nonecovered by 2c0f:fac0::/32 | 636 100% |
| 2c0f:fac0:3::/48 | Valid | Nonecovered by 2c0f:fac0::/32 | 636 100% |
| 2c0f:fac0:4::/48 | Valid | Nonecovered by 2c0f:fac0::/32 | 636 100% |
| 41.222.184.0/22 | Valid | Other IRR onlyRIPE-NONAUTH | 673 100% |
| 41.222.184.0/24 | Valid | Other IRR onlyRIPE-NONAUTH | 673 100% |
| 41.222.185.0/24 | Valid | Other IRR onlyRIPE-NONAUTH | 673 100% |
| 41.222.188.0/22 | Valid | Other IRR onlyRIPE-NONAUTH | 673 100% |
| 41.222.188.0/24 | Valid | Other IRR onlyRIPE-NONAUTH | 673 100% |
| 41.222.189.0/24 | Valid | Other IRR onlyRIPE-NONAUTH | 673 100% |
| 41.222.190.0/24 | Valid | Other IRR onlyRIPE-NONAUTH | 673 100% |
| 41.222.191.0/24 | Valid | Other IRR onlyRIPE-NONAUTH | 673 100% |
| 168.253.240.0/20 | Valid | Other IRR onlyRIPE-NONAUTH | 673 100% |
| 41.222.187.0/24 | Valid | Other IRR onlyRIPE-NONAUTH | 239 36% |
| 41.222.186.0/24 | Valid | Other IRR onlyRIPE-NONAUTH | 234 35% |
| 168.253.245.0/24 | Valid | RIR databaseAFRINIC | 673 100% |
| 168.253.248.0/24 | Valid | RIR databaseAFRINIC | 673 100% |
| 196.216.8.0/23 | Valid | RIR databaseAFRINIC | 673 100% |
| 196.216.8.0/24 | Valid | RIR databaseAFRINIC, RIPE-NONAUTH | 673 100% |
| 196.216.9.0/24 | Valid | RIR databaseAFRINIC, RIPE-NONAUTH | 673 100% |
| 196.216.10.0/23 | Valid | RIR databaseAFRINIC | 673 100% |
| 196.216.10.0/24 | Valid | RIR databaseAFRINIC, RIPE-NONAUTH | 673 100% |
| 196.216.11.0/24 | Valid | RIR databaseAFRINIC, RIPE-NONAUTH | 673 100% |
| 196.216.12.0/22 | Valid | RIR databaseAFRINIC, RIPE-NONAUTH | 673 100% |
| 196.216.12.0/23 | Valid | RIR databaseAFRINIC | 673 100% |
| 196.216.12.0/24 | Valid | RIR databaseAFRINIC, RIPE-NONAUTH | 673 100% |
| 196.216.13.0/24 | Valid | RIR databaseAFRINIC, RIPE-NONAUTH | 673 100% |
| 196.216.14.0/23 | Valid | RIR databaseAFRINIC | 673 100% |
| 196.216.14.0/24 | Valid | RIR databaseAFRINIC, RIPE-NONAUTH | 673 100% |
| 196.216.15.0/24 | Valid | RIR databaseAFRINIC, RIPE-NONAUTH | 673 100% |
| 196.216.8.0/22 | Valid | RIR databaseAFRINIC, RIPE-NONAUTH | 218 32% |
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
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 41.222.184.0/23 | No 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. |
| Route object: none | 41.222.186.0/23 | No 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. |
| Route object: none | 168.253.224.0/24 | No 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. |
| Route object: none | 102.70.86.0/24 | Route 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. |
| Route object: none | 2c0f:fac0:1::/48 | No 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. |
| Route object: none | 2c0f:fac0:2::/48 | No 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. |
| Route object: none | 2c0f:fac0:3::/48 | No 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. |
| Route object: none | 2c0f:fac0:4::/48 | No 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. |
| Route object: RIR | 41.222.184.0/22 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
| Route object: RIR | 41.222.184.0/24 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
| Route object: RIR | 41.222.185.0/24 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
| Route object: RIR | 41.222.188.0/22 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
| Route object: RIR | 41.222.188.0/24 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
| Route object: RIR | 41.222.189.0/24 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
| Route object: RIR | 41.222.190.0/24 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
| Route object: RIR | 41.222.191.0/24 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
| Route object: RIR | 168.253.240.0/20 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
| Route object: RIR | 41.222.187.0/24 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
| Route object: RIR | 41.222.186.0/24 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
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/21 | RIPE-NONAUTH | Valid |
| 102.70.0.0/15 | RADB | Valid |
| 168.253.224.0/19 | RIPE-NONAUTH | Valid |
| 168.253.224.0/20 | RIPE-NONAUTH | Valid |
| 168.253.240.0/24 | AFRINIC | Valid |
| 168.253.248.0/22 | RIPE-NONAUTH | Valid |
| 168.253.255.0/24 | AFRINIC | Valid |
| 196.216.8.0/21 | RIPE-NONAUTH | Valid |
| 2c0f:fac0::/32 | RIPE-NONAUTH | Valid |
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.