Network · data from 2026-11-12
AS135944 VINACIS-AS-VN - VinhNam Commercial informatics service corporation
Registry name: VINACIS-AS-VN - VinhNam Commercial informatics service corporation, VN · not in PeeringDB
25IPv4 routes
100.0% RPKI valid · 100.0% with a route object
1IPv6 routes
0.0% RPKI valid · 0.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
112Route objects not announced
registered with origin AS135944, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS135944, 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.
| 2404:ef80::/32 | No ROA | None | 635 100% |
| 116.118.88.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 116.118.90.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 116.118.92.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 116.118.94.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 180.93.180.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 180.93.182.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 103.216.124.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 116.118.64.0/22 | Valid | RIR databaseAPNIC | 672 100% |
| 116.118.88.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 116.118.89.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 116.118.90.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 116.118.91.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 116.118.92.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 116.118.93.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 116.118.94.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 116.118.95.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 157.119.248.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 180.93.172.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 180.93.176.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 180.93.178.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 180.93.179.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 180.93.180.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 180.93.181.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 180.93.182.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 180.93.183.0/24 | Valid | RIR databaseAPNIC | 672 100% |
AS-SET
AS135944 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 114 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced112
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2404:ef80::/32 | No ROA covers it. Add a ROA for AS135944, maxLength 32. |
| Route object: none | 2404:ef80::/32 | No route object for it. Add a route object with origin AS135944 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS135944 whose prefix no peer sees AS135944 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.159.54.0/24 | APNIC | Valid |
| 103.159.55.0/24 | APNIC | Valid |
| 103.165.144.0/23 | APNIC, NTTCOM, RADB | Valid |
| 103.165.144.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.165.145.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.199.8.0/22 | APNIC, NTTCOM, RADB | Valid |
| 103.199.8.0/23 | APNIC, NTTCOM, RADB | Valid |
| 103.199.8.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.199.9.0/24 | APNIC, RADB | Valid |
| 103.199.10.0/23 | APNIC | Valid |
| 103.199.10.0/24 | APNIC | Valid |
| 103.199.11.0/24 | APNIC, RADB | Valid |
| 103.216.124.0/22 | APNIC, NTTCOM, RADB | Valid |
| 103.216.124.0/23 | APNIC, RADB | Valid |
| 103.216.125.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.216.126.0/23 | APNIC, RADB | Valid |
| 103.216.126.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.216.127.0/24 | APNIC, NTTCOM, RADB | Valid |
| 116.118.0.0/22 | APNIC | Valid |
| 116.118.0.0/23 | APNIC | Valid |
| 116.118.0.0/24 | APNIC | Valid |
| 116.118.1.0/24 | APNIC | Valid |
| 116.118.2.0/23 | APNIC | Valid |
| 116.118.2.0/24 | APNIC | Valid |
| 116.118.3.0/24 | APNIC | Valid |
| 116.118.4.0/22 | APNIC | Valid |
| 116.118.4.0/23 | APNIC | Valid |
| 116.118.4.0/24 | APNIC | Valid |
| 116.118.5.0/24 | APNIC | Valid |
| 116.118.6.0/23 | APNIC | Valid |
| 116.118.6.0/24 | APNIC | Valid |
| 116.118.7.0/24 | APNIC | Valid |
| 116.118.8.0/22 | APNIC | Valid |
| 116.118.8.0/23 | APNIC | Valid |
| 116.118.8.0/24 | APNIC | Valid |
| 116.118.9.0/24 | APNIC | Valid |
| 116.118.10.0/23 | APNIC | Valid |
| 116.118.10.0/24 | APNIC | Valid |
| 116.118.11.0/24 | APNIC | Valid |
| 116.118.12.0/22 | APNIC | Valid |
| 116.118.12.0/23 | APNIC | Valid |
| 116.118.12.0/24 | APNIC | Valid |
| 116.118.13.0/24 | APNIC | Valid |
| 116.118.14.0/23 | APNIC | Valid |
| 116.118.14.0/24 | APNIC | Valid |
| 116.118.15.0/24 | APNIC | Valid |
| 116.118.16.0/22 | APNIC | Valid |
| 116.118.16.0/23 | APNIC | Valid |
| 116.118.16.0/24 | APNIC | Valid |
| 116.118.17.0/24 | APNIC | Valid |
| 116.118.18.0/23 | APNIC | Valid |
| 116.118.18.0/24 | APNIC | Valid |
| 116.118.19.0/24 | APNIC | Valid |
| 116.118.20.0/22 | APNIC | Valid |
| 116.118.20.0/23 | APNIC | Valid |
| 116.118.20.0/24 | APNIC | Valid |
| 116.118.21.0/24 | APNIC | Valid |
| 116.118.22.0/23 | APNIC | Valid |
| 116.118.22.0/24 | APNIC | Valid |
| 116.118.23.0/24 | APNIC | Valid |
| 116.118.24.0/22 | APNIC | Valid |
| 116.118.24.0/23 | APNIC | Valid |
| 116.118.24.0/24 | APNIC | Valid |
| 116.118.25.0/24 | APNIC | Valid |
| 116.118.26.0/23 | APNIC | Valid |
| 116.118.26.0/24 | APNIC | Valid |
| 116.118.27.0/24 | APNIC | Valid |
| 116.118.28.0/22 | APNIC | Valid |
| 116.118.28.0/23 | APNIC | Valid |
| 116.118.28.0/24 | APNIC | Valid |
| 116.118.29.0/24 | APNIC | Valid |
| 116.118.30.0/23 | APNIC | Valid |
| 116.118.30.0/24 | APNIC | Valid |
| 116.118.31.0/24 | APNIC | Valid |
| 116.118.44.0/22 | APNIC | Invalid: origin |
| 116.118.48.0/22 | APNIC | Invalid: origin |
| 116.118.64.0/23 | APNIC | Valid |
| 116.118.64.0/24 | APNIC | Valid |
| 116.118.65.0/24 | APNIC | Valid |
| 116.118.66.0/23 | APNIC | Valid |
| 116.118.66.0/24 | APNIC | Valid |
| 116.118.67.0/24 | APNIC | Valid |
| 116.118.72.0/22 | APNIC | Valid |
| 116.118.72.0/23 | APNIC | Valid |
| 116.118.72.0/24 | APNIC | Valid |
| 116.118.73.0/24 | APNIC | Valid |
| 116.118.74.0/23 | APNIC | Valid |
| 116.118.74.0/24 | APNIC | Valid |
| 116.118.75.0/24 | APNIC | Valid |
| 116.118.76.0/22 | APNIC | Valid |
| 116.118.76.0/23 | APNIC | Valid |
| 116.118.76.0/24 | APNIC | Valid |
| 116.118.77.0/24 | APNIC | Valid |
| 116.118.78.0/23 | APNIC | Valid |
| 116.118.78.0/24 | APNIC | Valid |
| 116.118.79.0/24 | APNIC | Valid |
| 116.118.88.0/22 | APNIC | Valid |
| 116.118.92.0/22 | APNIC, NTTCOM | Valid |
| 180.93.136.0/22 | APNIC | Invalid: origin |
| 180.93.172.0/23 | APNIC, NTTCOM, RADB | Valid |
| 180.93.172.0/24 | APNIC, NTTCOM, RADB | Valid |
| 180.93.173.0/24 | APNIC, NTTCOM, RADB | Valid |
| 180.93.174.0/23 | APNIC, NTTCOM, RADB | Valid |
| 180.93.174.0/24 | APNIC, NTTCOM, RADB | Valid |
| 180.93.175.0/24 | APNIC, NTTCOM, RADB | Valid |
| 180.93.176.0/22 | APNIC, NTTCOM, RADB | Valid |
| 180.93.176.0/24 | APNIC, NTTCOM, RADB | Valid |
| 180.93.177.0/24 | APNIC, NTTCOM, RADB | Valid |
| 180.93.178.0/23 | APNIC, NTTCOM, RADB | Valid |
| 180.93.180.0/22 | APNIC, NTTCOM | Valid |
| 2001:df7:cc00::/48 | APNIC | Valid |
| 2404:ef80::/48 | 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.