Network · data from 2026-11-12
AS37532 ZAMREN
Registry name: Zambia Research and Education Network (ZAMREN) - Zambia Research and Education Network (ZAMREN), ZM · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS37532, 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.63.0.0/19 | Valid | Nonecovered by 41.63.0.0/18 | 672 100% |
| 41.63.3.0/24 | Valid | Nonecovered by 41.63.0.0/18 | 672 100% |
| 41.63.32.0/19 | Valid | Nonecovered by 41.63.0.0/18 | 672 100% |
| 155.0.0.0/17 | Valid | Nonecovered by 155.0.0.0/16 | 672 100% |
| 155.0.4.0/24 | Valid | Nonecovered by 155.0.0.0/16 | 672 100% |
| 155.0.34.0/24 | Valid | Nonecovered by 155.0.0.0/16 | 672 100% |
| 155.0.128.0/17 | Valid | Nonecovered by 155.0.0.0/16 | 672 100% |
| 41.63.0.0/18 | Valid | RIR databaseAFRINIC | 673 100% |
| 155.0.0.0/16 | Valid | RIR databaseAFRINIC | 673 100% |
| 2c0f:f670::/32 | Valid | RIR databaseAFRINIC | 633 100% |
AS-SET
PeeringDB's irr_as_set for AS37532: AS-37532. 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 (AS37532 isn't in the set, or no route object for AS37532 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 | AS37532 in it | Not covered |
|---|---|---|---|---|---|
| AS-37532 | AFRINIC | 1 | 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 7 are in fix.csv.
- Route object: none7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 41.63.0.0/19 | No route object for it. A route object for 41.63.0.0/18 with origin AS37532 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37532 in the RIR database for the space. |
| Route object: none | 41.63.3.0/24 | No route object for it. A route object for 41.63.0.0/18 with origin AS37532 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37532 in the RIR database for the space. |
| Route object: none | 41.63.32.0/19 | No route object for it. A route object for 41.63.0.0/18 with origin AS37532 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37532 in the RIR database for the space. |
| Route object: none | 155.0.0.0/17 | No route object for it. A route object for 155.0.0.0/16 with origin AS37532 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37532 in the RIR database for the space. |
| Route object: none | 155.0.4.0/24 | No route object for it. A route object for 155.0.0.0/16 with origin AS37532 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37532 in the RIR database for the space. |
| Route object: none | 155.0.34.0/24 | No route object for it. A route object for 155.0.0.0/16 with origin AS37532 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37532 in the RIR database for the space. |
| Route object: none | 155.0.128.0/17 | No route object for it. A route object for 155.0.0.0/16 with origin AS37532 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37532 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS37532 is announced.
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.