bgpreport

Network · data from 2026-11-12

AS214930 finitud labs research network

Registry name: FINITUD-LABS-AS Alice Wyan Garcia Martin, ES · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS214930, 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.
44.32.90.0/24 No ROA Other IRR onlyRADB 672 100% 66
2a05:dfc1:1480::/41 No ROA RIR databaseRADB, RIPE 636 100% 69
2a0a:6044:b7a0::/44 Valid Nonecovered by 2a0a:6044:b700::/40 1 0%low visibility 2
2a0a:6044:b7c0::/44 Valid Nonecovered by 2a0a:6044:b700::/40 1 0%low visibility 2
2a07:54c1:c400::/40 Valid RIR databaseRADB, RIPE 636 100% 69
2a0a:6044:b700::/40 Valid RIR databaseRIPE 636 100% 69
2a0e:8f02:f06f::/48 Valid RIR databaseRADB, RIPE 636 100% 69

AS-SET

PeeringDB's irr_as_set for AS214930: AS214930:AS-FINITUD-LABS. 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 (AS214930 isn't in the set, or no route object for AS214930 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 objectsAS214930 in itNot covered
AS214930:AS-FINITUD-LABS RIPE 117 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 7 are in fix.csv.

  • ROA: none2
  • Route object: none2
  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none44.32.90.0/24No ROA covers it. Add a ROA for AS214930, maxLength 24.672 of 673
Route object: RIR44.32.90.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none2a05:dfc1:1480::/41No ROA covers it. Add a ROA for AS214930, maxLength 41.636 of 636
Route object: none2a0a:6044:b7a0::/44No route object for it. A route object for 2a0a:6044:b700::/40 with origin AS214930 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214930 in the RIR database for the space.1 of 636
Route object: none2a0a:6044:b7c0::/44No route object for it. A route object for 2a0a:6044:b700::/40 with origin AS214930 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214930 in the RIR database for the space.1 of 636

Route objects not announced

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

2602:fbe6:200::/39ARINNo ROA
2a07:54c1:c4fe::/48RIPEValid

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.