Network · data from 2026-11-12
AS328988 SAFARICOM ETHIOPIA (ORG-STEP1-AFRINIC)
Registry name: SAFARICOM TELECOMMUNICATIONS ETHIOPIA PLC - SAFARICOM TELECOMMUNICATIONS ETHIOPIA PLC, ET · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS328988, 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:6f00::/32 | No ROA | RIR databaseAFRINIC, RADB | 2 0%low visibility |
| 102.213.68.0/24 | Valid | RIR databaseAFRINIC, RADB | 672 100% |
| 102.203.224.0/22 | Valid | RIR databaseAFRINIC | 671 100% |
| 102.203.224.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 102.203.225.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 102.203.226.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 102.208.98.0/24 | Valid | RIR databaseAFRINIC, RADB | 671 100% |
| 102.208.99.0/24 | Valid | RIR databaseAFRINIC, RADB | 671 100% |
| 102.213.70.0/24 | Valid | RIR databaseAFRINIC, RADB | 671 100% |
| 102.213.71.0/24 | Valid | RIR databaseAFRINIC, RADB | 671 100% |
| 102.218.48.0/22 | Valid | RIR databaseAFRINIC, RADB | 671 100% |
| 102.218.48.0/24 | Valid | RIR databaseAFRINIC, RADB | 671 100% |
| 102.218.51.0/24 | Valid | RIR databaseAFRINIC, RADB | 671 100% |
| 196.97.16.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 196.97.17.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 196.97.18.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 196.97.19.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 102.208.97.0/24 | Valid | RIR databaseAFRINIC, RADB | 670 100% |
| 102.203.227.0/24 | Valid | RIR databaseAFRINIC | 669 99% |
| 102.208.96.0/22 | Valid | RIR databaseAFRINIC, RADB | 669 99% |
| 102.208.96.0/24 | Valid | RIR databaseAFRINIC, RADB | 669 99% |
| 102.213.68.0/22 | Valid | RIR databaseAFRINIC, RADB | 669 99% |
| 102.213.69.0/24 | Valid | RIR databaseAFRINIC, RADB | 669 99% |
| 102.218.49.0/24 | Valid | RIR databaseAFRINIC, RADB | 669 99% |
| 102.218.50.0/24 | Valid | RIR databaseAFRINIC, RADB | 669 99% |
AS-SET
PeeringDB's irr_as_set for AS328988: AFRINIC::AS-STEP_ALL_AS AFRINIC::RS-STEP_ALL_PREFIX. 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 (AS328988 isn't in the set, or no route object for AS328988 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 | AS328988 in it | Not covered | |
|---|---|---|---|---|---|---|
| AFRINIC::AS-STEP_ALL_AS | AFRINIC | 3 | 3 | Yes | 0 | |
| AFRINIC::RS-STEP_ALL_PREFIX | A route-set, not an AS-SET; route-sets aren't expanded. | |||||
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 10 are in fix.csv.
- ROA: none1
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2c0f:6f00::/32 | No ROA covers it. Add a ROA for AS328988, maxLength 32. |
Route objects not announced
Route objects with origin AS328988 whose prefix no peer sees AS328988 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 102.203.224.0/23 | AFRINIC | Valid |
| 102.203.226.0/23 | AFRINIC | Valid |
| 102.208.96.0/23 | AFRINIC | Invalid: maxLength |
| 102.208.98.0/23 | AFRINIC | Invalid: maxLength |
| 102.213.68.0/23 | AFRINIC | Invalid: maxLength |
| 102.213.70.0/23 | AFRINIC | Invalid: maxLength |
| 102.218.48.0/23 | AFRINIC | Invalid: maxLength |
| 102.218.50.0/23 | AFRINIC | Invalid: maxLength |
| 196.97.16.0/22 | AFRINIC | Valid |
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.