bgpreport

Network · data from 2026-11-12

AS8790 PETRSU-AS Federal State Budgetary Educational Institution of Higher Education "Petrozavodsk State University"

Registry name: PETRSU-AS Federal State Budgetary Educational Institution of Higher Education "Petrozavodsk State University", RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS8790, 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.
193.232.254.0/24 No ROA RIR databaseRIPE 672 100% 66
195.209.248.0/23 Valid RIR databaseRIPE 673 100% 66
194.85.173.0/24 Valid RIR databaseRIPE 672 100% 66
194.85.172.0/24 Valid RIR databaseRIPE 78 12% 26

AS-SET

AS8790 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: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none193.232.254.0/24No ROA covers it. Add a ROA for AS8790, maxLength 24.672 of 673

Route objects not announced

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

194.85.172.0/23RIPEValid
2001:b08:24::/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.