Network · data from 2026-11-12
AS49701 RIA-LINK-AS RIA Link Ltd
Registry name: RIA-LINK-AS RIA Link Ltd, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS49701, 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.215.188.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 91.215.188.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.215.189.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.215.190.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.215.191.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.247.208.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.247.209.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.247.216.0/22 | No ROA | RIR databaseRIPE | 673 100% |
AS-SET
AS49701 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 19 are in fix.csv.
- ROA: none8
- Route object: not announced11
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.215.188.0/22 | No ROA covers it. Add a ROA for AS49701, maxLength 22. |
| ROA: none | 91.215.188.0/24 | No ROA covers it. Add a ROA for AS49701, maxLength 24. |
| ROA: none | 91.215.189.0/24 | No ROA covers it. Add a ROA for AS49701, maxLength 24. |
| ROA: none | 91.215.190.0/24 | No ROA covers it. Add a ROA for AS49701, maxLength 24. |
| ROA: none | 91.215.191.0/24 | No ROA covers it. Add a ROA for AS49701, maxLength 24. |
| ROA: none | 91.247.208.0/24 | No ROA covers it. Add a ROA for AS49701, maxLength 24. |
| ROA: none | 91.247.209.0/24 | No ROA covers it. Add a ROA for AS49701, maxLength 24. |
| ROA: none | 91.247.216.0/22 | No ROA covers it. Add a ROA for AS49701, maxLength 22. |
Route objects not announced
Route objects with origin AS49701 whose prefix no peer sees AS49701 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.247.208.0/21 | RIPE | No ROA |
| 91.247.210.0/24 | RIPE | No ROA |
| 91.247.211.0/24 | RIPE | No ROA |
| 91.247.212.0/24 | RIPE | No ROA |
| 91.247.213.0/24 | RIPE | No ROA |
| 91.247.214.0/24 | RIPE | No ROA |
| 91.247.215.0/24 | RIPE | No ROA |
| 91.247.216.0/24 | RIPE | No ROA |
| 91.247.217.0/24 | RIPE | No ROA |
| 91.247.218.0/24 | RIPE | No ROA |
| 91.247.219.0/24 | 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.