bgpreport

Network · data from 2026-11-12

AS198345 VUB-AS Viesoji istaiga "Vilniaus universiteto bustas"

Registry name: VUB-AS Viesoji istaiga "Vilniaus universiteto bustas", LT · not in PeeringDB

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

Announced routes

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

2a09:d640::/30 Invalid: maxLength Nonecovered by 2a09:d640::/29 26 4%low visibility 20
2a09:d644::/30 Invalid: maxLength Nonecovered by 2a09:d640::/29 26 4%low visibility 20
2001:4048:105::/48 No ROA None 336 53% 64
2a0e:5080::/30 No ROA None 28 4%low visibility 21
2a0e:5084::/30 No ROA None 28 4%low visibility 21
91.233.176.0/22 No ROA RIR databaseRIPE 673 100% 66
194.28.232.0/22 No ROA RIR databaseRIPE 672 100% 66
84.32.160.0/22 Valid RIR databaseRIPE 673 100% 66

AS-SET

AS198345 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 20 are in fix.csv.

  • ROA: maxLength2
  • ROA: none5
  • Route object: none5
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: maxLength2a09:d640::/30ROA 2a09:d640::/29 AS198345 has maxLength 29; the route is a /30. Raise the maxLength, or add a ROA for 2a09:d640::/30.26 of 636
Route object: none2a09:d640::/30No route object for it. A route object for 2a09:d640::/29 with origin AS198345 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198345 in the RIR database for the space.26 of 636
ROA: maxLength2a09:d644::/30ROA 2a09:d640::/29 AS198345 has maxLength 29; the route is a /30. Raise the maxLength, or add a ROA for 2a09:d644::/30.26 of 636
Route object: none2a09:d644::/30No route object for it. A route object for 2a09:d640::/29 with origin AS198345 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198345 in the RIR database for the space.26 of 636
ROA: none2001:4048:105::/48No ROA covers it. Add a ROA for AS198345, maxLength 48.336 of 636
Route object: none2001:4048:105::/48No route object for it. Add a route object with origin AS198345 in the RIR database for the space.336 of 636
ROA: none2a0e:5080::/30No ROA covers it. Add a ROA for AS198345, maxLength 30.28 of 636
Route object: none2a0e:5080::/30No route object for it. Add a route object with origin AS198345 in the RIR database for the space.28 of 636
ROA: none2a0e:5084::/30No ROA covers it. Add a ROA for AS198345, maxLength 30.28 of 636
Route object: none2a0e:5084::/30No route object for it. Add a route object with origin AS198345 in the RIR database for the space.28 of 636
ROA: none91.233.176.0/22No ROA covers it. Add a ROA for AS198345, maxLength 22.673 of 673
ROA: none194.28.232.0/22No ROA covers it. Add a ROA for AS198345, maxLength 22.672 of 673

Route objects not announced

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

84.32.160.0/23RIPEValid
84.32.160.0/24RIPEValid
84.32.161.0/24RIPEValid
84.32.162.0/23RIPEValid
84.32.162.0/24RIPEValid
84.32.163.0/24RIPEValid
2001:678:fc::/48RIPENo ROA
2a09:d640::/29RIPEValid

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.