bgpreport

Network · data from 2026-11-12

AS135928 HOITUSO-AS-VN - Digital Convergence Technology Solutions Company Limited

Registry name: HOITUSO-AS-VN - Digital Convergence Technology Solutions Company Limited, VN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS135928, 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.103.116.0/24 No ROA Nonecovered by 103.103.116.0/22 673 100% 66
103.103.117.0/24 No ROA Nonecovered by 103.103.116.0/22 673 100% 66
103.103.118.0/24 No ROA Nonecovered by 103.103.116.0/22 673 100% 66
103.103.119.0/24 No ROA Nonecovered by 103.103.116.0/22 673 100% 66
2401:4be0::/48 No ROA Other origin only 635 100% 68
103.103.116.0/22 No ROA Other IRR onlyRADB 673 100% 66

AS-SET

AS135928 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 12 are in fix.csv.

  • ROA: none6
  • Route object: none5
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none103.103.116.0/24No ROA covers it. Add a ROA for AS135928, maxLength 24.673 of 673
Route object: none103.103.116.0/24No route object for it. A route object for 103.103.116.0/22 with origin AS135928 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135928 in the RIR database for the space.673 of 673
ROA: none103.103.117.0/24No ROA covers it. Add a ROA for AS135928, maxLength 24.673 of 673
Route object: none103.103.117.0/24No route object for it. A route object for 103.103.116.0/22 with origin AS135928 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135928 in the RIR database for the space.673 of 673
ROA: none103.103.118.0/24No ROA covers it. Add a ROA for AS135928, maxLength 24.673 of 673
Route object: none103.103.118.0/24No route object for it. A route object for 103.103.116.0/22 with origin AS135928 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135928 in the RIR database for the space.673 of 673
ROA: none103.103.119.0/24No ROA covers it. Add a ROA for AS135928, maxLength 24.673 of 673
Route object: none103.103.119.0/24No route object for it. A route object for 103.103.116.0/22 with origin AS135928 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135928 in the RIR database for the space.673 of 673
ROA: none2401:4be0::/48No ROA covers it. Add a ROA for AS135928, maxLength 48.635 of 636
Route object: none2401:4be0::/48Route objects for it name AS151865. Add a route object with origin AS135928 in the RIR database for the space.635 of 636
ROA: none103.103.116.0/22No ROA covers it. Add a ROA for AS135928, maxLength 22.673 of 673
Route object: RIR103.103.116.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

Every route object with origin AS135928 is announced.

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.