Network · data from 2026-11-12
AS328566 STE ELITE NETWORKS SARL - STE ELITE NETWORKS SARL
Registry name: STE ELITE NETWORKS SARL - STE ELITE NETWORKS SARL, CD · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS328566, 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.23.118.0/24 | No ROA | Nonecovered by 102.23.116.0/22 | 672 100% |
| 102.23.116.0/24 | No ROA | RIR databaseAFRINIC | 671 100% |
| 102.23.119.0/24 | No ROA | RIR databaseAFRINIC | 670 100% |
AS-SET
AS328566 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.
- ROA: none3
- Route object: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 102.23.118.0/24 | No ROA covers it. Add a ROA for AS328566, maxLength 24. |
| Route object: none | 102.23.118.0/24 | No route object for it. A route object for 102.23.116.0/22 with origin AS328566 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328566 in the RIR database for the space. |
| ROA: none | 102.23.116.0/24 | No ROA covers it. Add a ROA for AS328566, maxLength 24. |
| ROA: none | 102.23.119.0/24 | No ROA covers it. Add a ROA for AS328566, maxLength 24. |
Route objects not announced
Route objects with origin AS328566 whose prefix no peer sees AS328566 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 102.23.116.0/22 | AFRINIC | No ROA |
| 102.23.117.0/24 | AFRINIC | No ROA |
| 102.23.118.0/32 | AFRINIC | No ROA |
| 2c0f:eac8::/32 | 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.