bgpreport

Network · data from 2026-11-12

AS133747 TRIUMPH-AS-AP - TRIUMPH DYNASTY Limited

Registry name: TRIUMPH-AS-AP - TRIUMPH DYNASTY Limited, HK · not in PeeringDB

17IPv4 routes 17.6% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
14No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
54Route objects not announced registered with origin AS133747, seen from no peer

Announced routes

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

43.241.164.0/22 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
43.241.165.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
43.241.167.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
43.249.100.0/22 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
43.249.103.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
103.9.228.0/22 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
103.9.228.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
103.9.229.0/24 No ROA Other IRR onlyRADB 671 100% 67
103.40.5.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
103.40.6.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
103.40.176.0/22 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
103.226.100.0/22 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
103.226.100.0/24 No ROA Other IRR onlyRADB 671 100% 67
103.226.101.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
103.119.212.0/24 Valid Other IRR onlyRADB 671 100% 67
115.30.64.0/23 Valid Other IRR onlyRADB 671 100% 67
115.30.64.0/24 Valid Other IRR onlyRADB 671 100% 67

AS-SET

AS133747 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 85 are in fix.csv.

  • ROA: none14
  • Route object: RIR17
  • Route object: not announced54
ChangePrefix or setDetailFull-table peers
ROA: none43.241.164.0/22No ROA covers it. Add a ROA for AS133747, maxLength 22.671 of 673
Route object: RIR43.241.164.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none43.241.165.0/24No ROA covers it. Add a ROA for AS133747, maxLength 24.671 of 673
Route object: RIR43.241.165.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none43.241.167.0/24No ROA covers it. Add a ROA for AS133747, maxLength 24.671 of 673
Route object: RIR43.241.167.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none43.249.100.0/22No ROA covers it. Add a ROA for AS133747, maxLength 22.671 of 673
Route object: RIR43.249.100.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none43.249.103.0/24No ROA covers it. Add a ROA for AS133747, maxLength 24.671 of 673
Route object: RIR43.249.103.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none103.9.228.0/22No ROA covers it. Add a ROA for AS133747, maxLength 22.671 of 673
Route object: RIR103.9.228.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none103.9.228.0/24No ROA covers it. Add a ROA for AS133747, maxLength 24.671 of 673
Route object: RIR103.9.228.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none103.9.229.0/24No ROA covers it. Add a ROA for AS133747, maxLength 24.671 of 673
Route object: RIR103.9.229.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none103.40.5.0/24No ROA covers it. Add a ROA for AS133747, maxLength 24.671 of 673
Route object: RIR103.40.5.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none103.40.6.0/24No ROA covers it. Add a ROA for AS133747, maxLength 24.671 of 673
Route object: RIR103.40.6.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none103.40.176.0/22No ROA covers it. Add a ROA for AS133747, maxLength 22.671 of 673
Route object: RIR103.40.176.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none103.226.100.0/22No ROA covers it. Add a ROA for AS133747, maxLength 22.671 of 673
Route object: RIR103.226.100.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none103.226.100.0/24No ROA covers it. Add a ROA for AS133747, maxLength 24.671 of 673
Route object: RIR103.226.100.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none103.226.101.0/24No ROA covers it. Add a ROA for AS133747, maxLength 24.671 of 673
Route object: RIR103.226.101.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR103.119.212.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR115.30.64.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR115.30.64.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

27.123.10.0/24NTTCOM, RADBNo ROA
43.241.32.0/22RADBNo ROA
43.241.32.0/24RADBNo ROA
43.241.33.0/24NTTCOM, RADBNo ROA
43.241.34.0/24RADBNo ROA
43.241.35.0/24RADBNo ROA
43.241.164.0/23NTTCOM, RADBNo ROA
43.241.164.0/24NTTCOM, RADBNo ROA
43.241.166.0/23NTTCOM, RADBNo ROA
43.241.166.0/24NTTCOM, RADBNo ROA
43.249.100.0/23NTTCOM, RADBNo ROA
43.249.100.0/24NTTCOM, RADBNo ROA
43.249.101.0/24NTTCOM, RADBNo ROA
43.249.102.0/23NTTCOM, RADBNo ROA
43.249.102.0/24NTTCOM, RADBNo ROA
60.198.136.0/24RADBValid
103.7.237.0/24NTTCOM, RADBNo ROA
103.9.231.0/24RADBNo ROA
103.37.36.0/22NTTCOM, RADBNo ROA
103.37.36.0/24NTTCOM, RADBNo ROA
103.37.37.0/24NTTCOM, RADBNo ROA
103.37.38.0/24NTTCOM, RADBNo ROA
103.37.39.0/24NTTCOM, RADBNo ROA
103.40.4.0/22NTTCOM, RADBNo ROA
103.40.4.0/24NTTCOM, RADBNo ROA
103.40.7.0/24NTTCOM, RADBNo ROA
103.40.176.0/23NTTCOM, RADBNo ROA
103.40.176.0/24NTTCOM, RADBNo ROA
103.40.177.0/24NTTCOM, RADBNo ROA
103.40.178.0/23NTTCOM, RADBNo ROA
103.40.178.0/24NTTCOM, RADBNo ROA
103.40.179.0/24NTTCOM, RADBNo ROA
103.119.213.0/24RADBValid
103.226.102.0/24NTTCOM, RADBNo ROA
103.226.103.0/24NTTCOM, RADBNo ROA
115.30.65.0/24RADBValid
196.10.64.0/20RADBNo ROA
196.10.64.0/24RADBNo ROA
196.10.65.0/24RADBNo ROA
196.10.66.0/24RADBNo ROA
196.10.67.0/24RADBNo ROA
196.10.68.0/24RADBNo ROA
196.10.69.0/24RADBNo ROA
196.10.70.0/24RADBNo ROA
196.10.71.0/24RADBNo ROA
196.10.72.0/24RADBNo ROA
196.10.73.0/24RADBNo ROA
196.10.74.0/24RADBNo ROA
196.10.75.0/24RADBNo ROA
196.10.76.0/24RADBNo ROA
196.10.77.0/24RADBNo ROA
196.10.78.0/24RADBNo ROA
196.10.79.0/24RADBNo ROA
2401:9880::/32RADBNo 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.