bgpreport

Network · data from 2026-11-12

AS197919 Noah van der Aa

Registry name: NOAHVDAA-AS Noah van der Aa, NL · PeeringDB

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

Announced routes

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

2a05:dfc1:6200::/48 Valid Nonecovered by 2a05:dfc1:6200::/40 636 100% 69
2a05:dfc1:6299::/48 Valid Nonecovered by 2a05:dfc1:6200::/40 636 100% 69
2a05:dfc1:62c9::/48 Valid Nonecovered by 2a05:dfc1:6200::/40 636 100% 69
2a05:dfc1:62ff::/48 Valid Nonecovered by 2a05:dfc1:6200::/40 636 100% 69
2a05:dfc1:6260::/46 Valid Nonecovered by 2a05:dfc1:6200::/40 635 100% 69
2a05:dfc1:62b0::/44 Valid Nonecovered by 2a05:dfc1:6200::/40 2 0%low visibility 2
2a05:dfc1:62a3::/48 Valid Nonecovered by 2a05:dfc1:6200::/40 1 0%low visibility 1
2a05:dfc1:6201::/48 Valid RIR databaseRIPE 636 100% 69

AS-SET

PeeringDB's irr_as_set for AS197919: AS197919:AS-NOAHVDAA. 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 (AS197919 isn't in the set, or no route object for AS197919 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 objectsAS197919 in itNot covered
AS197919:AS-NOAHVDAA RIPE 114 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 10 are in fix.csv.

  • Route object: none7
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: none2a05:dfc1:6200::/48No route object for it. A route object for 2a05:dfc1:6200::/40 with origin AS197919 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197919 in the RIR database for the space.636 of 636
Route object: none2a05:dfc1:6299::/48No route object for it. A route object for 2a05:dfc1:6200::/40 with origin AS197919 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197919 in the RIR database for the space.636 of 636
Route object: none2a05:dfc1:62c9::/48No route object for it. A route object for 2a05:dfc1:6200::/40 with origin AS197919 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197919 in the RIR database for the space.636 of 636
Route object: none2a05:dfc1:62ff::/48No route object for it. A route object for 2a05:dfc1:6200::/40 with origin AS197919 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197919 in the RIR database for the space.636 of 636
Route object: none2a05:dfc1:6260::/46No route object for it. A route object for 2a05:dfc1:6200::/40 with origin AS197919 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197919 in the RIR database for the space.635 of 636
Route object: none2a05:dfc1:62b0::/44No route object for it. A route object for 2a05:dfc1:6200::/40 with origin AS197919 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197919 in the RIR database for the space.2 of 636
Route object: none2a05:dfc1:62a3::/48No route object for it. A route object for 2a05:dfc1:6200::/40 with origin AS197919 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197919 in the RIR database for the space.1 of 636

Route objects not announced

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

2a05:dfc1:6200::/40RIPEValid
2a0e:b107:27c8::/45RIPENo ROA
2a14:6f44:b00b::/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.