Network · data from 2026-11-12
AS57261 YARTV-AS YarTV Ltd.
Registry name: YARTV-AS YarTV Ltd., RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS57261, 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.
| 188.0.0.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 188.0.4.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 188.0.8.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 188.0.12.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 188.0.16.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 188.0.20.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 188.0.0.0/19 | No ROA | RIR databaseRIPE | 672 100% |
| 188.0.24.0/22 | No ROA | RIR databaseRIPE | 2 0%low visibility |
AS-SET
AS57261 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 27 are in fix.csv.
- ROA: none8
- Route object: not announced19
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 188.0.0.0/22 | No ROA covers it. Add a ROA for AS57261, maxLength 22. |
| ROA: none | 188.0.4.0/22 | No ROA covers it. Add a ROA for AS57261, maxLength 22. |
| ROA: none | 188.0.8.0/22 | No ROA covers it. Add a ROA for AS57261, maxLength 22. |
| ROA: none | 188.0.12.0/22 | No ROA covers it. Add a ROA for AS57261, maxLength 22. |
| ROA: none | 188.0.16.0/22 | No ROA covers it. Add a ROA for AS57261, maxLength 22. |
| ROA: none | 188.0.20.0/22 | No ROA covers it. Add a ROA for AS57261, maxLength 22. |
| ROA: none | 188.0.0.0/19 | No ROA covers it. Add a ROA for AS57261, maxLength 19. |
| ROA: none | 188.0.24.0/22 | No ROA covers it. Add a ROA for AS57261, maxLength 22. |
Route objects not announced
Route objects with origin AS57261 whose prefix no peer sees AS57261 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 87.250.220.0/24 | RIPE | No ROA |
| 91.230.23.0/24 | RADB | No ROA |
| 188.0.0.0/23 | RIPE | No ROA |
| 188.0.2.0/23 | RIPE | No ROA |
| 188.0.4.0/23 | RIPE | No ROA |
| 188.0.6.0/23 | RIPE | No ROA |
| 188.0.8.0/23 | RIPE | No ROA |
| 188.0.10.0/23 | RIPE | No ROA |
| 188.0.12.0/23 | RIPE | No ROA |
| 188.0.14.0/23 | RIPE | No ROA |
| 188.0.16.0/23 | RIPE | No ROA |
| 188.0.18.0/23 | RIPE | No ROA |
| 188.0.20.0/23 | RIPE | No ROA |
| 188.0.22.0/23 | RIPE | No ROA |
| 188.0.24.0/23 | RIPE | No ROA |
| 188.0.26.0/23 | RIPE | No ROA |
| 188.0.28.0/22 | RIPE | Invalid: origin |
| 188.0.28.0/23 | RIPE | Invalid: origin |
| 188.0.30.0/23 | RIPE | Invalid: origin |
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.