bgpreport

Network · data from 2026-11-12

AS131378 CLOUDVIET-AS-VN - Cloud Viet Technology Company Limited

Registry name: CLOUDVIET-AS-VN - Cloud Viet Technology Company Limited, VN · not in PeeringDB

4IPv4 routes 50.0% RPKI valid · 100.0% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
3No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
5Route objects not announced registered with origin AS131378, seen from no peer

Announced routes

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

103.147.186.0/24 No ROA Other IRR onlyNTTCOM 672 100% 66
103.147.187.0/24 No ROA Other IRR onlyNTTCOM 672 100% 66
2405:be40::/48 No ROA RIR databaseAPNIC, NTTCOM 636 100% 67
103.29.26.0/23 Valid RIR databaseAPNIC, NTTCOM 672 100% 67
160.191.2.0/23 Valid RIR databaseAPNIC 672 100% 66

AS-SET

AS131378 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 10 are in fix.csv.

  • ROA: none3
  • Route object: RIR2
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none103.147.186.0/24No ROA covers it. Add a ROA for AS131378, maxLength 24.672 of 673
Route object: RIR103.147.186.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
ROA: none103.147.187.0/24No ROA covers it. Add a ROA for AS131378, maxLength 24.672 of 673
Route object: RIR103.147.187.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
ROA: none2405:be40::/48No ROA covers it. Add a ROA for AS131378, maxLength 48.636 of 636

Route objects not announced

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

103.29.26.0/24APNIC, NTTCOMValid
103.29.27.0/24APNIC, NTTCOMValid
103.147.186.0/23APNIC, NTTCOMNo ROA
103.169.168.0/23APNICInvalid: origin
2407:a440::/48APNIC, NTTCOMNo ROA

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.