Network · data from 2026-11-12
AS37185 iSAT Africa Zambia Ltd - iSAT Africa Zambia Ltd
Registry name: iSAT Africa Zambia Ltd - iSAT Africa Zambia Ltd, ZM · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS37185, 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.191.116.0/24 | No ROA | RIR databaseAFRINIC, RIPE-NONAUTH | 673 100% |
| 41.191.119.0/24 | No ROA | RIR databaseAFRINIC, RIPE-NONAUTH | 673 100% |
| 154.73.233.0/24 | No ROA | RIR databaseAFRINIC, RIPE-NONAUTH | 2 0%low visibility |
AS-SET
AS37185 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 12 are in fix.csv.
- ROA: none3
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 41.191.116.0/24 | No ROA covers it. Add a ROA for AS37185, maxLength 24. |
| ROA: none | 41.191.119.0/24 | No ROA covers it. Add a ROA for AS37185, maxLength 24. |
| ROA: none | 154.73.233.0/24 | No ROA covers it. Add a ROA for AS37185, maxLength 24. |
Route objects not announced
Route objects with origin AS37185 whose prefix no peer sees AS37185 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 41.191.116.0/22 | AFRINIC, RIPE-NONAUTH | No ROA |
| 41.191.116.0/23 | RADB | No ROA |
| 41.191.118.0/24 | RIPE-NONAUTH | No ROA |
| 154.73.232.0/22 | AFRINIC, RIPE-NONAUTH | No ROA |
| 154.73.232.0/23 | RADB, RIPE-NONAUTH | No ROA |
| 154.73.232.0/24 | AFRINIC, RIPE-NONAUTH | No ROA |
| 154.73.234.0/23 | RIPE-NONAUTH | No ROA |
| 154.73.234.0/24 | AFRINIC, RIPE-NONAUTH | No ROA |
| 2c0f:fd90::/32 | AFRINIC, RIPE-NONAUTH | 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.