bgpreport

Network · data from 2026-11-12

AS141159 INCOMPARABLEHKNET-AS-AP - Incomparable(HK)Network Co., Limited

Registry name: INCOMPARABLEHKNET-AS-AP - Incomparable(HK)Network Co., Limited, HK · not in PeeringDB

22IPv4 routes 36.4% RPKI valid · 59.1% with a route object
0IPv6 routes
10RPKI invalid 10 origin · 0 maxLength
4No ROA 9 with no route object for this origin
10Low visibility seen by under 10% of full-table peers
14Route objects not announced registered with origin AS141159, seen from no peer

Announced routes

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

154.31.20.0/24 Invalid: origin None 80 12% 33
154.31.23.0/24 Invalid: origin None 7 1%low visibility 4
154.31.26.0/24 Invalid: origin None 7 1%low visibility 4
154.31.31.0/24 Invalid: origin None 7 1%low visibility 4
206.2.220.0/24 Invalid: origin None 7 1%low visibility 4
206.2.221.0/24 Invalid: origin None 7 1%low visibility 4
154.94.224.0/23 Invalid: origin None 2 0%low visibility 1
156.233.230.0/23 Invalid: origin None 2 0%low visibility 1
103.146.125.0/24 Invalid: origin Other origin onlycovered by 103.146.124.0/23 1 0%low visibility 1
45.205.16.0/21 Invalid: origin RIR databaseAFRINIC 2 0%low visibility 2
101.55.82.0/24 No ROA Other IRR onlyRADB 673 100% 66
103.146.124.0/23 No ROA Other IRR onlyRADB 654 97% 67
103.155.122.0/24 No ROA RIR databaseAPNIC, RADB 670 100% 69
103.155.123.0/24 No ROA RIR databaseAPNIC, RADB 670 100% 69
154.94.228.0/22 Valid Other IRR onlyRADB 18 3%low visibility 12
103.167.54.0/24 Valid RIR databaseAPNIC, RADB 671 100% 69
103.167.55.0/24 Valid RIR databaseAPNIC, RADB 671 100% 69
103.178.57.0/24 Valid RIR databaseAPNIC 671 100% 69
45.205.16.0/23 Valid RIR databaseAFRINIC, RADB 651 97% 67
45.205.16.0/24 Valid RIR databaseAFRINIC 647 96% 67
45.205.17.0/24 Valid RIR databaseAFRINIC 647 96% 67
103.146.124.0/24 Valid RIR databaseAPNIC 643 96% 67

AS-SET

AS141159 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 40 are in fix.csv.

  • ROA: origin10
  • ROA: none4
  • Route object: none9
  • Route object: RIR3
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
ROA: origin154.31.20.0/24ROAs covering it name AS215787, not AS141159. If AS141159 should announce it, add a ROA for AS141159.80 of 673
Route object: none154.31.20.0/24No route object for it. Add a route object with origin AS141159 in the RIR database for the space.80 of 673
ROA: origin154.31.23.0/24ROAs covering it name AS215787, not AS141159. If AS141159 should announce it, add a ROA for AS141159.7 of 673
Route object: none154.31.23.0/24No route object for it. Add a route object with origin AS141159 in the RIR database for the space.7 of 673
ROA: origin154.31.26.0/24ROAs covering it name AS215787, not AS141159. If AS141159 should announce it, add a ROA for AS141159.7 of 673
Route object: none154.31.26.0/24No route object for it. Add a route object with origin AS141159 in the RIR database for the space.7 of 673
ROA: origin154.31.31.0/24ROAs covering it name AS215787, not AS141159. If AS141159 should announce it, add a ROA for AS141159.7 of 673
Route object: none154.31.31.0/24No route object for it. Add a route object with origin AS141159 in the RIR database for the space.7 of 673
ROA: origin206.2.220.0/24ROAs covering it name AS269816, not AS141159. If AS141159 should announce it, add a ROA for AS141159.7 of 673
Route object: none206.2.220.0/24No route object for it. Add a route object with origin AS141159 in the RIR database for the space.7 of 673
ROA: origin206.2.221.0/24ROAs covering it name AS269816, not AS141159. If AS141159 should announce it, add a ROA for AS141159.7 of 673
Route object: none206.2.221.0/24No route object for it. Add a route object with origin AS141159 in the RIR database for the space.7 of 673
ROA: origin154.94.224.0/23ROAs covering it name AS8796, AS40779, AS137899, AS142032, AS395886, AS401696, AS401701, not AS141159. If AS141159 should announce it, add a ROA for AS141159.2 of 673
Route object: none154.94.224.0/23No route object for it. Add a route object with origin AS141159 in the RIR database for the space.2 of 673
ROA: origin156.233.230.0/23ROAs covering it name AS8796, AS40779, AS137899, AS142032, AS395886, AS401696, AS401701, not AS141159. If AS141159 should announce it, add a ROA for AS141159.2 of 673
Route object: none156.233.230.0/23No route object for it. Add a route object with origin AS141159 in the RIR database for the space.2 of 673
ROA: origin103.146.125.0/24ROAs covering it name AS401696, not AS141159. If AS141159 should announce it, add a ROA for AS141159.1 of 673
Route object: none103.146.125.0/24Route objects for it name AS401696. A route object for 103.146.124.0/23 with origin AS141159 covers it (filters allowing more-specifics accept it). Add a route object with origin AS141159 in the RIR database for the space.1 of 673
ROA: origin45.205.16.0/21ROAs covering it name AS8796, AS40779, AS137899, AS142032, AS395886, AS401696, AS401701, not AS141159. If AS141159 should announce it, add a ROA for AS141159.2 of 673
ROA: none101.55.82.0/24No ROA covers it. Add a ROA for AS141159, maxLength 24.673 of 673
Route object: RIR101.55.82.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none103.146.124.0/23No ROA covers it. Add a ROA for AS141159, maxLength 23.654 of 673
Route object: RIR103.146.124.0/23Route object only in RADB. Add it in the RIR database for the space.654 of 673
ROA: none103.155.122.0/24No ROA covers it. Add a ROA for AS141159, maxLength 24.670 of 673
ROA: none103.155.123.0/24No ROA covers it. Add a ROA for AS141159, maxLength 24.670 of 673
Route object: RIR154.94.228.0/22Route object only in RADB. Add it in the RIR database for the space.18 of 673

Route objects not announced

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

45.205.18.0/24AFRINICValid
45.205.19.0/24AFRINICValid
45.205.20.0/24AFRINICValid
103.117.138.0/23APNICValid
103.117.138.0/24APNICValid
103.117.139.0/24APNICValid
103.155.122.0/23RADBNo ROA
103.158.36.0/24NTTCOM, RADBNo ROA
103.167.54.0/23RADBNo ROA
154.94.228.0/24RADBValid
154.94.229.0/24RADBValid
154.94.230.0/24RADBValid
154.94.231.0/24RADBValid
155.235.228.0/22RADBNo 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.