Network · data from 2026-11-12

AS150828 VMONCLOUD-VN - VMON CLOUD COMPANY LIMITED

Registry name: VMONCLOUD-VN - VMON CLOUD COMPANY LIMITED, VN · not in PeeringDB

9IPv4 routes 77.8% RPKI valid · 77.8% with a route object

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

2RPKI invalid 0 origin · 2 maxLength

0No ROA 2 with no route object for this origin

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

2Route objects not announced registered with origin AS150828, seen from no peer

Announced routes

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


36.50.232.240/32	Invalid: maxLength	Nonecovered by 36.50.232.0/24	4 1%low visibility	11
103.252.122.1/32	Invalid: maxLength	Nonecovered by 103.252.122.0/24	4 1%low visibility	11
103.116.8.0/23	Valid	RIR databaseAPNIC	672 100%	67
103.252.122.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	669 99%	67
103.252.123.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	669 99%	67
165.99.234.0/24	Valid	RIR databaseAPNIC	669 99%	67
165.99.235.0/24	Valid	RIR databaseAPNIC	669 99%	67
36.50.232.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	668 99%	67
36.50.233.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	668 99%	67
2401:4ae0::/48	Valid	RIR databaseAPNIC, RADB	636 100%	69

36.50.232.240/32

Invalid: maxLength

Nonecovered by 36.50.232.0/24

4 1%low visibility

103.252.122.1/32

Invalid: maxLength

Nonecovered by 103.252.122.0/24

4 1%low visibility

103.116.8.0/23

Valid

RIR databaseAPNIC

672 100%

103.252.122.0/24

Valid

RIR databaseAPNIC, NTTCOM, RADB

669 99%

103.252.123.0/24

Valid

RIR databaseAPNIC, NTTCOM, RADB

669 99%

165.99.234.0/24

Valid

RIR databaseAPNIC

669 99%

165.99.235.0/24

Valid

RIR databaseAPNIC

669 99%

36.50.232.0/24

Valid

RIR databaseAPNIC, NTTCOM, RADB

668 99%

36.50.233.0/24

Valid

RIR databaseAPNIC, NTTCOM, RADB

668 99%

2401:4ae0::/48

Valid

RIR databaseAPNIC, RADB

636 100%

AS-SET

AS150828 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 6 are in fix.csv.

ROA: maxLength2
Route object: none2
Route object: not announced2

Change	Prefix or set	Detail	Full-table peers
ROA: maxLength	36.50.232.240/32	ROA 36.50.232.0/24 AS150828 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 36.50.232.240/32.	4 of 673
Route object: none	36.50.232.240/32	No route object for it. A route object for 36.50.232.0/24 with origin AS150828 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS150828 in the RIR database for the space.	4 of 673
ROA: maxLength	103.252.122.1/32	ROA 103.252.122.0/24 AS150828 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 103.252.122.1/32.	4 of 673
Route object: none	103.252.122.1/32	No route object for it. A route object for 103.252.122.0/24 with origin AS150828 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS150828 in the RIR database for the space.	4 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: maxLength

36.50.232.240/32

ROA 36.50.232.0/24 AS150828 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 36.50.232.240/32.

4 of 673

Route object: none

36.50.232.240/32

No route object for it. A route object for 36.50.232.0/24 with origin AS150828 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS150828 in the RIR database for the space.

4 of 673

ROA: maxLength

103.252.122.1/32

ROA 103.252.122.0/24 AS150828 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 103.252.122.1/32.

4 of 673

Route object: none

103.252.122.1/32

No route object for it. A route object for 103.252.122.0/24 with origin AS150828 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS150828 in the RIR database for the space.

4 of 673

Route objects not announced

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


2400:eca0::/48	APNIC	Valid
2401:5e20::/48	APNIC	Valid

2400:eca0::/48

APNIC

Valid

2401:5e20::/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.