bgpreport

Network · data from 2026-11-12

AS35816 SEVSTAR Lancom Ltd.

Registry name: SEVSTAR Lancom Ltd., RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS35816, 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.
5.149.208.0/20 No ROA RIR databaseRIPE 672 100% 66
31.28.224.0/19 No ROA RIR databaseRIPE 672 100% 66
37.139.96.0/20 No ROA RIR databaseRIPE 672 100% 66
46.35.224.0/19 No ROA RIR databaseRIPE 672 100% 66
78.30.192.0/18 No ROA RIR databaseRIPE 672 100% 66
91.200.44.0/22 No ROA RIR databaseRIPE 672 100% 66
91.207.146.0/23 No ROA RIR databaseRIPE 672 100% 66
91.215.248.0/22 No ROA RIR databaseRIPE 672 100% 66
91.218.28.0/22 No ROA RIR databaseRIPE 672 100% 67
130.255.128.0/20 No ROA RIR databaseRIPE 672 100% 66
178.219.240.0/20 No ROA RIR databaseRIPE 672 100% 66
185.16.28.0/22 No ROA RIR databaseRIPE 672 100% 66
185.153.132.0/22 No ROA RIR databaseRIPE 672 100% 66
194.12.96.0/19 No ROA RIR databaseRIPE 672 100% 66
109.110.64.0/19 No ROA RIR databaseRIPE 669 99% 66
2a02:2b18::/32 No ROA RIR databaseRIPE 635 100% 68

AS-SET

AS35816 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 16 are in fix.csv.

  • ROA: none16
ChangePrefix or setDetailFull-table peers
ROA: none5.149.208.0/20No ROA covers it. Add a ROA for AS35816, maxLength 20.672 of 673
ROA: none31.28.224.0/19No ROA covers it. Add a ROA for AS35816, maxLength 19.672 of 673
ROA: none37.139.96.0/20No ROA covers it. Add a ROA for AS35816, maxLength 20.672 of 673
ROA: none46.35.224.0/19No ROA covers it. Add a ROA for AS35816, maxLength 19.672 of 673
ROA: none78.30.192.0/18No ROA covers it. Add a ROA for AS35816, maxLength 18.672 of 673
ROA: none91.200.44.0/22No ROA covers it. Add a ROA for AS35816, maxLength 22.672 of 673
ROA: none91.207.146.0/23No ROA covers it. Add a ROA for AS35816, maxLength 23.672 of 673
ROA: none91.215.248.0/22No ROA covers it. Add a ROA for AS35816, maxLength 22.672 of 673
ROA: none91.218.28.0/22No ROA covers it. Add a ROA for AS35816, maxLength 22.672 of 673
ROA: none130.255.128.0/20No ROA covers it. Add a ROA for AS35816, maxLength 20.672 of 673
ROA: none178.219.240.0/20No ROA covers it. Add a ROA for AS35816, maxLength 20.672 of 673
ROA: none185.16.28.0/22No ROA covers it. Add a ROA for AS35816, maxLength 22.672 of 673
ROA: none185.153.132.0/22No ROA covers it. Add a ROA for AS35816, maxLength 22.672 of 673
ROA: none194.12.96.0/19No ROA covers it. Add a ROA for AS35816, maxLength 19.672 of 673
ROA: none109.110.64.0/19No ROA covers it. Add a ROA for AS35816, maxLength 19.669 of 673
ROA: none2a02:2b18::/32No ROA covers it. Add a ROA for AS35816, maxLength 32.635 of 636

Route objects not announced

Every route object with origin AS35816 is announced.

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.