bgpreport

Network · data from 2026-11-12

AS131435 HOABINH-VN - Vietnam Esports and Entertainment Joint Stock Company

Registry name: HOABINH-VN - Vietnam Esports and Entertainment Joint Stock Company, VN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS131435, 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.119.240.0/22 No ROA Other origin only 523 78% 66
148.222.90.0/23 No ROA Other IRR onlyRADB 671 100% 66
45.119.242.0/24 No ROA Other IRR onlyRADB 613 91% 66
103.60.17.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
103.60.19.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
45.119.216.0/22 Valid RIR databaseAPNIC, NTTCOM 672 100% 66
45.119.216.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
103.60.16.0/22 Valid RIR databaseAPNIC 672 100% 66
148.222.80.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
148.222.81.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
148.222.90.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
148.222.91.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
148.222.95.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
45.119.218.0/23 Valid RIR databaseAPNIC 671 100% 66
45.119.218.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
45.119.219.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
103.60.18.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 66
103.60.18.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 66
148.222.80.0/23 Valid RIR databaseAPNIC 671 100% 66
148.222.93.0/24 Valid RIR databaseAPNIC 670 100% 66
103.60.16.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 669 99% 66

AS-SET

AS131435 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 9 are in fix.csv.

  • ROA: none3
  • Route object: none1
  • Route object: RIR2
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none45.119.240.0/22No ROA covers it. Add a ROA for AS131435, maxLength 22.523 of 673
Route object: none45.119.240.0/22Route objects for it name AS131418. Add a route object with origin AS131435 in the RIR database for the space.523 of 673
ROA: none148.222.90.0/23No ROA covers it. Add a ROA for AS131435, maxLength 23.671 of 673
Route object: RIR148.222.90.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none45.119.242.0/24No ROA covers it. Add a ROA for AS131435, maxLength 24.613 of 673
Route object: RIR45.119.242.0/24Route object only in RADB. Add it in the RIR database for the space.613 of 673

Route objects not announced

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

45.119.216.0/23APNICValid
45.119.217.0/24APNIC, NTTCOMValid
103.60.16.0/23APNICValid

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.