Network · data from 2026-11-12
AS15468 KLGELECS-AS PJSC Rostelecom
Registry name: KLGELECS-AS PJSC Rostelecom, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS15468, 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.
| 94.242.151.0/24 | Invalid: maxLength | Nonecovered by 94.242.144.0/20 | 69 10% |
| 5.143.176.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 5.143.176.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 5.143.184.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 31.172.192.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 31.172.192.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 31.172.192.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 31.172.200.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 31.172.208.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 31.172.208.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 31.172.216.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 62.148.128.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 62.148.128.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 62.148.144.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 94.242.128.0/18 | Valid | RIR databaseRIPE | 672 100% |
| 94.242.128.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 94.242.128.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 94.242.144.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 94.242.144.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.242.145.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.242.146.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.242.147.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.242.149.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.242.150.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.242.160.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 94.242.160.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 94.242.176.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 95.107.16.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 95.107.16.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 95.107.24.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 95.107.112.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 95.107.112.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 95.107.120.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 109.225.0.0/18 | Valid | RIR databaseRIPE | 672 100% |
| 109.225.0.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 109.225.0.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 109.225.16.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 109.225.32.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 109.225.32.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 109.225.48.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 212.106.32.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 212.106.32.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 212.106.32.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 212.106.40.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 212.106.48.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 212.106.48.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 212.106.56.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 94.242.148.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
AS15468 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 2 are in fix.csv.
- ROA: maxLength1
- Route object: none1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 94.242.151.0/24 | ROA 94.242.128.0/18 AS15468 has maxLength 18; ROA 94.242.128.0/19 AS15468 has maxLength 19; ROA 94.242.144.0/20 AS15468 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 94.242.151.0/24. |
| Route object: none | 94.242.151.0/24 | No route object for it. A route object for 94.242.144.0/20 with origin AS15468 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15468 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS15468 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.