Network · data from 2026-11-12
AS49199 RIPN Autonomous Nonprofit Organisation "Russian Scientific-Research Institute for Public Networks"
Registry name: RIPN Autonomous Nonprofit Organisation "Russian Scientific-Research Institute for Public Networks", RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS49199, 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.
| 195.85.234.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 195.85.236.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 62.76.97.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 62.76.74.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 62.76.75.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 62.76.96.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS49199 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 10 are in fix.csv.
- ROA: none2
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 195.85.234.0/24 | No ROA covers it. Add a ROA for AS49199, maxLength 24. |
| ROA: none | 195.85.236.0/24 | No ROA covers it. Add a ROA for AS49199, maxLength 24. |
Route objects not announced
Route objects with origin AS49199 whose prefix no peer sees AS49199 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 194.226.34.0/24 | RIPE | Valid |
| 194.226.35.0/24 | RIPE | Valid |
| 194.226.137.0/24 | RIPE | Valid |
| 195.19.10.0/24 | RIPE | Valid |
| 195.19.11.0/24 | RIPE | Valid |
| 195.85.235.0/24 | RIPE | No ROA |
| 195.208.220.0/24 | RIPE | Valid |
| 195.208.221.0/24 | RIPE | Valid |
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.