bgpreport

Network · data from 2026-11-12

AS20071 KUXUEYUN-LLC

Registry name: KUXUEYUN-US - KUXUEYUN LLC, US · PeeringDB

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

Announced routes

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

2602:f66f:1::/48 No ROA None 633 100% 68
23.138.76.0/24 Valid RIR databaseARIN 673 100% 67
2602:f66f:10::/44 Valid RIR databaseARIN 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS20071: AS20071:AS-PEERS. 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 (AS20071 isn't in the set, or no route object for AS20071 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 objectsAS20071 in itNot covered
AS20071:AS-PEERS ARIN 010 No 3

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

  • ROA: none1
  • Route object: none1
  • AS-SET: own ASN1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none2602:f66f:1::/48No ROA covers it. Add a ROA for AS20071, maxLength 48.633 of 636
Route object: none2602:f66f:1::/48No route object for it. Add a route object with origin AS20071 in the RIR database for the space.633 of 636
AS-SET: own ASNAS20071:AS-PEERSAS20071 isn't in AS20071:AS-PEERS (ARIN) once expanded. Add AS20071 to it.

Route objects not announced

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

204.14.192.0/22RADBNo ROA
204.14.196.0/22RADBNo ROA
2602:f66f:f0::/44ARINNo ROA

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.