Network · data from 2026-11-12
AS56818 NCUBE-AS Chernyshov Volodymyr
Registry name: NCUBE-AS Chernyshov Volodymyr, UA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS56818, 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.
| 5.153.177.0/24 | Invalid: origin | Other origin only | 113 17% |
| 91.227.254.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 192.162.200.0/22 | Valid | RIR databaseRIPE | 670 100% |
AS-SET
AS56818 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 5 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 5.153.177.0/24 | ROAs covering it name AS41039, not AS56818. If AS56818 should announce it, add a ROA for AS56818. |
| Route object: none | 5.153.177.0/24 | Route objects for it name AS41039. Add a route object with origin AS56818 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS56818 whose prefix no peer sees AS56818 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 192.162.200.0/24 | RIPE | Valid |
| 192.162.201.0/24 | RIPE | Valid |
| 192.162.202.0/23 | RIPE | 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.