Network · data from 2026-11-12
AS56150 VHOST-AS-VN - Viet Solutions Services Trading Company Limited
Registry name: VHOST-AS-VN - Viet Solutions Services Trading Company Limited, VN · not in PeeringDB
32IPv4 routes
84.4% RPKI valid · 84.4% with a route object
4IPv6 routes
0.0% RPKI valid · 100.0% with a route object
5RPKI invalid
0 origin · 5 maxLength
4No ROA
5 with no route object for this origin
9Low visibility
seen by under 10% of full-table peers
10Route objects not announced
registered with origin AS56150, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS56150, 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.
| 45.122.221.228/32 | Invalid: maxLength | Nonecovered by 45.122.221.0/24 | 4 1%low visibility |
| 103.232.122.231/32 | Invalid: maxLength | Nonecovered by 103.232.122.0/24 | 4 1%low visibility |
| 103.232.123.215/32 | Invalid: maxLength | Nonecovered by 103.232.123.0/24 | 4 1%low visibility |
| 45.122.221.89/32 | Invalid: maxLength | Nonecovered by 45.122.221.0/24 | 0 0%low visibility |
| 103.143.142.167/32 | Invalid: maxLength | Nonecovered by 103.143.142.0/24 | 0 0%low visibility |
| 2001:df1:9780::/48 | No ROA | RIR databaseAPNIC, NTTCOM | 636 100% |
| 2401:78c0::/32 | No ROA | RIR databaseAPNIC, NTTCOM | 636 100% |
| 2405:54c0::/48 | No ROA | RIR databaseAPNIC, NTTCOM, RADB | 636 100% |
| 2405:5440::/48 | No ROA | RIR databaseAPNIC | 635 100% |
| 103.143.142.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.143.143.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.232.122.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.27.60.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 103.27.61.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 103.27.62.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 103.27.63.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 103.92.28.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 103.92.29.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 103.92.30.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 103.92.31.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 103.143.145.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 103.232.120.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 103.232.121.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 103.232.123.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 45.122.220.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 45.122.221.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 45.122.222.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 45.122.223.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 103.143.144.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 103.143.208.0/23 | Valid | RIR databaseAPNIC, NTTCOM | 670 100% |
| 103.143.208.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 670 100% |
| 103.143.209.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 670 100% |
| 45.122.220.0/22 | Valid | RIR databaseAPNIC, NTTCOM | 2 0%low visibility |
| 103.27.60.0/22 | Valid | RIR databaseAPNIC, NTTCOM | 2 0%low visibility |
| 103.92.28.0/22 | Valid | RIR databaseAPNIC, NTTCOM | 2 0%low visibility |
| 103.143.142.0/23 | Valid | RIR databaseAPNIC | 2 0%low visibility |
AS-SET
AS56150 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 24 are in fix.csv.
- ROA: maxLength5
- ROA: none4
- Route object: none5
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 45.122.221.228/32 | ROA 45.122.220.0/22 AS56150 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 45.122.221.228/32. |
| Route object: none | 45.122.221.228/32 | No route object for it. A route object for 45.122.221.0/24 with origin AS56150 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS56150 in the RIR database for the space. |
| ROA: maxLength | 103.232.122.231/32 | ROA 103.232.120.0/22 AS56150 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 103.232.122.231/32. |
| Route object: none | 103.232.122.231/32 | No route object for it. A route object for 103.232.122.0/24 with origin AS56150 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS56150 in the RIR database for the space. |
| ROA: maxLength | 103.232.123.215/32 | ROA 103.232.120.0/22 AS56150 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 103.232.123.215/32. |
| Route object: none | 103.232.123.215/32 | No route object for it. A route object for 103.232.123.0/24 with origin AS56150 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS56150 in the RIR database for the space. |
| ROA: maxLength | 45.122.221.89/32 | ROA 45.122.220.0/22 AS56150 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 45.122.221.89/32. |
| Route object: none | 45.122.221.89/32 | No route object for it. A route object for 45.122.221.0/24 with origin AS56150 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS56150 in the RIR database for the space. |
| ROA: maxLength | 103.143.142.167/32 | ROA 103.143.142.0/23 AS56150 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 103.143.142.167/32. |
| Route object: none | 103.143.142.167/32 | No route object for it. A route object for 103.143.142.0/24 with origin AS56150 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS56150 in the RIR database for the space. |
| ROA: none | 2001:df1:9780::/48 | No ROA covers it. Add a ROA for AS56150, maxLength 48. |
| ROA: none | 2401:78c0::/32 | No ROA covers it. Add a ROA for AS56150, maxLength 32. |
| ROA: none | 2405:54c0::/48 | No ROA covers it. Add a ROA for AS56150, maxLength 48. |
| ROA: none | 2405:5440::/48 | No ROA covers it. Add a ROA for AS56150, maxLength 48. |
Route objects not announced
Route objects with origin AS56150 whose prefix no peer sees AS56150 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.122.220.0/23 | APNIC, NTTCOM | Valid |
| 45.122.222.0/23 | APNIC, NTTCOM | Valid |
| 103.27.60.0/23 | APNIC | Valid |
| 103.27.62.0/23 | APNIC | Valid |
| 103.92.28.0/23 | APNIC, NTTCOM | Valid |
| 103.92.30.0/23 | APNIC, NTTCOM | Valid |
| 103.143.144.0/23 | APNIC, NTTCOM, RADB | Valid |
| 103.232.120.0/22 | APNIC, NTTCOM, RADB | Valid |
| 103.232.120.0/23 | APNIC, NTTCOM | Valid |
| 103.232.122.0/23 | APNIC, NTTCOM | 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.