Network · data from 2026-11-12
AS202383 EL-K-STIL-AS EL.K.STIL LLC
Registry name: EL-K-STIL-AS EL.K.STIL LLC, UA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS202383, 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.
| 2001:678:724::/48 | No ROA | Other origin only | 629 99% |
| 2001:678:6c4::/48 | No ROA | RIR databaseRIPE | 629 99% |
AS-SET
AS202383 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 3 are in fix.csv.
- ROA: none2
- Route object: none1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2001:678:724::/48 | No ROA covers it. Add a ROA for AS202383, maxLength 48. |
| Route object: none | 2001:678:724::/48 | Route objects for it name AS58215. Add a route object with origin AS202383 in the RIR database for the space. |
| ROA: none | 2001:678:6c4::/48 | No ROA covers it. Add a ROA for AS202383, maxLength 48. |
Route objects not announced
Every route object with origin AS202383 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.