Network · data from 2026-11-12
AS51012 RU-URALPROMSERVICE-AS LLC "Uralpromservice"
Registry name: RU-URALPROMSERVICE-AS LLC "Uralpromservice", RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS51012, 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.
| 85.208.223.0/24 | No ROA | Nonecovered by 85.208.220.0/22 | 673 100% |
| 85.208.220.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 85.208.220.0/23 | No ROA | RIR databaseRIPE | 672 100% |
| 85.208.220.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 2a05:6c40::/32 | No ROA | RIR databaseRIPE | 635 100% |
AS-SET
AS51012 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 7 are in fix.csv.
- ROA: none5
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 85.208.223.0/24 | No ROA covers it. Add a ROA for AS51012, maxLength 24. |
| Route object: none | 85.208.223.0/24 | No route object for it. A route object for 85.208.220.0/22 with origin AS51012 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51012 in the RIR database for the space. |
| ROA: none | 85.208.220.0/22 | No ROA covers it. Add a ROA for AS51012, maxLength 22. |
| ROA: none | 85.208.220.0/23 | No ROA covers it. Add a ROA for AS51012, maxLength 23. |
| ROA: none | 85.208.220.0/24 | No ROA covers it. Add a ROA for AS51012, maxLength 24. |
| ROA: none | 2a05:6c40::/32 | No ROA covers it. Add a ROA for AS51012, maxLength 32. |
Route objects not announced
Route objects with origin AS51012 whose prefix no peer sees AS51012 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 85.208.221.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.