bgpreport

Network · data from 2026-11-12

AS23659 HEITECH-AS-AP - HeiTech Padu Bhd.

Registry name: HEITECH-AS-AP - HeiTech Padu Bhd., MY · not in PeeringDB

19IPv4 routes 0.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
20No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
19Route objects not announced registered with origin AS23659, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS23659, 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.235.28.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 66
103.235.29.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 66
103.235.31.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 66
202.171.40.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
202.171.44.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
2401:5200::/32 No ROA Other IRR onlyRADB 636 100% 67
202.171.34.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
103.235.30.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 672 100% 68
202.171.32.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 672 100% 68
202.171.33.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 672 100% 68
202.171.35.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 672 100% 68
202.171.36.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 672 100% 68
202.171.38.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 672 100% 68
202.171.39.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 672 100% 68
202.171.41.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 672 100% 68
202.171.42.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 672 100% 68
202.171.43.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 672 100% 68
202.171.45.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 672 100% 68
202.171.46.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 672 100% 68
202.171.47.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 672 100% 68

AS-SET

AS23659 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 45 are in fix.csv.

  • ROA: none20
  • Route object: RIR6
  • Route object: not announced19
ChangePrefix or setDetailFull-table peers
ROA: none103.235.28.0/24No ROA covers it. Add a ROA for AS23659, maxLength 24.672 of 673
Route object: RIR103.235.28.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none103.235.29.0/24No ROA covers it. Add a ROA for AS23659, maxLength 24.672 of 673
Route object: RIR103.235.29.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none103.235.31.0/24No ROA covers it. Add a ROA for AS23659, maxLength 24.672 of 673
Route object: RIR103.235.31.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none202.171.40.0/24No ROA covers it. Add a ROA for AS23659, maxLength 24.672 of 673
Route object: RIR202.171.40.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none202.171.44.0/24No ROA covers it. Add a ROA for AS23659, maxLength 24.672 of 673
Route object: RIR202.171.44.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none2401:5200::/32No ROA covers it. Add a ROA for AS23659, maxLength 32.636 of 636
Route object: RIR2401:5200::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none202.171.34.0/24No ROA covers it. Add a ROA for AS23659, maxLength 24.673 of 673
ROA: none103.235.30.0/24No ROA covers it. Add a ROA for AS23659, maxLength 24.672 of 673
ROA: none202.171.32.0/24No ROA covers it. Add a ROA for AS23659, maxLength 24.672 of 673
ROA: none202.171.33.0/24No ROA covers it. Add a ROA for AS23659, maxLength 24.672 of 673
ROA: none202.171.35.0/24No ROA covers it. Add a ROA for AS23659, maxLength 24.672 of 673
ROA: none202.171.36.0/24No ROA covers it. Add a ROA for AS23659, maxLength 24.672 of 673
ROA: none202.171.38.0/24No ROA covers it. Add a ROA for AS23659, maxLength 24.672 of 673
ROA: none202.171.39.0/24No ROA covers it. Add a ROA for AS23659, maxLength 24.672 of 673
ROA: none202.171.41.0/24No ROA covers it. Add a ROA for AS23659, maxLength 24.672 of 673
ROA: none202.171.42.0/24No ROA covers it. Add a ROA for AS23659, maxLength 24.672 of 673
ROA: none202.171.43.0/24No ROA covers it. Add a ROA for AS23659, maxLength 24.672 of 673
ROA: none202.171.45.0/24No ROA covers it. Add a ROA for AS23659, maxLength 24.672 of 673
ROA: none202.171.46.0/24No ROA covers it. Add a ROA for AS23659, maxLength 24.672 of 673
ROA: none202.171.47.0/24No ROA covers it. Add a ROA for AS23659, maxLength 24.672 of 673

Route objects not announced

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

103.235.28.0/22NTTCOM, RADBNo ROA
103.235.28.0/23NTTCOM, RADBNo ROA
103.235.30.0/23NTTCOM, RADBNo ROA
202.171.32.0/20NTTCOMNo ROA
202.171.32.0/21NTTCOM, RADBNo ROA
202.171.32.0/22NTTCOM, RADBNo ROA
202.171.32.0/23NTTCOM, RADBNo ROA
202.171.34.0/23NTTCOM, RADBNo ROA
202.171.36.0/22NTTCOM, RADBNo ROA
202.171.36.0/23NTTCOM, RADBNo ROA
202.171.37.0/24NTTCOM, RADBNo ROA
202.171.38.0/23NTTCOM, RADBNo ROA
202.171.40.0/21NTTCOM, RADBNo ROA
202.171.40.0/22NTTCOM, RADBNo ROA
202.171.40.0/23NTTCOM, RADBNo ROA
202.171.42.0/23NTTCOM, RADBNo ROA
202.171.44.0/22NTTCOM, RADBNo ROA
202.171.44.0/23NTTCOM, RADBNo ROA
202.171.46.0/23NTTCOM, RADBNo 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.