Network · data from 2026-11-12
AS57452 Summit-Systems-AS Summit Systems Ltd.
Registry name: Summit-Systems-AS Summit Systems Ltd., RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS57452, 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.45.27.219/32 | No ROA | Nonecovered by 212.45.27.0/24 | 6 1%low visibility |
| 82.138.42.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.232.12.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 91.235.26.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 212.45.27.0/24 | No ROA | RIR databaseRIPE | 673 100% |
AS-SET
AS57452 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 | 212.45.27.219/32 | No ROA covers it. Add a ROA for AS57452, maxLength 32. |
| Route object: none | 212.45.27.219/32 | No route object for it. A route object for 212.45.27.0/24 with origin AS57452 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS57452 in the RIR database for the space. |
| ROA: none | 82.138.42.0/24 | No ROA covers it. Add a ROA for AS57452, maxLength 24. |
| ROA: none | 91.232.12.0/22 | No ROA covers it. Add a ROA for AS57452, maxLength 22. |
| ROA: none | 91.235.26.0/24 | No ROA covers it. Add a ROA for AS57452, maxLength 24. |
| ROA: none | 212.45.27.0/24 | No ROA covers it. Add a ROA for AS57452, maxLength 24. |
Route objects not announced
Route objects with origin AS57452 whose prefix no peer sees AS57452 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.232.12.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.