bgpreport

Network · data from 2026-11-12

AS131143 ChinaTrust-AS-TW - Chinatrust Commercial Bank

Registry name: ChinaTrust-AS-TW - Chinatrust Commercial Bank, TW · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS131143, 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.126.164.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
175.184.240.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
175.184.241.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
175.184.242.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
175.184.243.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
175.184.244.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
175.184.245.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
175.184.246.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
175.184.247.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
103.126.164.0/22 Valid Other IRR onlyRADB 670 100% 67
2405:3300::/32 Valid Other IRR onlyRADB 635 100% 67

AS-SET

AS131143 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 24 are in fix.csv.

  • Route object: RIR11
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
Route object: RIR103.126.164.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR175.184.240.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR175.184.241.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR175.184.242.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR175.184.243.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR175.184.244.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR175.184.245.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR175.184.246.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR175.184.247.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR103.126.164.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR2405:3300::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

103.126.164.0/23RADBValid
103.126.165.0/24RADBValid
103.126.166.0/23RADBValid
103.126.166.0/24RADBValid
103.126.167.0/24RADBValid
103.127.132.0/22RADBNo ROA
175.184.240.0/21NTTCOM, RADBValid
175.184.240.0/22NTTCOM, RADBValid
175.184.240.0/23NTTCOM, RADBValid
175.184.242.0/23NTTCOM, RADBValid
175.184.244.0/22NTTCOM, RADBValid
175.184.244.0/23NTTCOM, RADBValid
175.184.246.0/23NTTCOM, RADBValid

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.