bgpreport

Network · data from 2026-11-12

AS61360 NOVOCHEK-AS Special Engineering and Design Bureau "Orbita" JSC

Registry name: NOVOCHEK-AS Special Engineering and Design Bureau "Orbita" JSC, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS61360, 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.243.96.0/24 No ROA RIR databaseRIPE 673 100% 66
91.243.97.0/24 No ROA RIR databaseRIPE 673 100% 66
91.243.98.0/24 No ROA RIR databaseRIPE 673 100% 66
91.243.99.0/24 No ROA RIR databaseRIPE 673 100% 67
91.243.100.0/24 No ROA RIR databaseRIPE 673 100% 66
91.243.101.0/24 No ROA RIR databaseRIPE 673 100% 66
91.243.102.0/24 No ROA RIR databaseRIPE 673 100% 67
91.243.103.0/24 No ROA RIR databaseRIPE 673 100% 67
91.243.104.0/24 No ROA RIR databaseRIPE 673 100% 66
91.243.105.0/24 No ROA RIR databaseRIPE 673 100% 66
91.243.106.0/24 No ROA RIR databaseRIPE 673 100% 67
91.243.107.0/24 No ROA RIR databaseRIPE 673 100% 66
91.243.108.0/24 No ROA RIR databaseRIPE 673 100% 67
91.243.109.0/24 No ROA RIR databaseRIPE 673 100% 66
91.243.110.0/24 No ROA RIR databaseRIPE 673 100% 67
91.243.111.0/24 No ROA RIR databaseRIPE 673 100% 66
91.243.96.0/20 No ROA RIR databaseRIPE 672 100% 67

AS-SET

AS61360 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 32 are in fix.csv.

  • ROA: none17
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
ROA: none91.243.96.0/24No ROA covers it. Add a ROA for AS61360, maxLength 24.673 of 673
ROA: none91.243.97.0/24No ROA covers it. Add a ROA for AS61360, maxLength 24.673 of 673
ROA: none91.243.98.0/24No ROA covers it. Add a ROA for AS61360, maxLength 24.673 of 673
ROA: none91.243.99.0/24No ROA covers it. Add a ROA for AS61360, maxLength 24.673 of 673
ROA: none91.243.100.0/24No ROA covers it. Add a ROA for AS61360, maxLength 24.673 of 673
ROA: none91.243.101.0/24No ROA covers it. Add a ROA for AS61360, maxLength 24.673 of 673
ROA: none91.243.102.0/24No ROA covers it. Add a ROA for AS61360, maxLength 24.673 of 673
ROA: none91.243.103.0/24No ROA covers it. Add a ROA for AS61360, maxLength 24.673 of 673
ROA: none91.243.104.0/24No ROA covers it. Add a ROA for AS61360, maxLength 24.673 of 673
ROA: none91.243.105.0/24No ROA covers it. Add a ROA for AS61360, maxLength 24.673 of 673
ROA: none91.243.106.0/24No ROA covers it. Add a ROA for AS61360, maxLength 24.673 of 673
ROA: none91.243.107.0/24No ROA covers it. Add a ROA for AS61360, maxLength 24.673 of 673
ROA: none91.243.108.0/24No ROA covers it. Add a ROA for AS61360, maxLength 24.673 of 673
ROA: none91.243.109.0/24No ROA covers it. Add a ROA for AS61360, maxLength 24.673 of 673
ROA: none91.243.110.0/24No ROA covers it. Add a ROA for AS61360, maxLength 24.673 of 673
ROA: none91.243.111.0/24No ROA covers it. Add a ROA for AS61360, maxLength 24.673 of 673
ROA: none91.243.96.0/20No ROA covers it. Add a ROA for AS61360, maxLength 20.672 of 673

Route objects not announced

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

91.243.96.0/21RIPENo ROA
91.243.96.0/22RIPENo ROA
91.243.96.0/23RIPENo ROA
91.243.98.0/23RIPENo ROA
91.243.100.0/22RIPENo ROA
91.243.100.0/23RIPENo ROA
91.243.102.0/23RIPENo ROA
91.243.104.0/21RIPENo ROA
91.243.104.0/22RIPENo ROA
91.243.104.0/23RIPENo ROA
91.243.106.0/23RIPENo ROA
91.243.108.0/22RIPENo ROA
91.243.108.0/23RIPENo ROA
91.243.110.0/23RIPENo ROA
137.22.136.0/22RIPEValid

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.