bgpreport

Network · data from 2026-11-12

AS197451 Brno University of Technology

Registry name: VUTBR-AS Brno University of Technology, CZ · PeeringDB

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

Announced routes

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

185.149.204.0/22 No ROA RIR databaseRIPE 673 100% 67
185.149.204.0/24 No ROA RIR databaseRIPE 673 100% 67
185.149.205.0/24 No ROA RIR databaseRIPE 673 100% 67
2a07:6bc0::/29 No ROA RIR databaseRIPE 634 100% 67
147.229.0.0/17 Valid RIR databaseRADB, RIPE 673 100% 67
147.229.128.0/18 Valid RIR databaseRADB, RIPE 673 100% 67
147.229.224.0/19 Valid RIR databaseRADB, RIPE 673 100% 67
185.62.108.0/23 Valid RIR databaseRIPE 673 100% 67
147.229.192.0/19 Valid RIR databaseRADB, RIPE 672 100% 67
2001:67c:1220::/46 Valid RIR databaseRIPE 635 100% 70
2a03:2e0::/32 Valid RIR databaseRIPE 635 100% 67
2a03:2e4::/30 Valid RIR databaseRIPE 634 100% 70

AS-SET

PeeringDB's irr_as_set for AS197451: AS-VUTBR. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS197451 isn't in the set, or no route object for AS197451 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS197451 in itNot covered
AS-VUTBR RIPE 385238 Yes 0

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

  • ROA: none4
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none185.149.204.0/22No ROA covers it. Add a ROA for AS197451, maxLength 22.673 of 673
ROA: none185.149.204.0/24No ROA covers it. Add a ROA for AS197451, maxLength 24.673 of 673
ROA: none185.149.205.0/24No ROA covers it. Add a ROA for AS197451, maxLength 24.673 of 673
ROA: none2a07:6bc0::/29No ROA covers it. Add a ROA for AS197451, maxLength 29.634 of 636

Route objects not announced

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

147.229.0.0/16RADB, RIPENo ROA
147.229.240.0/21RADBValid
147.229.240.0/23RADB, RIPEValid
147.229.242.0/23RADB, RIPEValid
185.149.207.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.