bgpreport

Network · data from 2026-11-12

AS35608 RLINE1-AS R-LINE 1 LLC

Registry name: RLINE1-AS R-LINE 1 LLC, RU · not in PeeringDB

13IPv4 routes 53.8% RPKI valid · 100.0% with a route object
5IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
11No ROA 0 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
9Route objects not announced registered with origin AS35608, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS35608, 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.141.93.0/24 No ROA RIR databaseRIPE 673 100% 66
171.22.212.0/24 No ROA RIR databaseRIPE 673 100% 66
171.22.213.0/24 No ROA RIR databaseRIPE 673 100% 66
171.22.214.0/24 No ROA RIR databaseRIPE 673 100% 66
171.22.215.0/24 No ROA RIR databaseRIPE 673 100% 66
193.19.111.0/24 No ROA RIR databaseRIPE 673 100% 66
2a09:3ec0::/48 No ROA RIR databaseRIPE 636 100% 69
2a09:3ec0:1::/48 No ROA RIR databaseRIPE 636 100% 69
2a09:3ec0:5::/48 No ROA RIR databaseRIPE 636 100% 69
2a09:3ec0:8::/48 No ROA RIR databaseRIPE 636 100% 68
2a09:3ec0:4::/48 No ROA RIR databaseRIPE 1 0%low visibility 1
45.136.144.0/24 Valid RIR databaseRIPE 673 100% 66
79.171.117.0/24 Valid RIR databaseRIPE 673 100% 66
91.192.95.0/24 Valid RIR databaseRIPE 673 100% 67
193.8.74.0/24 Valid RIR databaseRIPE 673 100% 66
194.67.69.0/24 Valid RIR databaseRIPE 673 100% 67
194.67.70.0/24 Valid RIR databaseRIPE 673 100% 66
192.144.17.0/24 Valid RIR databaseRIPE 671 100% 67

AS-SET

AS35608 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 20 are in fix.csv.

  • ROA: none11
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none45.141.93.0/24No ROA covers it. Add a ROA for AS35608, maxLength 24.673 of 673
ROA: none171.22.212.0/24No ROA covers it. Add a ROA for AS35608, maxLength 24.673 of 673
ROA: none171.22.213.0/24No ROA covers it. Add a ROA for AS35608, maxLength 24.673 of 673
ROA: none171.22.214.0/24No ROA covers it. Add a ROA for AS35608, maxLength 24.673 of 673
ROA: none171.22.215.0/24No ROA covers it. Add a ROA for AS35608, maxLength 24.673 of 673
ROA: none193.19.111.0/24No ROA covers it. Add a ROA for AS35608, maxLength 24.673 of 673
ROA: none2a09:3ec0::/48No ROA covers it. Add a ROA for AS35608, maxLength 48.636 of 636
ROA: none2a09:3ec0:1::/48No ROA covers it. Add a ROA for AS35608, maxLength 48.636 of 636
ROA: none2a09:3ec0:5::/48No ROA covers it. Add a ROA for AS35608, maxLength 48.636 of 636
ROA: none2a09:3ec0:8::/48No ROA covers it. Add a ROA for AS35608, maxLength 48.636 of 636
ROA: none2a09:3ec0:4::/48No ROA covers it. Add a ROA for AS35608, maxLength 48.1 of 636

Route objects not announced

Route objects with origin AS35608 whose prefix no peer sees AS35608 announce. Many are kept on purpose (backup routes, space announced only in some places).

171.22.212.0/22RIPENo ROA
171.22.212.0/23RIPENo ROA
171.22.214.0/23RIPENo ROA
2a09:3ec0::/29RIPENo ROA
2a09:3ec0:2::/48RIPENo ROA
2a09:3ec0:3::/48RIPENo ROA
2a09:3ec0:6::/48RIPENo ROA
2a09:3ec0:7::/48RIPENo ROA
2a09:3ec0:9::/48RIPENo 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.