Network · data from 2026-11-12
AS44265 SMOLTELECOM-NET OOO Smoltelecom
Registry name: SMOLTELECOM-NET OOO Smoltelecom, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS44265, 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.145.192.0/20 | No ROA | Nonecovered by 5.145.192.0/18 | 673 100% |
| 5.145.208.0/20 | No ROA | Nonecovered by 5.145.192.0/18 | 673 100% |
| 5.145.224.0/20 | No ROA | Nonecovered by 5.145.192.0/18 | 673 100% |
| 5.145.240.0/20 | No ROA | Nonecovered by 5.145.192.0/18 | 673 100% |
| 5.145.160.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 37.44.40.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 92.241.96.0/19 | No ROA | RIR databaseRIPE | 673 100% |
| 185.180.160.0/22 | No ROA | RIR databaseRIPE | 673 100% |
AS-SET
AS44265 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 13 are in fix.csv.
- ROA: none8
- Route object: none4
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 5.145.192.0/20 | No ROA covers it. Add a ROA for AS44265, maxLength 20. |
| Route object: none | 5.145.192.0/20 | No route object for it. A route object for 5.145.192.0/18 with origin AS44265 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44265 in the RIR database for the space. |
| ROA: none | 5.145.208.0/20 | No ROA covers it. Add a ROA for AS44265, maxLength 20. |
| Route object: none | 5.145.208.0/20 | No route object for it. A route object for 5.145.192.0/18 with origin AS44265 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44265 in the RIR database for the space. |
| ROA: none | 5.145.224.0/20 | No ROA covers it. Add a ROA for AS44265, maxLength 20. |
| Route object: none | 5.145.224.0/20 | No route object for it. A route object for 5.145.192.0/18 with origin AS44265 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44265 in the RIR database for the space. |
| ROA: none | 5.145.240.0/20 | No ROA covers it. Add a ROA for AS44265, maxLength 20. |
| Route object: none | 5.145.240.0/20 | No route object for it. A route object for 5.145.192.0/18 with origin AS44265 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44265 in the RIR database for the space. |
| ROA: none | 5.145.160.0/21 | No ROA covers it. Add a ROA for AS44265, maxLength 21. |
| ROA: none | 37.44.40.0/21 | No ROA covers it. Add a ROA for AS44265, maxLength 21. |
| ROA: none | 92.241.96.0/19 | No ROA covers it. Add a ROA for AS44265, maxLength 19. |
| ROA: none | 185.180.160.0/22 | No ROA covers it. Add a ROA for AS44265, maxLength 22. |
Route objects not announced
Route objects with origin AS44265 whose prefix no peer sees AS44265 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.145.192.0/18 | 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.