bgpreport

Network · data from 2026-11-12

AS21320 GEANT IAS

Registry name: GEANT_IAS_VRF GEANT Vereniging, NL · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS21320, 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:1::/48 Invalid: origin None 2 0%low visibility 2
83.97.88.0/21 Valid RIR databaseRIPE 673 100% 67

AS-SET

PeeringDB's irr_as_set for AS21320: AS-GEANT-EUPEER. 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 (AS21320 isn't in the set, or no route object for AS21320 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 objectsAS21320 in itNot covered
AS-GEANT-EUPEER RIPElists itself further down 81910617,560 Yes 1

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

  • ROA: origin1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: origin2001:798:1::/48ROAs covering it name AS20965, not AS21320. If AS21320 should announce it, add a ROA for AS21320.2 of 636
Route object: none2001:798:1::/48No route object for it. Add a route object with origin AS21320 in the RIR database for the space.2 of 636

Route objects not announced

Every route object with origin AS21320 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.