Network · data from 2026-11-12
AS328676 Zanzibar Information Communication Technology Infrastructure Agency (ZICTIA) - Zanzibar Information Communication Technology Infrastructure Agency (ZICTIA)
Registry name: Zanzibar Information Communication Technology Infrastructure Agency (ZICTIA) - Zanzibar Information Communication Technology Infrastructure Agency (ZICTIA), TZ · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS328676, 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.207.204.0/24 | Valid | Nonecovered by 102.207.204.0/22 | 672 100% |
| 102.207.205.0/24 | Valid | Nonecovered by 102.207.204.0/22 | 672 100% |
| 102.207.206.0/24 | Valid | Nonecovered by 102.207.204.0/22 | 672 100% |
| 102.207.207.0/24 | Valid | Nonecovered by 102.207.204.0/22 | 672 100% |
| 102.214.44.0/24 | Valid | Nonecovered by 102.214.44.0/23 | 672 100% |
| 102.214.45.0/24 | Valid | Nonecovered by 102.214.44.0/23 | 672 100% |
| 102.223.7.0/24 | Valid | RIR databaseAFRINIC | 672 100% |
AS-SET
AS328676 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 8 are in fix.csv.
- Route object: none6
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 102.207.204.0/24 | No route object for it. A route object for 102.207.204.0/22 with origin AS328676 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328676 in the RIR database for the space. |
| Route object: none | 102.207.205.0/24 | No route object for it. A route object for 102.207.204.0/22 with origin AS328676 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328676 in the RIR database for the space. |
| Route object: none | 102.207.206.0/24 | No route object for it. A route object for 102.207.204.0/22 with origin AS328676 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328676 in the RIR database for the space. |
| Route object: none | 102.207.207.0/24 | No route object for it. A route object for 102.207.204.0/22 with origin AS328676 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328676 in the RIR database for the space. |
| Route object: none | 102.214.44.0/24 | No route object for it. A route object for 102.214.44.0/23 with origin AS328676 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328676 in the RIR database for the space. |
| Route object: none | 102.214.45.0/24 | No route object for it. A route object for 102.214.44.0/23 with origin AS328676 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328676 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS328676 whose prefix no peer sees AS328676 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 102.207.204.0/22 | AFRINIC | No ROA |
| 102.214.44.0/23 | AFRINIC | 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.