Network · data from 2026-11-12
AS42548 KCHR-AS PJSC Rostelecom
Registry name: KCHR-AS PJSC Rostelecom, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS42548, 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.
| 62.183.76.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 83.239.112.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 83.239.123.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.172.182.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.172.184.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 85.173.160.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 85.173.165.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.173.166.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.173.169.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.173.170.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 85.173.172.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 85.173.174.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.173.177.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.173.180.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 85.173.188.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 178.34.224.0/19 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS42548 isn't in PeeringDB, where networks name their AS-SET.
Fix list
Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.
Route objects not announced
Every route object with origin AS42548 is announced.
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.