Network · data from 2026-11-12

AS214921 JudgeDuck Research and Development Network

Registry name: JudgeDuck-net Yisong Wang, CN · PeeringDB

0IPv4 routes

3IPv6 routes 100.0% RPKI valid · 33.3% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 2 with no route object for this origin

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

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

Announced routes

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


2a0e:aa06:500::/48	Valid	Nonecovered by 2a0e:aa06:500::/44	636 100%	68
2a0e:aa06:501::/48	Valid	Nonecovered by 2a0e:aa06:500::/44	636 100%	68
2a0e:aa06:500::/44	Valid	RIR databaseRADB, RIPE	636 100%	68

AS-SET

PeeringDB's irr_as_set for AS214921: AS214921:AS-CUSTOMERS. 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 (AS214921 isn't in the set, or no route object for AS214921 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	AS214921 in it	Not covered
AS214921:AS-CUSTOMERS	In no IRR database read today.

Name

Database

ASNs

Sets

Route objects

AS214921 in it

Not covered

AS214921:AS-CUSTOMERS

In no IRR database read today.

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.

Route object: none2
AS-SET: not found1

Change	Prefix or set	Detail	Full-table peers
Route object: none	2a0e:aa06:500::/48	No route object for it. A route object for 2a0e:aa06:500::/44 with origin AS214921 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214921 in the RIR database for the space.	636 of 636
Route object: none	2a0e:aa06:501::/48	No route object for it. A route object for 2a0e:aa06:500::/44 with origin AS214921 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214921 in the RIR database for the space.	636 of 636
AS-SET: not found	AS214921:AS-CUSTOMERS	PeeringDB names AS214921:AS-CUSTOMERS; no IRR database read has it.

Change

Prefix or set

Detail

Full-table peers

Route object: none

2a0e:aa06:500::/48

No route object for it. A route object for 2a0e:aa06:500::/44 with origin AS214921 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214921 in the RIR database for the space.

636 of 636

Route object: none

2a0e:aa06:501::/48

636 of 636

AS-SET: not found

AS214921:AS-CUSTOMERS

PeeringDB names AS214921:AS-CUSTOMERS; no IRR database read has it.

Route objects not announced

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