Network · data from 2026-11-12
AS218583 Dr-Nefarios-Lab Anastasia Cernavska
Registry name: Dr-Nefarios-Lab Anastasia Cernavska, LV · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS218583, 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.
| 151.247.85.0/24 | Invalid: origin | None | 273 41% |
| 151.247.86.0/24 | Invalid: origin | None | 271 40% |
AS-SET
AS218583 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 6 are in fix.csv.
- ROA: origin2
- Route object: none2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 151.247.85.0/24 | ROAs covering it name AS834, not AS218583. If AS218583 should announce it, add a ROA for AS218583. |
| Route object: none | 151.247.85.0/24 | No route object for it. Add a route object with origin AS218583 in the RIR database for the space. |
| ROA: origin | 151.247.86.0/24 | ROAs covering it name AS834, not AS218583. If AS218583 should announce it, add a ROA for AS218583. |
| Route object: none | 151.247.86.0/24 | No route object for it. Add a route object with origin AS218583 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS218583 whose prefix no peer sees AS218583 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 31.58.94.0/24 | RIPE | Valid |
| 201.58.138.0/24 | 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.