Network · data from 2026-11-12

AS18590 CHINETWORKS - Chi Networks

Registry name: CHINETWORKS - Chi Networks, US · not in PeeringDB

23IPv4 routes 100.0% RPKI valid · 100.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

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

28Route objects not announced registered with origin AS18590, seen from no peer

Announced routes

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


104.152.176.0/24	Valid	RIR databaseARIN	673 100%	67
104.152.178.0/24	Valid	RIR databaseARIN	673 100%	67
104.152.179.0/24	Valid	RIR databaseARIN	673 100%	67
162.213.188.0/24	Valid	RIR databaseARIN	673 100%	67
162.213.189.0/24	Valid	RIR databaseARIN	673 100%	67
162.213.190.0/24	Valid	RIR databaseARIN	673 100%	67
162.213.191.0/24	Valid	RIR databaseARIN, RADB	673 100%	67
162.222.33.0/24	Valid	RIR databaseARIN	673 100%	67
162.222.34.0/24	Valid	RIR databaseARIN	673 100%	67
162.222.35.0/24	Valid	RIR databaseARIN, RADB	673 100%	67
162.222.37.0/24	Valid	RIR databaseARIN, RADB	673 100%	67
162.222.39.0/24	Valid	RIR databaseARIN	673 100%	67
170.178.144.0/24	Valid	RIR databaseARIN	673 100%	67
170.178.146.0/24	Valid	RIR databaseARIN	673 100%	67
170.178.147.0/24	Valid	RIR databaseARIN	673 100%	67
204.80.89.0/24	Valid	RIR databaseARIN	673 100%	67
204.80.91.0/24	Valid	RIR databaseARIN	673 100%	67
204.80.92.0/24	Valid	RIR databaseARIN, RADB	673 100%	67
204.80.94.0/24	Valid	RIR databaseARIN	673 100%	67
204.80.95.0/24	Valid	RIR databaseARIN, RADB	673 100%	67
208.92.14.0/24	Valid	RIR databaseARIN	673 100%	67
208.92.15.0/24	Valid	RIR databaseARIN, RADB	673 100%	67
38.100.110.0/24	Valid	RIR databaseARIN	672 100%	67

AS-SET

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

Route object: not announced28

Route objects not announced

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


8.42.4.0/22	ARIN	No ROA
8.42.4.0/23	NTTCOM	No ROA
67.106.77.0/24	ARIN	No ROA
67.106.81.0/24	ARIN	No ROA
71.5.97.0/24	ARIN	No ROA
98.124.181.0/24	ARIN	No ROA
104.152.176.0/22	ARIN, NTTCOM	No ROA
104.152.177.0/24	ARIN	Valid
140.239.62.0/23	ARIN	No ROA
162.22.38.0/24	RADB	No ROA
162.22.39.0/24	RADB	No ROA
162.213.188.0/22	ARIN	No ROA
162.222.32.0/21	ARIN, RADB	No ROA
162.222.32.0/24	ARIN	Valid
162.222.36.0/24	ARIN, RADB	Valid
162.222.38.0/24	ARIN	Valid
170.178.144.0/22	ARIN, RADB	No ROA
170.178.145.0/24	ARIN	Valid
204.80.88.0/21	ARIN	No ROA
204.80.88.0/24	ARIN	Valid
204.80.90.0/24	ARIN	Valid
204.80.93.0/24	ARIN	Valid
207.88.55.0/24	ARIN	No ROA
208.92.12.0/22	ARIN	No ROA
208.92.12.0/24	ARIN	Valid
208.92.13.0/24	ARIN	Valid
209.211.220.0/24	NTTCOM	Valid
2001:470:20a::/48	ARIN	Invalid: origin

8.42.4.0/22

ARIN

No ROA

8.42.4.0/23

NTTCOM

No ROA

67.106.77.0/24

ARIN

No ROA

67.106.81.0/24

ARIN

No ROA

71.5.97.0/24

ARIN

No ROA

98.124.181.0/24

ARIN

No ROA

104.152.176.0/22

ARIN, NTTCOM

No ROA

104.152.177.0/24

ARIN

Valid

140.239.62.0/23

ARIN

No ROA

162.22.38.0/24

RADB

No ROA

162.22.39.0/24

RADB

No ROA

162.213.188.0/22

ARIN

No ROA

162.222.32.0/21

ARIN, RADB

No ROA

162.222.32.0/24

ARIN

Valid

162.222.36.0/24

ARIN, RADB

Valid

162.222.38.0/24

ARIN

Valid

170.178.144.0/22

ARIN, RADB

No ROA

170.178.145.0/24

ARIN

Valid

204.80.88.0/21

ARIN

No ROA

204.80.88.0/24

ARIN

Valid

204.80.90.0/24

ARIN

Valid

204.80.93.0/24

ARIN

Valid

207.88.55.0/24

ARIN

No ROA

208.92.12.0/22

ARIN

No ROA

208.92.12.0/24

ARIN

Valid

208.92.13.0/24

ARIN

Valid

209.211.220.0/24

NTTCOM

Valid

2001:470:20a::/48

ARIN

Invalid: origin

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.