Network · data from 2026-11-12
AS36969 Malawi Telecommunications
Registry name: Malawi Telecommunications Limited - Malawi Telecommunications Limited, MW · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS36969, 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.87.8.0/24 | Invalid: maxLength | Nonecovered by 41.87.8.0/23 | 82 12% |
| 41.87.9.0/24 | Invalid: maxLength | Nonecovered by 41.87.8.0/23 | 82 12% |
| 41.87.29.0/24 | Invalid: maxLength | RIR databaseAFRINIC | 84 12% |
| 41.87.30.0/24 | Invalid: maxLength | RIR databaseAFRINIC | 84 12% |
| 41.87.31.0/24 | Invalid: maxLength | RIR databaseAFRINIC | 84 12% |
| 41.221.96.0/24 | Invalid: maxLength | RIR databaseAFRINIC | 84 12% |
| 41.87.0.0/19 | No ROA | RIR databaseAFRINIC, RADB, RIPE-NONAUTH | 673 100% |
| 41.221.96.0/20 | No ROA | RIR databaseAFRINIC, RIPE-NONAUTH | 673 100% |
| 196.45.190.0/24 | No ROA | RIR databaseAFRINIC, RADB, RIPE-NONAUTH | 673 100% |
| 196.45.188.0/24 | No ROA | RIR databaseAFRINIC, RADB | 670 100% |
| 2c0e:7800::/24 | No ROA | RIR databaseAFRINIC, RADB | 635 100% |
| 41.87.27.0/24 | Valid | Nonecovered by 41.87.26.0/23 | 2 0%low visibility |
| 41.87.3.0/24 | Valid | RIR databaseAFRINIC, RADB | 673 100% |
| 41.87.4.0/24 | Valid | RIR databaseAFRINIC, RADB | 673 100% |
| 41.87.5.0/24 | Valid | RIR databaseAFRINIC, RADB | 673 100% |
| 41.87.6.0/24 | Valid | RIR databaseAFRINIC, RADB | 673 100% |
| 41.87.28.0/24 | Valid | RIR databaseAFRINIC | 673 100% |
| 41.221.98.0/24 | Valid | RIR databaseAFRINIC | 673 100% |
| 41.221.99.0/24 | Valid | RIR databaseAFRINIC | 673 100% |
| 41.221.100.0/24 | Valid | RIR databaseAFRINIC, RADB | 673 100% |
| 41.221.102.0/24 | Valid | RIR databaseAFRINIC | 673 100% |
| 41.221.107.0/24 | Valid | RIR databaseAFRINIC | 673 100% |
| 41.87.16.0/23 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.87.16.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.87.17.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.221.106.0/23 | Valid | RIR databaseAFRINIC | 3 0%low visibility |
| 41.221.106.0/24 | Valid | RIR databaseAFRINIC | 3 0%low visibility |
| 41.87.2.0/23 | Valid | RIR databaseAFRINIC, RADB | 2 0%low visibility |
| 41.87.7.0/24 | Valid | RIR databaseAFRINIC, RADB | 2 0%low visibility |
| 41.87.24.0/23 | Valid | RIR databaseAFRINIC | 2 0%low visibility |
| 41.87.28.0/22 | Valid | RIR databaseAFRINIC | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS36969: AS36969. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS36969 isn't in the set, or no route object for AS36969 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS36969 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS36969 | A single AS number, not a set: AS36969 (this network), 67 route objects. | |||||
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 53 are in fix.csv.
- ROA: maxLength6
- ROA: none5
- Route object: none3
- Route object: not announced39
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 41.87.8.0/24 | ROA 41.87.0.0/20 AS36969 has maxLength 20; ROA 41.87.8.0/22 AS36969 has maxLength 22; ROA 41.87.8.0/23 AS36969 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 41.87.8.0/24. |
| Route object: none | 41.87.8.0/24 | No route object for it. A route object for 41.87.8.0/23 with origin AS36969 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36969 in the RIR database for the space. |
| ROA: maxLength | 41.87.9.0/24 | ROA 41.87.0.0/20 AS36969 has maxLength 20; ROA 41.87.8.0/22 AS36969 has maxLength 22; ROA 41.87.8.0/23 AS36969 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 41.87.9.0/24. |
| Route object: none | 41.87.9.0/24 | No route object for it. A route object for 41.87.8.0/23 with origin AS36969 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36969 in the RIR database for the space. |
| ROA: maxLength | 41.87.29.0/24 | ROA 41.87.28.0/22 AS36969 has maxLength 22; ROA 41.87.28.0/23 AS36969 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 41.87.29.0/24. |
| ROA: maxLength | 41.87.30.0/24 | ROA 41.87.28.0/22 AS36969 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 41.87.30.0/24. |
| ROA: maxLength | 41.87.31.0/24 | ROA 41.87.28.0/22 AS36969 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 41.87.31.0/24. |
| ROA: maxLength | 41.221.96.0/24 | ROA 41.221.96.0/22 AS36969 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 41.221.96.0/24. |
| ROA: none | 41.87.0.0/19 | No ROA covers it. Add a ROA for AS36969, maxLength 19. |
| ROA: none | 41.221.96.0/20 | No ROA covers it. Add a ROA for AS36969, maxLength 20. |
| ROA: none | 196.45.190.0/24 | No ROA covers it. Add a ROA for AS36969, maxLength 24. |
| ROA: none | 196.45.188.0/24 | No ROA covers it. Add a ROA for AS36969, maxLength 24. |
| ROA: none | 2c0e:7800::/24 | No ROA covers it. Add a ROA for AS36969, maxLength 24. |
| Route object: none | 41.87.27.0/24 | No route object for it. A route object for 41.87.26.0/23 with origin AS36969 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36969 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS36969 whose prefix no peer sees AS36969 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 41.87.0.0/21 | AFRINIC | Invalid: maxLength |
| 41.87.0.0/23 | AFRINIC, RADB | Valid |
| 41.87.0.0/24 | AFRINIC, RADB | Valid |
| 41.87.1.0/24 | AFRINIC, RADB | Valid |
| 41.87.2.0/24 | AFRINIC, RADB | Valid |
| 41.87.4.0/23 | AFRINIC, RADB | Valid |
| 41.87.6.0/23 | AFRINIC, RADB | Valid |
| 41.87.8.0/21 | AFRINIC | Invalid: maxLength |
| 41.87.8.0/22 | AFRINIC | Valid |
| 41.87.8.0/23 | AFRINIC | Valid |
| 41.87.10.0/23 | AFRINIC | Valid |
| 41.87.11.0/24 | AFRINIC | Invalid: maxLength |
| 41.87.12.0/22 | AFRINIC | Valid |
| 41.87.12.0/23 | AFRINIC | Valid |
| 41.87.14.0/23 | AFRINIC | Valid |
| 41.87.16.0/21 | AFRINIC | Valid |
| 41.87.16.0/22 | AFRINIC | Invalid: maxLength |
| 41.87.18.0/23 | AFRINIC | Valid |
| 41.87.18.0/24 | AFRINIC | Valid |
| 41.87.19.0/24 | AFRINIC | Valid |
| 41.87.24.0/22 | AFRINIC | Valid |
| 41.87.26.0/23 | AFRINIC | Valid |
| 41.87.26.0/24 | AFRINIC | Invalid: maxLength |
| 41.87.28.0/23 | AFRINIC | Valid |
| 41.221.96.0/22 | AFRINIC | Valid |
| 41.221.96.0/23 | AFRINIC | Invalid: maxLength |
| 41.221.97.0/24 | AFRINIC | Valid |
| 41.221.98.0/23 | AFRINIC | Valid |
| 41.221.100.0/22 | AFRINIC | Valid |
| 41.221.100.0/23 | AFRINIC | Invalid: maxLength |
| 41.221.101.0/24 | AFRINIC, RADB | Valid |
| 41.221.102.0/23 | AFRINIC | Invalid: maxLength |
| 41.221.103.0/24 | AFRINIC | Valid |
| 41.221.104.0/21 | AFRINIC | Valid |
| 41.221.104.0/23 | AFRINIC | Valid |
| 41.221.104.0/24 | AFRINIC | Invalid: maxLength |
| 41.221.105.0/24 | AFRINIC | Invalid: maxLength |
| 41.221.108.0/23 | AFRINIC | Invalid: maxLength |
| 102.176.250.0/24 | RADB | No 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.