Network · data from 2026-11-12

AS219207 AS-FUYANG-SIQIN

Registry name: AS-FUYANG-SIQIN YIYUAN CHEN, CN · PeeringDB

0IPv4 routes

14IPv6 routes 78.6% RPKI valid · 78.6% with a route object

1RPKI invalid 1 origin · 0 maxLength

2No ROA 3 with no route object for this origin

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

4Route objects not announced registered with origin AS219207, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS219207, 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:6281::/33	Invalid: origin	None	1 0%low visibility	1
2a0f:7304::/30	No ROA	None	3 0%low visibility	3
2a0f:7300::/30	No ROA	None	1 0%low visibility	1
2a07:e000:20::/44	Valid	RIR databaseRIPE	636 100%	67
2a0a:d682:e000::/36	Valid	RIR databaseRIPE	636 100%	67
2a0c:e641::/33	Valid	RIR databaseRIPE	636 100%	67
2a0e:4001:9800::/37	Valid	RIR databaseRIPE	636 100%	67
2a0f:6280:7800::/39	Valid	RIR databaseRIPE	636 100%	67
2602:fa02:d00::/40	Valid	RIR databaseARIN	635 100%	67
2a05:1086:8000::/33	Valid	RIR databaseRIPE	635 100%	67
2a06:de07:f800::/39	Valid	RIR databaseRIPE	635 100%	67
2a14:7581:5800::/40	Valid	RIR databaseRIPE	634 100%	67
2a09:3f00:4600::/39	Valid	RIR databaseRIPE	631 99%	67
2a0f:6280:7000::/39	Valid	RIR databaseRIPE	631 99%	67

2a0f:6281::/33

Invalid: origin

None

1 0%low visibility

2a0f:7304::/30

No ROA

None

3 0%low visibility

2a0f:7300::/30

No ROA

None

1 0%low visibility

2a07:e000:20::/44

Valid

RIR databaseRIPE

636 100%

2a0a:d682:e000::/36

Valid

RIR databaseRIPE

636 100%

2a0c:e641::/33

Valid

RIR databaseRIPE

636 100%

2a0e:4001:9800::/37

Valid

RIR databaseRIPE

636 100%

2a0f:6280:7800::/39

Valid

RIR databaseRIPE

636 100%

2602:fa02:d00::/40

Valid

RIR databaseARIN

635 100%

2a05:1086:8000::/33

Valid

RIR databaseRIPE

635 100%

2a06:de07:f800::/39

Valid

RIR databaseRIPE

635 100%

2a14:7581:5800::/40

Valid

RIR databaseRIPE

634 100%

2a09:3f00:4600::/39

Valid

RIR databaseRIPE

631 99%

2a0f:6280:7000::/39

Valid

RIR databaseRIPE

631 99%

AS-SET

AS219207's PeeringDB record names no 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 10 are in fix.csv.

ROA: origin1
ROA: none2
Route object: none3
Route object: not announced4

Change	Prefix or set	Detail	Full-table peers
ROA: origin	2a0f:6281::/33	ROAs covering it name AS218798, not AS219207. If AS219207 should announce it, add a ROA for AS219207.	1 of 636
Route object: none	2a0f:6281::/33	No route object for it. Add a route object with origin AS219207 in the RIR database for the space.	1 of 636
ROA: none	2a0f:7304::/30	No ROA covers it. Add a ROA for AS219207, maxLength 30.	3 of 636
Route object: none	2a0f:7304::/30	No route object for it. Add a route object with origin AS219207 in the RIR database for the space.	3 of 636
ROA: none	2a0f:7300::/30	No ROA covers it. Add a ROA for AS219207, maxLength 30.	1 of 636
Route object: none	2a0f:7300::/30	No route object for it. Add a route object with origin AS219207 in the RIR database for the space.	1 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: origin

2a0f:6281::/33

ROAs covering it name AS218798, not AS219207. If AS219207 should announce it, add a ROA for AS219207.

1 of 636

Route object: none

2a0f:6281::/33

No route object for it. Add a route object with origin AS219207 in the RIR database for the space.

1 of 636

ROA: none

2a0f:7304::/30

No ROA covers it. Add a ROA for AS219207, maxLength 30.

3 of 636

Route object: none

2a0f:7304::/30

No route object for it. Add a route object with origin AS219207 in the RIR database for the space.

3 of 636

ROA: none

2a0f:7300::/30

No ROA covers it. Add a ROA for AS219207, maxLength 30.

1 of 636

Route object: none

2a0f:7300::/30

No route object for it. Add a route object with origin AS219207 in the RIR database for the space.

1 of 636

Route objects not announced

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


2a06:de07:f800::/38	RIPE	Valid
2a0a:d687:ff02::/48	RIPE	Valid
2a10:fa81:e00::/40	RIPE	Valid
2a10:fa86:8000::/34	RIPE	Valid

2a06:de07:f800::/38

RIPE

Valid

2a0a:d687:ff02::/48

RIPE

Valid

2a10:fa81:e00::/40

RIPE

Valid

2a10:fa86:8000::/34

RIPE

Valid

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.