Network · data from 2026-11-12

AS20965 GEANT R&E

Registry name: GEANT GEANT Vereniging, NL · PeeringDB

2IPv4 routes 100.0% RPKI valid · 100.0% with a route object

3IPv6 routes 66.7% RPKI valid · 66.7% with a route object

1RPKI invalid 0 origin · 1 maxLength

0No ROA 1 with no route object for this origin

2Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS20965, seen from no peer

Announced routes

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


2001:798:3::/64	Invalid: maxLength	Nonecovered by 2001:798::/32	2 0%low visibility	2
62.40.96.0/19	Valid	RIR databaseRIPE	671 100%	68
2001:798::/32	Valid	RIR databaseRIPE	635 100%	68
2001:799::/32	Valid	RIR databaseRIPE	635 100%	68
83.97.92.0/22	Valid	RIR databaseRIPE	20 3%low visibility	18

2001:798:3::/64

Invalid: maxLength

Nonecovered by 2001:798::/32

2 0%low visibility

62.40.96.0/19

Valid

RIR databaseRIPE

671 100%

2001:798::/32

Valid

RIR databaseRIPE

635 100%

2001:799::/32

Valid

RIR databaseRIPE

635 100%

83.97.92.0/22

Valid

RIR databaseRIPE

20 3%low visibility

AS-SET

PeeringDB's irr_as_set for AS20965: AS-GEANTNRN. 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 (AS20965 isn't in the set, or no route object for AS20965 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.

Name	Database	ASNs	Sets	Route objects	AS20965 in it	Not covered
AS-GEANTNRN	RIPElists itself further down1 member set in no database: AS-SARIMNER	915	123	18,374	Yes	1

Name

Database

ASNs

Sets

Route objects

AS20965 in it

Not covered

AS-GEANTNRN

RIPElists itself further down1 member set in no database: AS-SARIMNER

915

123

18,374

Yes

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

ROA: maxLength1
Route object: none1
AS-SET: missing member1

Change	Prefix or set	Detail	Full-table peers
ROA: maxLength	2001:798:3::/64	ROA 2001:798::/32 AS20965 has maxLength 32; the route is a /64. Raise the maxLength, or add a ROA for 2001:798:3::/64.	2 of 636
Route object: none	2001:798:3::/64	No route object for it. A route object for 2001:798::/32 with origin AS20965 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS20965 in the RIR database for the space.	2 of 636
AS-SET: missing member	AS-GEANTNRN	AS-GEANTNRN (RIPE) lists AS-SARIMNER; no IRR database read has it.

Change

Prefix or set

Detail

Full-table peers

ROA: maxLength

2001:798:3::/64

ROA 2001:798::/32 AS20965 has maxLength 32; the route is a /64. Raise the maxLength, or add a ROA for 2001:798:3::/64.

2 of 636

Route object: none

2001:798:3::/64

No route object for it. A route object for 2001:798::/32 with origin AS20965 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS20965 in the RIR database for the space.

2 of 636

AS-SET: missing member

AS-GEANTNRN

AS-GEANTNRN (RIPE) lists AS-SARIMNER; no IRR database read has it.

Route objects not announced

Every route object with origin AS20965 is announced.

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.