Network · data from 2026-11-12

AS150895 EZTECH-VN - EZ TECHNOLOGY COMPANY LIMITED

Registry name: EZTECH-VN - EZ TECHNOLOGY COMPANY LIMITED, VN · not in PeeringDB

49IPv4 routes 98.0% RPKI valid · 98.0% with a route object

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

0RPKI invalid 0 origin · 0 maxLength

1No ROA 1 with no route object for this origin

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

16Route objects not announced registered with origin AS150895, seen from no peer

Announced routes

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


163.227.230.0/23	No ROA	None	672 100%	67
103.14.48.0/23	Valid	RIR databaseAPNIC	673 100%	66
103.14.48.0/24	Valid	RIR databaseAPNIC	673 100%	66
103.14.49.0/24	Valid	RIR databaseAPNIC	673 100%	66
103.20.102.0/24	Valid	RIR databaseAPNIC	673 100%	66
103.20.103.0/24	Valid	RIR databaseAPNIC	673 100%	66
103.67.162.0/23	Valid	RIR databaseAPNIC	673 100%	66
103.75.76.0/23	Valid	RIR databaseAPNIC	673 100%	66
103.77.208.0/23	Valid	RIR databaseAPNIC	673 100%	66
103.78.2.0/23	Valid	RIR databaseAPNIC	673 100%	66
103.116.52.0/24	Valid	RIR databaseAPNIC	673 100%	66
157.66.48.0/23	Valid	RIR databaseAPNIC	673 100%	66
157.66.222.0/23	Valid	RIR databaseAPNIC	673 100%	66
157.66.224.0/23	Valid	RIR databaseAPNIC	673 100%	66
160.22.120.0/23	Valid	RIR databaseAPNIC	673 100%	66
160.25.72.0/23	Valid	RIR databaseAPNIC	673 100%	66
160.250.4.0/23	Valid	RIR databaseAPNIC	673 100%	66
160.250.132.0/23	Valid	RIR databaseAPNIC	673 100%	66
161.248.4.0/23	Valid	RIR databaseAPNIC	673 100%	66
202.158.248.0/23	Valid	RIR databaseAPNIC	673 100%	66
202.158.248.0/24	Valid	RIR databaseAPNIC	673 100%	66
202.158.249.0/24	Valid	RIR databaseAPNIC	673 100%	66
103.116.53.0/24	Valid	RIR databaseAPNIC	672 100%	67
160.22.81.0/24	Valid	RIR databaseAPNIC	672 100%	66
103.72.56.0/23	Valid	RIR databaseAPNIC	669 99%	67
103.152.164.0/23	Valid	RIR databaseAPNIC	669 99%	67
103.152.164.0/24	Valid	RIR databaseAPNIC	669 99%	67
103.152.165.0/24	Valid	RIR databaseAPNIC	669 99%	67
103.161.172.0/24	Valid	RIR databaseAPNIC	669 99%	67
103.173.66.0/23	Valid	RIR databaseAPNIC	669 99%	67
103.173.66.0/24	Valid	RIR databaseAPNIC	669 99%	67
103.173.67.0/24	Valid	RIR databaseAPNIC	669 99%	67
160.22.80.0/24	Valid	RIR databaseAPNIC	669 99%	67
160.30.50.0/23	Valid	RIR databaseAPNIC	669 99%	67
160.30.136.0/23	Valid	RIR databaseAPNIC	669 99%	67
160.191.86.0/23	Valid	RIR databaseAPNIC	669 99%	67
160.191.160.0/24	Valid	RIR databaseAPNIC	669 99%	67
160.191.214.0/23	Valid	RIR databaseAPNIC	669 99%	67
160.250.128.0/23	Valid	RIR databaseAPNIC	669 99%	67
160.250.180.0/23	Valid	RIR databaseAPNIC	669 99%	67
160.250.186.0/23	Valid	RIR databaseAPNIC	669 99%	67
161.248.238.0/23	Valid	RIR databaseAPNIC	669 99%	67
163.61.72.0/23	Valid	RIR databaseAPNIC	669 99%	67
163.61.72.0/24	Valid	RIR databaseAPNIC	669 99%	67
163.61.73.0/24	Valid	RIR databaseAPNIC	669 99%	67
163.223.210.0/23	Valid	RIR databaseAPNIC	669 99%	67
36.50.26.0/24	Valid	RIR databaseAPNIC	668 99%	67
36.50.27.0/24	Valid	RIR databaseAPNIC	668 99%	67
161.248.178.0/23	Valid	RIR databaseAPNIC	666 99%	66
2401:2be0::/48	Valid	RIR databaseAPNIC	636 100%	69
2401:37e0::/48	Valid	RIR databaseAPNIC	636 100%	69

AS-SET

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

ROA: none1
Route object: none1
Route object: not announced16

Change	Prefix or set	Detail	Full-table peers
ROA: none	163.227.230.0/23	No ROA covers it. Add a ROA for AS150895, maxLength 23.	672 of 673
Route object: none	163.227.230.0/23	No route object for it. Add a route object with origin AS150895 in the RIR database for the space.	672 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

163.227.230.0/23

No ROA covers it. Add a ROA for AS150895, maxLength 23.

672 of 673

Route object: none

163.227.230.0/23

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

672 of 673

Route objects not announced

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


103.20.102.0/23	APNIC	Valid
103.77.208.0/24	APNIC	Valid
103.77.209.0/24	APNIC	Valid
103.116.52.0/23	APNIC	Valid
103.237.86.0/23	APNIC	Valid
103.237.86.0/24	APNIC	Valid
103.237.87.0/24	APNIC	Valid
160.22.80.0/23	APNIC	Valid
160.191.86.0/24	APNIC	Valid
160.191.87.0/24	APNIC	Valid
160.250.180.0/24	APNIC	Valid
160.250.181.0/24	APNIC	Valid
160.250.186.0/24	APNIC	Valid
160.250.187.0/24	APNIC	Valid
2001:df3:e4c0::/48	APNIC	Valid
2401:3560::/48	APNIC	Valid

103.20.102.0/23

APNIC

Valid

103.77.208.0/24

APNIC

Valid

103.77.209.0/24

APNIC

Valid

103.116.52.0/23

APNIC

Valid

103.237.86.0/23

APNIC

Valid

103.237.86.0/24

APNIC

Valid

103.237.87.0/24

APNIC

Valid

160.22.80.0/23

APNIC

Valid

160.191.86.0/24

APNIC

Valid

160.191.87.0/24

APNIC

Valid

160.250.180.0/24

APNIC

Valid

160.250.181.0/24

APNIC

Valid

160.250.186.0/24

APNIC

Valid

160.250.187.0/24

APNIC

Valid

2001:df3:e4c0::/48

APNIC

Valid

2401:3560::/48

APNIC

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.