bgpreport

Network · data from 2026-11-12

AS8670 University of Sarajevo

Registry name: UTIC_Autonomus_System University of Sarajevo, BA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS8670, 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.

195.130.38.0/24 No ROA Nonecovered by 195.130.32.0/19 113 17% 44
195.130.35.0/24 No ROA RIR databaseRIPE 673 100% 67
195.130.37.0/24 No ROA RIR databaseRIPE 673 100% 67
195.130.43.0/24 No ROA RIR databaseRIPE 673 100% 67
195.130.50.0/24 No ROA RIR databaseRIPE 673 100% 67
195.130.53.0/24 No ROA RIR databaseRIPE 673 100% 67
195.130.60.0/24 No ROA RIR databaseRIPE 673 100% 67
195.130.61.0/24 No ROA RIR databaseRIPE 673 100% 67
195.130.62.0/24 No ROA RIR databaseRIPE 673 100% 67
195.130.32.0/19 No ROA RIR databaseRIPE 671 100% 68
195.130.34.0/24 No ROA RIR databaseRIPE 671 100% 67
195.130.40.0/24 No ROA RIR databaseRIPE 671 100% 67
2a03:3320:4::/48 No ROA RIR databaseRIPE 636 100% 68

AS-SET

AS8670's PeeringDB record names no 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 22 are in fix.csv.

  • ROA: none13
  • Route object: none1
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none195.130.38.0/24No ROA covers it. Add a ROA for AS8670, maxLength 24.113 of 673
Route object: none195.130.38.0/24No route object for it. A route object for 195.130.32.0/19 with origin AS8670 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8670 in the RIR database for the space.113 of 673
ROA: none195.130.35.0/24No ROA covers it. Add a ROA for AS8670, maxLength 24.673 of 673
ROA: none195.130.37.0/24No ROA covers it. Add a ROA for AS8670, maxLength 24.673 of 673
ROA: none195.130.43.0/24No ROA covers it. Add a ROA for AS8670, maxLength 24.673 of 673
ROA: none195.130.50.0/24No ROA covers it. Add a ROA for AS8670, maxLength 24.673 of 673
ROA: none195.130.53.0/24No ROA covers it. Add a ROA for AS8670, maxLength 24.673 of 673
ROA: none195.130.60.0/24No ROA covers it. Add a ROA for AS8670, maxLength 24.673 of 673
ROA: none195.130.61.0/24No ROA covers it. Add a ROA for AS8670, maxLength 24.673 of 673
ROA: none195.130.62.0/24No ROA covers it. Add a ROA for AS8670, maxLength 24.673 of 673
ROA: none195.130.32.0/19No ROA covers it. Add a ROA for AS8670, maxLength 19.671 of 673
ROA: none195.130.34.0/24No ROA covers it. Add a ROA for AS8670, maxLength 24.671 of 673
ROA: none195.130.40.0/24No ROA covers it. Add a ROA for AS8670, maxLength 24.671 of 673
ROA: none2a03:3320:4::/48No ROA covers it. Add a ROA for AS8670, maxLength 48.636 of 636

Route objects not announced

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

195.130.32.0/24RIPENo ROA
195.130.33.0/24RIPENo ROA
195.130.41.0/24RIPENo ROA
195.130.44.0/24RIPENo ROA
195.130.47.0/24RIPENo ROA
195.130.48.0/24RIPENo ROA
195.130.49.0/24RIPENo ROA
195.130.51.0/24RIPENo 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.