Network · data from 2026-11-12
AS57562 PULS-KT-AS Puls-KT LLC.
Registry name: PULS-KT-AS Puls-KT LLC., RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS57562, 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.
| 91.232.216.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 91.232.217.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 93.170.248.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 93.170.248.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.170.249.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.171.166.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 93.171.166.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.232.216.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 93.171.167.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS57562 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 3 are in fix.csv.
- ROA: none2
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.232.216.0/23 | No ROA covers it. Add a ROA for AS57562, maxLength 23. |
| ROA: none | 91.232.217.0/24 | No ROA covers it. Add a ROA for AS57562, maxLength 24. |
Route objects not announced
Route objects with origin AS57562 whose prefix no peer sees AS57562 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.232.216.128/25 | RIPE | Invalid: maxLength |
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.