Network · data from 2026-11-12
AS37395 Abari Communications
Registry name: Abari Communications - Abari Communications, BW · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS37395, 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.
| 102.165.135.0/24 | Valid | Nonecovered by 102.165.128.0/19 | 672 100% |
| 102.165.128.0/24 | Valid | Nonecovered by 102.165.128.0/19 | 63 9%low visibility |
| 41.79.136.0/22 | Valid | RIR databaseAFRINIC, RIPE-NONAUTH | 672 100% |
| 102.165.128.0/19 | Valid | RIR databaseAFRINIC | 672 100% |
| 2c0f:fac8::/32 | Valid | RIR databaseAFRINIC | 40 6%low visibility |
AS-SET
AS37395's PeeringDB record names no 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 6 are in fix.csv.
- Route object: none2
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 102.165.135.0/24 | No route object for it. A route object for 102.165.128.0/19 with origin AS37395 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37395 in the RIR database for the space. |
| Route object: none | 102.165.128.0/24 | No route object for it. A route object for 102.165.128.0/19 with origin AS37395 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37395 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS37395 whose prefix no peer sees AS37395 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 41.79.136.0/24 | AFRINIC | Invalid: maxLength |
| 41.79.137.0/24 | AFRINIC | Invalid: maxLength |
| 41.79.138.0/24 | AFRINIC | Invalid: maxLength |
| 41.79.139.0/24 | AFRINIC | Invalid: maxLength |
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.