Network · data from 2026-11-12
AS196648 YSU-AS North-Eastern Federal University n.a. M.K.Ammosov, State Federal Autonomous Educational Organisation of Higher Professional Education
Registry name: YSU-AS North-Eastern Federal University n.a. M.K.Ammosov, State Federal Autonomous Educational Organisation of Higher Professional Education, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS196648, 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.
| 94.231.16.0/20 | No ROA | RIR databaseRADB, RIPE | 673 100% |
AS-SET
AS196648 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 19 are in fix.csv.
- ROA: none1
- Route object: not announced18
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 94.231.16.0/20 | No ROA covers it. Add a ROA for AS196648, maxLength 20. |
Route objects not announced
Route objects with origin AS196648 whose prefix no peer sees AS196648 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 94.231.16.0/21 | RIPE | No ROA |
| 94.231.16.0/24 | RIPE | No ROA |
| 94.231.17.0/24 | RIPE | No ROA |
| 94.231.18.0/24 | RIPE | No ROA |
| 94.231.19.0/24 | RIPE | No ROA |
| 94.231.20.0/24 | RIPE | No ROA |
| 94.231.21.0/24 | RIPE | No ROA |
| 94.231.22.0/24 | RIPE | No ROA |
| 94.231.23.0/24 | RIPE | No ROA |
| 94.231.24.0/22 | RIPE | No ROA |
| 94.231.24.0/24 | RIPE | No ROA |
| 94.231.25.0/24 | RIPE | No ROA |
| 94.231.26.0/24 | RIPE | No ROA |
| 94.231.27.0/24 | RIPE | No ROA |
| 94.231.28.0/24 | RIPE | No ROA |
| 94.231.29.0/24 | RIPE | No ROA |
| 94.231.30.0/24 | RIPE | No ROA |
| 94.231.31.0/24 | RIPE | 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.