Network · data from 2026-11-12
AS41719 SKTVSPEKTR-AS SKTV Spektr LLC
Registry name: SKTVSPEKTR-AS SKTV Spektr LLC, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS41719, 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.
| 45.136.103.0/24 | No ROA | Nonecovered by 45.136.102.0/23 | 672 100% |
| 95.181.165.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 95.181.166.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 193.232.52.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 193.232.138.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.93.28.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 194.93.30.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 45.135.130.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 45.136.207.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 45.136.102.0/24 | No ROA | RIR databaseRIPE | 671 100% |
AS-SET
AS41719 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 15 are in fix.csv.
- ROA: none10
- Route object: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 45.136.103.0/24 | No ROA covers it. Add a ROA for AS41719, maxLength 24. |
| Route object: none | 45.136.103.0/24 | No route object for it. A route object for 45.136.102.0/23 with origin AS41719 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41719 in the RIR database for the space. |
| ROA: none | 95.181.165.0/24 | No ROA covers it. Add a ROA for AS41719, maxLength 24. |
| ROA: none | 95.181.166.0/24 | No ROA covers it. Add a ROA for AS41719, maxLength 24. |
| ROA: none | 193.232.52.0/24 | No ROA covers it. Add a ROA for AS41719, maxLength 24. |
| ROA: none | 193.232.138.0/24 | No ROA covers it. Add a ROA for AS41719, maxLength 24. |
| ROA: none | 194.93.28.0/23 | No ROA covers it. Add a ROA for AS41719, maxLength 23. |
| ROA: none | 194.93.30.0/23 | No ROA covers it. Add a ROA for AS41719, maxLength 23. |
| ROA: none | 45.135.130.0/24 | No ROA covers it. Add a ROA for AS41719, maxLength 24. |
| ROA: none | 45.136.207.0/24 | No ROA covers it. Add a ROA for AS41719, maxLength 24. |
| ROA: none | 45.136.102.0/24 | No ROA covers it. Add a ROA for AS41719, maxLength 24. |
Route objects not announced
Route objects with origin AS41719 whose prefix no peer sees AS41719 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.136.102.0/23 | RIPE | No ROA |
| 62.76.141.0/24 | RIPE | Valid |
| 95.181.156.0/24 | RIPE | No ROA |
| 194.93.28.0/22 | 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.