Network · data from 2026-11-12
AS36996 Telecom Namibia - Telecom Namibia
Registry name: Telecom Namibia - Telecom Namibia, NA · not in PeeringDB
37IPv4 routes
100.0% RPKI valid · 75.7% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
9 with no route object for this origin
2Low visibility
seen by under 10% of full-table peers
9Route objects not announced
registered with origin AS36996, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS36996, 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.182.176.0/20 | Valid | Nonecovered by 41.182.160.0/19 | 673 100% |
| 41.205.135.0/24 | Valid | Nonecovered by 41.205.128.0/19 | 673 100% |
| 41.205.152.0/24 | Valid | Nonecovered by 41.205.128.0/19 | 673 100% |
| 197.188.135.0/24 | Valid | Nonecovered by 197.188.0.0/16 | 673 100% |
| 197.188.176.0/21 | Valid | Nonecovered by 197.188.0.0/16 | 673 100% |
| 197.188.133.0/24 | Valid | Nonecovered by 197.188.0.0/16 | 672 100% |
| 41.182.136.0/21 | Valid | Nonecovered by 41.182.0.0/16 | 670 100% |
| 41.182.160.0/20 | Valid | Nonecovered by 41.182.160.0/19 | 670 100% |
| 197.188.96.0/21 | Valid | Nonecovered by 197.188.0.0/16 | 670 100% |
| 41.182.0.0/16 | Valid | RIR databaseAFRINIC, RADB | 673 100% |
| 41.182.0.0/19 | Valid | RIR databaseAFRINIC | 673 100% |
| 41.182.32.0/20 | Valid | RIR databaseAFRINIC | 673 100% |
| 41.182.64.0/20 | Valid | RIR databaseAFRINIC | 673 100% |
| 41.182.64.0/21 | Valid | RIR databaseAFRINIC | 673 100% |
| 41.182.128.0/21 | Valid | RIR databaseAFRINIC | 673 100% |
| 41.182.160.0/19 | Valid | RIR databaseAFRINIC | 673 100% |
| 41.182.192.0/20 | Valid | RIR databaseAFRINIC | 673 100% |
| 41.205.128.0/19 | Valid | RIR databaseAFRINIC, RADB | 673 100% |
| 41.205.143.0/24 | Valid | RIR databaseAFRINIC | 673 100% |
| 196.44.128.0/19 | Valid | RIR databaseAFRINIC, RADB | 673 100% |
| 196.44.150.0/24 | Valid | RIR databaseAFRINIC | 673 100% |
| 197.188.0.0/16 | Valid | RIR databaseAFRINIC, RADB | 673 100% |
| 197.188.168.0/21 | Valid | RIR databaseAFRINIC | 673 100% |
| 197.188.254.0/24 | Valid | RIR databaseAFRINIC | 673 100% |
| 41.182.32.0/19 | Valid | RIR databaseAFRINIC | 670 100% |
| 41.182.64.0/19 | Valid | RIR databaseAFRINIC | 670 100% |
| 41.182.96.0/19 | Valid | RIR databaseAFRINIC | 670 100% |
| 41.182.96.0/20 | Valid | RIR databaseAFRINIC | 670 100% |
| 41.182.144.0/21 | Valid | RIR databaseAFRINIC | 670 100% |
| 41.182.208.0/20 | Valid | RIR databaseAFRINIC | 670 100% |
| 41.205.142.0/24 | Valid | RIR databaseAFRINIC | 670 100% |
| 197.188.144.0/21 | Valid | RIR databaseAFRINIC | 670 100% |
| 197.188.160.0/21 | Valid | RIR databaseAFRINIC | 670 100% |
| 197.188.208.0/21 | Valid | RIR databaseAFRINIC | 670 100% |
| 196.44.136.0/24 | Valid | RIR databaseAFRINIC | 669 99% |
| 41.182.0.0/20 | Valid | RIR databaseAFRINIC | 2 0%low visibility |
| 41.182.7.0/24 | Valid | RIR databaseAFRINIC | 2 0%low visibility |
AS-SET
AS36996 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 18 are in fix.csv.
- Route object: none9
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 41.182.176.0/20 | No route object for it. A route object for 41.182.160.0/19 with origin AS36996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36996 in the RIR database for the space. |
| Route object: none | 41.205.135.0/24 | No route object for it. A route object for 41.205.128.0/19 with origin AS36996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36996 in the RIR database for the space. |
| Route object: none | 41.205.152.0/24 | No route object for it. A route object for 41.205.128.0/19 with origin AS36996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36996 in the RIR database for the space. |
| Route object: none | 197.188.135.0/24 | No route object for it. A route object for 197.188.0.0/16 with origin AS36996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36996 in the RIR database for the space. |
| Route object: none | 197.188.176.0/21 | No route object for it. A route object for 197.188.0.0/16 with origin AS36996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36996 in the RIR database for the space. |
| Route object: none | 197.188.133.0/24 | No route object for it. A route object for 197.188.0.0/16 with origin AS36996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36996 in the RIR database for the space. |
| Route object: none | 41.182.136.0/21 | No route object for it. A route object for 41.182.0.0/16 with origin AS36996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36996 in the RIR database for the space. |
| Route object: none | 41.182.160.0/20 | No route object for it. A route object for 41.182.160.0/19 with origin AS36996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36996 in the RIR database for the space. |
| Route object: none | 197.188.96.0/21 | No route object for it. A route object for 197.188.0.0/16 with origin AS36996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36996 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS36996 whose prefix no peer sees AS36996 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 41.182.243.0/24 | AFRINIC | Valid |
| 197.188.24.0/21 | AFRINIC | Valid |
| 197.188.32.0/20 | AFRINIC | Valid |
| 197.188.48.0/20 | AFRINIC | Valid |
| 197.188.64.0/20 | AFRINIC | Valid |
| 197.188.80.0/20 | AFRINIC | Valid |
| 197.188.104.0/22 | AFRINIC | Valid |
| 197.188.112.0/20 | AFRINIC | Valid |
| 197.188.192.0/21 | AFRINIC | 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.