bgpreport

Network · data from 2026-11-12

AS2643 IHEP-SU Federal State Budgetary Institution "Institute of High Energy Physics named after A.A.Logunov of National Research Center "Kurchatov Institute"

Registry name: IHEP-SU Federal State Budgetary Institution "Institute of High Energy Physics named after A.A.Logunov of National Research Center "Kurchatov Institute", EU · not in PeeringDB

4IPv4 routes 25.0% RPKI valid · 100.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
3No 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 AS2643, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS2643, 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.
144.206.136.0/21 No ROA RIR databaseRIPE 673 100% 66
192.102.229.0/24 No ROA RIR databaseRIPE 673 100% 66
192.160.233.0/24 No ROA RIR databaseRIPE 673 100% 66
194.190.160.0/21 Valid RIR databaseRIPE 673 100% 66
2001:678:7d8::/48 Valid RIR databaseRIPE 636 100% 67

AS-SET

AS2643 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 3 are in fix.csv.

  • ROA: none3
ChangePrefix or setDetailFull-table peers
ROA: none144.206.136.0/21No ROA covers it. Add a ROA for AS2643, maxLength 21.673 of 673
ROA: none192.102.229.0/24No ROA covers it. Add a ROA for AS2643, maxLength 24.673 of 673
ROA: none192.160.233.0/24No ROA covers it. Add a ROA for AS2643, maxLength 24.673 of 673

Route objects not announced

Every route object with origin AS2643 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.