Network · data from 2026-11-12

AS150862 MAYTINHVPSTTT-VN - VPSTTT COMPUTER COMPANY LIMITED

Registry name: MAYTINHVPSTTT-VN - VPSTTT COMPUTER COMPANY LIMITED, VN · not in PeeringDB

20IPv4 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

17Route objects not announced registered with origin AS150862, seen from no peer

Announced routes

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


203.145.46.0/23	Valid	RIR databaseAPNIC	673 100%	67
160.187.122.0/23	Valid	RIR databaseAPNIC	672 100%	66
160.187.226.0/23	Valid	RIR databaseAPNIC	672 100%	66
103.240.6.0/23	Valid	RIR databaseAPNIC	669 99%	67
157.10.42.0/23	Valid	RIR databaseAPNIC	669 99%	67
157.10.44.0/23	Valid	RIR databaseAPNIC	669 99%	67
157.15.108.0/23	Valid	RIR databaseAPNIC	669 99%	67
157.15.110.0/23	Valid	RIR databaseAPNIC	669 99%	67
160.30.20.0/23	Valid	RIR databaseAPNIC	669 99%	67
160.30.156.0/23	Valid	RIR databaseAPNIC	669 99%	67
160.30.192.0/23	Valid	RIR databaseAPNIC	669 99%	67
160.30.200.0/23	Valid	RIR databaseAPNIC	669 99%	67
160.187.228.0/23	Valid	RIR databaseAPNIC	669 99%	67
160.187.246.0/23	Valid	RIR databaseAPNIC	669 99%	67
160.191.54.0/23	Valid	RIR databaseAPNIC	669 99%	67
160.191.138.0/23	Valid	RIR databaseAPNIC	669 99%	67
160.191.174.0/23	Valid	RIR databaseAPNIC	669 99%	67
36.50.24.0/23	Valid	RIR databaseAPNIC	668 99%	67
36.50.134.0/23	Valid	RIR databaseAPNIC	668 99%	67
160.22.106.0/23	Valid	RIR databaseAPNIC, RADB	667 99%	67

AS-SET

AS150862 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 17 are in fix.csv.

Route object: not announced17

Route objects not announced

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


2001:df3:e6c0::/48	APNIC	Valid
2001:df4:1c40::/48	APNIC	Valid
2001:df4:2dc0::/48	APNIC	Valid
2001:df4:3640::/48	APNIC	Valid
2001:df4:36c0::/48	APNIC	Valid
2001:df4:50c0::/48	APNIC	Valid
2001:df4:63c0::/48	APNIC	Valid
2001:df4:6440::/48	APNIC	Valid
2001:df4:6840::/48	APNIC	Valid
2001:df4:73c0::/48	APNIC	Valid
2001:df4:8640::/48	APNIC	Valid
2001:df4:8cc0::/48	APNIC	Valid
2401:4120::/48	APNIC	Valid
2401:5120::/48	APNIC	Valid
2401:5b20::/48	APNIC	Valid
2401:7160::/48	APNIC	Valid
2401:71a0::/48	APNIC	Valid

2001:df3:e6c0::/48

APNIC

Valid

2001:df4:1c40::/48

APNIC

Valid

2001:df4:2dc0::/48

APNIC

Valid

2001:df4:3640::/48

APNIC

Valid

2001:df4:36c0::/48

APNIC

Valid

2001:df4:50c0::/48

APNIC

Valid

2001:df4:63c0::/48

APNIC

Valid

2001:df4:6440::/48

APNIC

Valid

2001:df4:6840::/48

APNIC

Valid

2001:df4:73c0::/48

APNIC

Valid

2001:df4:8640::/48

APNIC

Valid

2001:df4:8cc0::/48

APNIC

Valid

2401:4120::/48

APNIC

Valid

2401:5120::/48

APNIC

Valid

2401:5b20::/48

APNIC

Valid

2401:7160::/48

APNIC

Valid

2401:71a0::/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.