bgpreport

Network · data from 2026-11-12

AS214610 YANGXULIAO YangXu Liao

Registry name: YANGXULIAO YangXu Liao, CN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS214610, 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.
2a0f:6284:400::/44 Valid Other IRR onlyRADB 635 100% 68
2a0f:6284:410::/44 Valid Other IRR onlyRADB 635 100% 68
2a0f:6284:420::/44 Valid Other IRR onlyRADB 635 100% 68
2a0f:6284:430::/44 Valid Other IRR onlyRADB 635 100% 68
2a0f:6284:440::/44 Valid Other IRR onlyRADB 635 100% 68
2a0f:6284:450::/44 Valid Other IRR onlyRADB 635 100% 68
2a0f:6284:300::/40 Valid RIR databaseRADB, RIPE 635 100% 68
2a0f:6284:3000::/40 Valid RIR databaseRIPE 2 0%low visibility 2
2a0f:6284:3100::/40 Valid RIR databaseRIPE 2 0%low visibility 2
2a0f:6284:4f00::/40 Valid RIR databaseRIPE 2 0%low visibility 2
2a0f:6284:e000::/36 Valid RIR databaseRIPE 2 0%low visibility 2
2a0f:6284:f000::/36 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

AS214610 isn't in PeeringDB, where networks name their AS-SET.

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

  • Route object: RIR6
  • Route object: not announced19
ChangePrefix or setDetailFull-table peers
Route object: RIR2a0f:6284:400::/44Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2a0f:6284:410::/44Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2a0f:6284:420::/44Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2a0f:6284:430::/44Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2a0f:6284:440::/44Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2a0f:6284:450::/44Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

2a0f:6284:400::/40RIPEValid
2a0f:6284:4d00::/40RIPEValid
2a0f:6284:4e00::/40RIPEValid
2a0f:7803:f5d0::/44RADBNo ROA
2a0f:7803:f5e0::/44RADBNo ROA
2a0f:7803:f5f0::/44RADBNo ROA
2a0f:7803:f690::/44RADBNo ROA
2a0f:7803:f6a0::/44RADBNo ROA
2a0f:7803:f7c0::/44RADBNo ROA
2a0f:7803:f7d0::/44RADBNo ROA
2a0f:7803:f7e0::/44RADBNo ROA
2a0f:7803:f7f0::/44RADBNo ROA
2a0f:7803:f800::/44RADBNo ROA
2a0f:7803:f810::/44RADBNo ROA
2a0f:7803:f840::/44RADBNo ROA
2a0f:7803:f860::/44RADBNo ROA
2a0f:7803:f8b0::/44RADBNo ROA
2a0f:7803:f970::/44RADBNo ROA
2a0f:85c1:ca0::/44RADBValid

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.