bgpreport

Network · data from 2026-11-12

AS9671 TRADEVAN-AS-AP - Trade-Van Informaiton Services Co.

Registry name: TRADEVAN-AS-AP - Trade-Van Informaiton Services Co., TW · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS9671, 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.
202.173.32.0/19 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
202.173.32.0/20 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
202.173.48.0/20 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
202.173.32.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
202.173.34.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
202.173.37.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
202.173.39.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
202.173.43.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
202.173.45.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
202.173.46.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
202.173.50.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
202.173.51.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
202.173.54.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
202.173.55.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
202.173.62.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
2405:4500::/32 No ROA Other IRR onlyNTTCOM, RADB 636 100% 67
2405:4500:d::/48 No ROA Other IRR onlyRADB 634 100% 67

AS-SET

AS9671 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 83 are in fix.csv.

  • ROA: none17
  • Route object: RIR17
  • Route object: not announced49
ChangePrefix or setDetailFull-table peers
ROA: none202.173.32.0/19No ROA covers it. Add a ROA for AS9671, maxLength 19.673 of 673
Route object: RIR202.173.32.0/19Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none202.173.32.0/20No ROA covers it. Add a ROA for AS9671, maxLength 20.673 of 673
Route object: RIR202.173.32.0/20Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none202.173.48.0/20No ROA covers it. Add a ROA for AS9671, maxLength 20.673 of 673
Route object: RIR202.173.48.0/20Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none202.173.32.0/24No ROA covers it. Add a ROA for AS9671, maxLength 24.671 of 673
Route object: RIR202.173.32.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none202.173.34.0/24No ROA covers it. Add a ROA for AS9671, maxLength 24.671 of 673
Route object: RIR202.173.34.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none202.173.37.0/24No ROA covers it. Add a ROA for AS9671, maxLength 24.671 of 673
Route object: RIR202.173.37.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none202.173.39.0/24No ROA covers it. Add a ROA for AS9671, maxLength 24.671 of 673
Route object: RIR202.173.39.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none202.173.43.0/24No ROA covers it. Add a ROA for AS9671, maxLength 24.671 of 673
Route object: RIR202.173.43.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none202.173.45.0/24No ROA covers it. Add a ROA for AS9671, maxLength 24.671 of 673
Route object: RIR202.173.45.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none202.173.46.0/24No ROA covers it. Add a ROA for AS9671, maxLength 24.671 of 673
Route object: RIR202.173.46.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none202.173.50.0/24No ROA covers it. Add a ROA for AS9671, maxLength 24.671 of 673
Route object: RIR202.173.50.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none202.173.51.0/24No ROA covers it. Add a ROA for AS9671, maxLength 24.671 of 673
Route object: RIR202.173.51.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none202.173.54.0/24No ROA covers it. Add a ROA for AS9671, maxLength 24.671 of 673
Route object: RIR202.173.54.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none202.173.55.0/24No ROA covers it. Add a ROA for AS9671, maxLength 24.671 of 673
Route object: RIR202.173.55.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none202.173.62.0/24No ROA covers it. Add a ROA for AS9671, maxLength 24.671 of 673
Route object: RIR202.173.62.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none2405:4500::/32No ROA covers it. Add a ROA for AS9671, maxLength 32.636 of 636
Route object: RIR2405:4500::/32Route object only in NTTCOM, RADB. Add it in the RIR database for the space.636 of 636
ROA: none2405:4500:d::/48No ROA covers it. Add a ROA for AS9671, maxLength 48.634 of 636
Route object: RIR2405:4500:d::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

202.173.32.0/21NTTCOM, RADBNo ROA
202.173.32.0/22NTTCOM, RADBNo ROA
202.173.32.0/23NTTCOM, RADBNo ROA
202.173.33.0/24NTTCOM, RADBNo ROA
202.173.34.0/23NTTCOM, RADBNo ROA
202.173.35.0/24NTTCOM, RADBNo ROA
202.173.36.0/22NTTCOM, RADBNo ROA
202.173.36.0/23NTTCOM, RADBNo ROA
202.173.36.0/24NTTCOM, RADBNo ROA
202.173.38.0/23NTTCOM, RADBNo ROA
202.173.38.0/24NTTCOM, RADBNo ROA
202.173.40.0/21NTTCOM, RADBNo ROA
202.173.40.0/22NTTCOM, RADBNo ROA
202.173.40.0/23NTTCOM, RADBNo ROA
202.173.40.0/24NTTCOM, RADBNo ROA
202.173.41.0/24NTTCOM, RADBNo ROA
202.173.42.0/23NTTCOM, RADBNo ROA
202.173.42.0/24NTTCOM, RADBNo ROA
202.173.44.0/22NTTCOM, RADBNo ROA
202.173.44.0/23NTTCOM, RADBNo ROA
202.173.44.0/24NTTCOM, RADBNo ROA
202.173.46.0/23NTTCOM, RADBNo ROA
202.173.47.0/24NTTCOM, RADBNo ROA
202.173.48.0/21NTTCOM, RADBNo ROA
202.173.48.0/22NTTCOM, RADBNo ROA
202.173.48.0/23NTTCOM, RADBNo ROA
202.173.48.0/24NTTCOM, RADBNo ROA
202.173.49.0/24NTTCOM, RADBNo ROA
202.173.50.0/23NTTCOM, RADBNo ROA
202.173.52.0/22NTTCOM, RADBNo ROA
202.173.52.0/23NTTCOM, RADBNo ROA
202.173.52.0/24NTTCOM, RADBNo ROA
202.173.53.0/24NTTCOM, RADBNo ROA
202.173.54.0/23NTTCOM, RADBNo ROA
202.173.56.0/21NTTCOM, RADBNo ROA
202.173.56.0/22NTTCOM, RADBNo ROA
202.173.56.0/23NTTCOM, RADBNo ROA
202.173.56.0/24NTTCOM, RADBNo ROA
202.173.57.0/24NTTCOM, RADBNo ROA
202.173.58.0/23NTTCOM, RADBNo ROA
202.173.58.0/24NTTCOM, RADBNo ROA
202.173.59.0/24NTTCOM, RADBNo ROA
202.173.60.0/22NTTCOM, RADBNo ROA
202.173.60.0/23NTTCOM, RADBNo ROA
202.173.60.0/24NTTCOM, RADBNo ROA
202.173.61.0/24NTTCOM, RADBNo ROA
202.173.62.0/23NTTCOM, RADBNo ROA
202.173.63.0/24NTTCOM, RADBNo ROA
2405:4500:2::/48NTTCOM, 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.