Network · data from 2026-11-12
AS3316 RELARN
Registry name: RELARN Join-stock company "Internet Exchange"MSK-IX", RU · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS3316, 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.
| 194.226.72.0/24 | No ROA | Nonecovered by 194.226.64.0/20 | 37 5%low visibility |
| 194.226.64.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.226.69.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.226.64.0/20 | No ROA | RIR databaseRIPE | 672 100% |
| 194.226.73.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 2001:6d0:ffb8::/48 | No ROA | RIR databaseRIPE | 636 100% |
| 2001:6d0:ffd9::/48 | No ROA | RIR databaseRIPE | 635 100% |
| 86.62.49.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.232.85.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.232.131.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.85.105.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.85.106.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.85.117.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.85.118.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.85.119.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.190.132.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 194.190.134.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.190.145.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.190.156.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.226.46.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 195.19.26.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.208.22.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 195.209.16.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.209.146.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.190.132.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 194.190.138.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 194.190.141.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 194.190.142.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 194.190.148.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 194.226.29.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 194.226.44.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 195.209.4.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 195.209.8.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS3316's PeeringDB record names no 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 12 are in fix.csv.
- ROA: none7
- Route object: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 194.226.72.0/24 | No ROA covers it. Add a ROA for AS3316, maxLength 24. |
| Route object: none | 194.226.72.0/24 | No route object for it. A route object for 194.226.64.0/20 with origin AS3316 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3316 in the RIR database for the space. |
| ROA: none | 194.226.64.0/24 | No ROA covers it. Add a ROA for AS3316, maxLength 24. |
| ROA: none | 194.226.69.0/24 | No ROA covers it. Add a ROA for AS3316, maxLength 24. |
| ROA: none | 194.226.64.0/20 | No ROA covers it. Add a ROA for AS3316, maxLength 20. |
| ROA: none | 194.226.73.0/24 | No ROA covers it. Add a ROA for AS3316, maxLength 24. |
| ROA: none | 2001:6d0:ffb8::/48 | No ROA covers it. Add a ROA for AS3316, maxLength 48. |
| ROA: none | 2001:6d0:ffd9::/48 | No ROA covers it. Add a ROA for AS3316, maxLength 48. |
Route objects not announced
Route objects with origin AS3316 whose prefix no peer sees AS3316 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 194.85.105.11/32 | RIPE | Invalid: maxLength |
| 194.85.105.12/32 | RIPE | Invalid: maxLength |
| 194.226.67.0/24 | RIPE | No ROA |
| 2001:67c:1442::/48 | 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.