Network · data from 2026-11-12

AS153656 HKISP-AS-AP - OWGELS INTERNATIONAL CO., LIMITED

Registry name: HKISP-AS-AP - OWGELS INTERNATIONAL CO., LIMITED, HK · not in PeeringDB

17IPv4 routes 100.0% RPKI valid · 100.0% with a route object

0IPv6 routes

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

2Route objects not announced registered with origin AS153656, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS153656, 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.197.141.0/24	Valid	Other IRR onlyRADB	671 100%	66
154.197.154.0/24	Valid	Other IRR onlyRADB	671 100%	66
155.117.12.0/24	Valid	Other IRR onlyRADB	670 100%	67
155.117.98.0/24	Valid	Other IRR onlyRADB	670 100%	67
82.41.66.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
45.135.237.0/24	Valid	RIR databaseRIPE	672 100%	67
103.140.154.0/24	Valid	RIR databaseAPNIC	672 100%	66
141.11.88.0/24	Valid	RIR databaseRADB, RIPE	672 100%	66
103.163.208.0/24	Valid	RIR databaseAPNIC	670 100%	67
103.165.81.0/24	Valid	RIR databaseAPNIC	670 100%	67
163.8.216.0/24	Valid	RIR databaseAPNIC, RADB	670 100%	67
166.88.26.0/24	Valid	RIR databaseARIN, RADB	670 100%	67
168.222.65.0/24	Valid	RIR databaseRADB, RIPE	670 100%	67
179.61.182.0/24	Valid	RIR databaseRADB, RIPE	670 100%	67
202.71.4.0/24	Valid	RIR databaseRIPE	670 100%	67
87.84.204.0/24	Valid	RIR databaseRADB, RIPE	669 99%	67
104.234.194.0/24	Valid	RIR databaseARIN, RADB	668 99%	67

AS-SET

AS153656 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 6 are in fix.csv.

Route object: RIR4
Route object: not announced2

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	154.197.141.0/24	Route object only in RADB. Add it in the RIR database for the space.	671 of 673
Route object: RIR	154.197.154.0/24	Route object only in RADB. Add it in the RIR database for the space.	671 of 673
Route object: RIR	155.117.12.0/24	Route object only in RADB. Add it in the RIR database for the space.	670 of 673
Route object: RIR	155.117.98.0/24	Route object only in RADB. Add it in the RIR database for the space.	670 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

154.197.141.0/24

Route object only in RADB. Add it in the RIR database for the space.

671 of 673

Route object: RIR

154.197.154.0/24

Route object only in RADB. Add it in the RIR database for the space.

671 of 673

Route object: RIR

155.117.12.0/24

Route object only in RADB. Add it in the RIR database for the space.

670 of 673

Route object: RIR

155.117.98.0/24

Route object only in RADB. Add it in the RIR database for the space.

670 of 673

Route objects not announced

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


156.254.32.0/19	AFRINIC, RADB	Valid
156.254.64.0/19	AFRINIC, RADB	Valid

156.254.32.0/19

AFRINIC, RADB

Valid

156.254.64.0/19

AFRINIC, RADB

Valid

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.