Network · data from 2026-11-12
AS36890 MTN Rwandacell
Registry name: MTN Rwandacell - MTN Rwandacell, RW · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS36890, 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.
| 2c0f:f860::/32 | Valid | Other IRR onlyRADB | 636 100% |
| 41.186.0.0/16 | Valid | RIR databaseAFRINIC, RADB, RIPE-NONAUTH | 671 100% |
| 41.186.0.0/20 | Valid | RIR databaseAFRINIC, RIPE-NONAUTH | 671 100% |
| 41.186.5.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.186.6.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.186.15.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.186.16.0/20 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.186.32.0/20 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.186.48.0/20 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.186.64.0/20 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.186.70.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.186.76.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.186.78.0/24 | Valid | RIR databaseAFRINIC, RADB | 671 100% |
| 41.186.79.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.186.80.0/20 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.186.86.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.186.88.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.186.96.0/20 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.186.112.0/20 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.186.130.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.186.131.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.186.132.0/22 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.186.136.0/22 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.186.158.0/23 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.186.160.0/20 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.186.176.0/22 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.186.180.0/22 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.186.180.0/24 | Valid | RIR databaseAFRINIC, RADB | 671 100% |
| 41.186.181.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.186.182.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.186.184.0/22 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.186.184.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.186.186.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.186.188.0/22 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.186.192.0/20 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.186.208.0/20 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.186.224.0/20 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.186.240.0/20 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.186.252.0/22 | Valid | RIR databaseAFRINIC | 671 100% |
| 196.44.240.0/20 | Valid | RIR databaseAFRINIC, RADB, RIPE-NONAUTH | 671 100% |
| 196.44.240.0/24 | Valid | RIR databaseAFRINIC, RIPE-NONAUTH | 671 100% |
| 196.44.242.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 196.44.243.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 196.44.244.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 196.44.245.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 196.44.246.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 196.44.247.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 196.44.248.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 196.44.249.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 196.44.250.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
AS-SET
PeeringDB's irr_as_set for AS36890: AS-MTNRW. 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 (AS36890 isn't in the set, or no route object for AS36890 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 | AS36890 in it | Not covered |
|---|---|---|---|---|---|
| AS-MTNRW | AFRINIC | 12 | 1 | Yes | 0 |
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 35 are in fix.csv.
- Route object: RIR1
- Route object: not announced34
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 2c0f:f860::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS36890 whose prefix no peer sees AS36890 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 41.186.0.0/22 | RADB | Valid |
| 41.186.1.0/24 | AFRINIC | Valid |
| 41.186.4.0/22 | RADB | Valid |
| 41.186.8.0/22 | RADB | Valid |
| 41.186.11.0/24 | AFRINIC | Valid |
| 41.186.16.0/22 | RADB | Valid |
| 41.186.35.0/24 | AFRINIC | Valid |
| 41.186.59.0/24 | AFRINIC | Valid |
| 41.186.128.0/20 | AFRINIC | Valid |
| 41.186.144.0/20 | AFRINIC | Valid |
| 41.186.176.0/20 | AFRINIC | Valid |
| 41.189.213.0/24 | RADB | No ROA |
| 41.222.244.0/22 | RADB | No ROA |
| 41.222.244.0/23 | RADB | No ROA |
| 41.222.244.0/24 | RADB | No ROA |
| 41.222.246.0/23 | RADB | No ROA |
| 102.130.32.0/21 | RADB | No ROA |
| 102.135.176.0/22 | RADB | No ROA |
| 102.135.176.0/23 | RADB | No ROA |
| 102.218.176.0/22 | RADB | No ROA |
| 102.218.176.0/23 | RADB | No ROA |
| 102.218.176.0/24 | RADB | No ROA |
| 102.223.210.0/24 | RADB | No ROA |
| 154.73.104.0/22 | RADB | No ROA |
| 154.117.192.0/18 | RADB | No ROA |
| 169.255.188.0/22 | RADB | No ROA |
| 169.255.188.0/23 | RADB | No ROA |
| 169.255.188.0/24 | RADB | No ROA |
| 197.157.192.0/22 | RADB | No ROA |
| 197.157.192.0/23 | RADB | No ROA |
| 197.157.192.0/24 | RADB | No ROA |
| 197.234.244.0/22 | RADB | No ROA |
| 197.234.244.0/23 | RADB | No ROA |
| 197.234.244.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.