bgpreport

Network · data from 2026-11-12

AS17537 Jardine OneSolution (HK)

Registry name: JOSNSCHKAS-AP - HKBN JOS Synergy (HK) Limited, HK · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS17537, 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.
203.189.160.1/32 No ROA Nonecovered by 203.189.160.0/24 2 0%low visibility 7
203.189.160.0/20 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
203.189.160.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
203.189.161.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
203.189.162.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
203.189.163.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
203.189.164.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
203.189.165.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
203.189.166.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
203.189.167.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
203.189.169.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
203.189.170.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
203.189.171.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
203.189.172.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
203.189.173.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
203.189.174.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
203.189.175.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
2403:5500::/32 No ROA Other IRR onlyRADB 636 100% 70
203.189.168.0/24 No ROA Other IRR onlyNTTCOM, RADB 172 26% 55

AS-SET

AS17537's PeeringDB record names no 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 52 are in fix.csv.

  • ROA: none19
  • Route object: none1
  • Route object: RIR18
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
ROA: none203.189.160.1/32No ROA covers it. Add a ROA for AS17537, maxLength 32.2 of 673
Route object: none203.189.160.1/32No route object for it. A route object for 203.189.160.0/24 with origin AS17537 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS17537 in the RIR database for the space.2 of 673
ROA: none203.189.160.0/20No ROA covers it. Add a ROA for AS17537, maxLength 20.672 of 673
Route object: RIR203.189.160.0/20Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.189.160.0/24No ROA covers it. Add a ROA for AS17537, maxLength 24.672 of 673
Route object: RIR203.189.160.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.189.161.0/24No ROA covers it. Add a ROA for AS17537, maxLength 24.672 of 673
Route object: RIR203.189.161.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.189.162.0/24No ROA covers it. Add a ROA for AS17537, maxLength 24.672 of 673
Route object: RIR203.189.162.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.189.163.0/24No ROA covers it. Add a ROA for AS17537, maxLength 24.672 of 673
Route object: RIR203.189.163.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.189.164.0/24No ROA covers it. Add a ROA for AS17537, maxLength 24.672 of 673
Route object: RIR203.189.164.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.189.165.0/24No ROA covers it. Add a ROA for AS17537, maxLength 24.672 of 673
Route object: RIR203.189.165.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.189.166.0/24No ROA covers it. Add a ROA for AS17537, maxLength 24.672 of 673
Route object: RIR203.189.166.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.189.167.0/24No ROA covers it. Add a ROA for AS17537, maxLength 24.672 of 673
Route object: RIR203.189.167.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.189.169.0/24No ROA covers it. Add a ROA for AS17537, maxLength 24.672 of 673
Route object: RIR203.189.169.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.189.170.0/24No ROA covers it. Add a ROA for AS17537, maxLength 24.672 of 673
Route object: RIR203.189.170.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.189.171.0/24No ROA covers it. Add a ROA for AS17537, maxLength 24.672 of 673
Route object: RIR203.189.171.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.189.172.0/24No ROA covers it. Add a ROA for AS17537, maxLength 24.672 of 673
Route object: RIR203.189.172.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.189.173.0/24No ROA covers it. Add a ROA for AS17537, maxLength 24.672 of 673
Route object: RIR203.189.173.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.189.174.0/24No ROA covers it. Add a ROA for AS17537, maxLength 24.672 of 673
Route object: RIR203.189.174.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.189.175.0/24No ROA covers it. Add a ROA for AS17537, maxLength 24.672 of 673
Route object: RIR203.189.175.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none2403:5500::/32No ROA covers it. Add a ROA for AS17537, maxLength 32.636 of 636
Route object: RIR2403:5500::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none203.189.168.0/24No ROA covers it. Add a ROA for AS17537, maxLength 24.172 of 673
Route object: RIR203.189.168.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.172 of 673

Route objects not announced

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

203.189.160.0/21NTTCOM, RADBNo ROA
203.189.160.0/22NTTCOM, RADBNo ROA
203.189.160.0/23NTTCOM, RADBNo ROA
203.189.162.0/23NTTCOM, RADBNo ROA
203.189.164.0/22NTTCOM, RADBNo ROA
203.189.164.0/23NTTCOM, RADBNo ROA
203.189.166.0/23NTTCOM, RADBNo ROA
203.189.168.0/21NTTCOM, RADBNo ROA
203.189.168.0/22NTTCOM, RADBNo ROA
203.189.168.0/23NTTCOM, RADBNo ROA
203.189.170.0/23NTTCOM, RADBNo ROA
203.189.172.0/22NTTCOM, RADBNo ROA
203.189.172.0/23NTTCOM, RADBNo ROA
203.189.174.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.