bgpreport

Network · data from 2026-11-12

AS63733 HOATHAI-VN - Hoa Thai Software Services Company Limited

Registry name: HOATHAI-VN - Hoa Thai Software Services Company Limited, VN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS63733, 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.206.212.0/23 No ROA Nonecovered by 103.206.212.0/22 671 100% 66
103.206.213.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
103.206.212.0/22 No ROA Other IRR onlyNTTCOM, RADB 670 100% 67
103.206.214.0/24 No ROA Other IRR onlyNTTCOM 670 100% 67
137.59.116.0/22 Valid RIR databaseAPNIC, NTTCOM 672 100% 66
137.59.116.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
137.59.117.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
137.59.118.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
137.59.119.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66

AS-SET

AS63733 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: none4
  • Route object: none1
  • Route object: RIR3
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none103.206.212.0/23No ROA covers it. Add a ROA for AS63733, maxLength 23.671 of 673
Route object: none103.206.212.0/23No route object for it. A route object for 103.206.212.0/22 with origin AS63733 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63733 in the RIR database for the space.671 of 673
ROA: none103.206.213.0/24No ROA covers it. Add a ROA for AS63733, maxLength 24.671 of 673
Route object: RIR103.206.213.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none103.206.212.0/22No ROA covers it. Add a ROA for AS63733, maxLength 22.670 of 673
Route object: RIR103.206.212.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
ROA: none103.206.214.0/24No ROA covers it. Add a ROA for AS63733, maxLength 24.670 of 673
Route object: RIR103.206.214.0/24Route object only in NTTCOM. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

103.206.212.0/24NTTCOM, RADBNo ROA
103.206.215.0/24NTTCOM, RADBNo ROA
137.59.116.0/23APNICValid
137.59.118.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.