Network · data from 2026-11-12

AS37969 AIDC-CN

Registry name: AIDC-CN - Zhejiang WuLian Network Technology Co.,Ltd., CN · PeeringDB

6IPv4 routes 100.0% RPKI valid · 66.7% with a route object

2IPv6 routes 100.0% RPKI valid · 50.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 3 with no route object for this origin

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

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

Announced routes

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


157.15.94.0/24	Valid	Nonecovered by 157.15.94.0/23	32 5%low visibility	19
157.15.95.0/24	Valid	Nonecovered by 157.15.94.0/23	32 5%low visibility	19
2400:8fc0:571::/48	Valid	Nonecovered by 2400:8fc0::/32	26 4%low visibility	16
157.15.94.0/23	Valid	RIR databaseAPNIC, RADB	35 5%low visibility	19
103.83.64.0/22	Valid	RIR databaseAPNIC, RADB	29 4%low visibility	18
103.98.92.0/22	Valid	RIR databaseAPNIC, RADB	29 4%low visibility	18
103.98.96.0/22	Valid	RIR databaseAPNIC, RADB	29 4%low visibility	18
2400:8fc0::/32	Valid	RIR databaseAPNIC, RADB	22 3%low visibility	14

157.15.94.0/24

Valid

Nonecovered by 157.15.94.0/23

32 5%low visibility

157.15.95.0/24

Valid

Nonecovered by 157.15.94.0/23

32 5%low visibility

2400:8fc0:571::/48

Valid

Nonecovered by 2400:8fc0::/32

26 4%low visibility

157.15.94.0/23

Valid

RIR databaseAPNIC, RADB

35 5%low visibility

103.83.64.0/22

Valid

RIR databaseAPNIC, RADB

29 4%low visibility

103.98.92.0/22

Valid

RIR databaseAPNIC, RADB

29 4%low visibility

103.98.96.0/22

Valid

RIR databaseAPNIC, RADB

29 4%low visibility

2400:8fc0::/32

Valid

RIR databaseAPNIC, RADB

22 3%low visibility

AS-SET

AS37969'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 3 are in fix.csv.

Route object: none3

Change	Prefix or set	Detail	Full-table peers
Route object: none	157.15.94.0/24	No route object for it. A route object for 157.15.94.0/23 with origin AS37969 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37969 in the RIR database for the space.	32 of 673
Route object: none	157.15.95.0/24	No route object for it. A route object for 157.15.94.0/23 with origin AS37969 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37969 in the RIR database for the space.	32 of 673
Route object: none	2400:8fc0:571::/48	No route object for it. A route object for 2400:8fc0::/32 with origin AS37969 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37969 in the RIR database for the space.	26 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

157.15.94.0/24

No route object for it. A route object for 157.15.94.0/23 with origin AS37969 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37969 in the RIR database for the space.

32 of 673

Route object: none

157.15.95.0/24

32 of 673

Route object: none

2400:8fc0:571::/48

No route object for it. A route object for 2400:8fc0::/32 with origin AS37969 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37969 in the RIR database for the space.

26 of 636

Route objects not announced

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