bgpreport

Network · data from 2026-11-12

AS17487 ICBCASIA-AP - Industrial and Commercial Bank

Registry name: ICBCASIA-AP - Industrial and Commercial Bank, HK · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS17487, 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.
2001:df7:dc80::/48 No ROA Other IRR onlyNTTCOM, RADB 636 100% 68
203.34.252.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
203.34.253.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 673 100% 67

AS-SET

AS17487 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 8 are in fix.csv.

  • ROA: none3
  • Route object: RIR1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none2001:df7:dc80::/48No ROA covers it. Add a ROA for AS17487, maxLength 48.636 of 636
Route object: RIR2001:df7:dc80::/48Route object only in NTTCOM, RADB. Add it in the RIR database for the space.636 of 636
ROA: none203.34.252.0/24No ROA covers it. Add a ROA for AS17487, maxLength 24.673 of 673
ROA: none203.34.253.0/24No ROA covers it. Add a ROA for AS17487, maxLength 24.673 of 673

Route objects not announced

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

202.66.24.0/24NTTCOM, RADBNo ROA
203.26.40.0/24APNIC, NTTCOM, RADBNo ROA
218.188.87.0/24APNIC, RADBValid
220.241.83.0/24APNIC, NTTCOM, 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.