Network · data from 2026-11-12

AS219324 HUANGTIANDI

Registry name: GUOLIN-AS LI GUOLIN, CN · PeeringDB

1IPv4 routes 0.0% RPKI valid · 0.0% with a route object

0IPv6 routes

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 AS219324, seen from no peer

Announced routes

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


82.108.77.0/24	Invalid: origin	Other origin only	2 0%low visibility	1

82.108.77.0/24

Invalid: origin

Other origin only

2 0%low visibility

AS-SET

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

ROA: origin1
Route object: none1

Change	Prefix or set	Detail	Full-table peers
ROA: origin	82.108.77.0/24	ROAs covering it name AS137409, not AS219324. If AS219324 should announce it, add a ROA for AS219324.	2 of 673
Route object: none	82.108.77.0/24	Route objects for it name AS3257, AS137409. Add a route object with origin AS219324 in the RIR database for the space.	2 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: origin

82.108.77.0/24

ROAs covering it name AS137409, not AS219324. If AS219324 should announce it, add a ROA for AS219324.

2 of 673

Route object: none

82.108.77.0/24

Route objects for it name AS3257, AS137409. Add a route object with origin AS219324 in the RIR database for the space.

2 of 673

Route objects not announced

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