Network · data from 2026-11-12
AS5468 UrFU Yeltsin UrFU, Ural Federal University
Registry name: UrFU Yeltsin UrFU, Ural Federal University, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS5468, 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.
| 212.193.69.0/24 | No ROA | Nonecovered by 212.193.64.0/19 | 673 100% |
| 93.88.176.0/20 | No ROA | Other origin only | 168 25% |
| 212.193.64.0/19 | No ROA | RIR databaseRIPE | 673 100% |
AS-SET
AS5468 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 10 are in fix.csv.
- ROA: none3
- Route object: none2
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 212.193.69.0/24 | No ROA covers it. Add a ROA for AS5468, maxLength 24. |
| Route object: none | 212.193.69.0/24 | No route object for it. A route object for 212.193.64.0/19 with origin AS5468 covers it (filters allowing more-specifics accept it). Add a route object with origin AS5468 in the RIR database for the space. |
| ROA: none | 93.88.176.0/20 | No ROA covers it. Add a ROA for AS5468, maxLength 20. |
| Route object: none | 93.88.176.0/20 | Route objects for it name AS44868. Add a route object with origin AS5468 in the RIR database for the space. |
| ROA: none | 212.193.64.0/19 | No ROA covers it. Add a ROA for AS5468, maxLength 19. |
Route objects not announced
Route objects with origin AS5468 whose prefix no peer sees AS5468 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 212.193.64.0/22 | RIPE | No ROA |
| 212.193.78.0/24 | RIPE | No ROA |
| 212.193.80.0/22 | RIPE | No ROA |
| 212.193.94.0/24 | RIPE | No ROA |
| 212.193.95.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.