Network · data from 2026-11-12

AS23749 GLOBAL-TRANSIT-AS-HKCOLO-AP - HKCOLO ltd. Internet Service Provider

Registry name: GLOBAL-TRANSIT-AS-HKCOLO-AP - HKCOLO ltd. Internet Service Provider, HK · not in PeeringDB

19IPv4 routes 84.2% RPKI valid · 100.0% with a route object

3IPv6 routes 100.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

27Route objects not announced registered with origin AS23749, seen from no peer

Announced routes

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


112.213.79.0/24	No ROA	Other IRR onlyNTTCOM	172 26%	55
202.122.96.0/21	No ROA	RIR databaseAPNIC, NTTCOM	670 100%	68
202.122.104.0/22	No ROA	RIR databaseAPNIC	670 100%	68
112.213.69.0/24	Valid	RIR databaseAPNIC, NTTCOM	673 100%	67
202.122.96.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	67
202.122.97.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	67
202.122.98.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	67
202.122.100.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	67
202.122.103.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	67
202.122.104.0/24	Valid	RIR databaseAPNIC, NTTCOM	673 100%	67
202.122.107.0/24	Valid	RIR databaseAPNIC, NTTCOM	673 100%	67
202.122.108.0/23	Valid	RIR databaseAPNIC	673 100%	67
202.122.102.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	67
202.122.99.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	671 100%	68
202.122.105.0/24	Valid	RIR databaseAPNIC, NTTCOM	671 100%	68
202.122.106.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	671 100%	68
202.122.109.0/24	Valid	RIR databaseAPNIC, NTTCOM	671 100%	67
112.213.64.0/24	Valid	RIR databaseAPNIC, NTTCOM	670 100%	68
2401:3c60:1::/48	Valid	RIR databaseAPNIC	636 100%	69
2401:3c60::/32	Valid	RIR databaseAPNIC	635 100%	69
2401:3c60:2::/48	Valid	RIR databaseAPNIC	634 100%	69
202.122.110.0/24	Valid	RIR databaseAPNIC, NTTCOM	172 26%	55

AS-SET

AS23749 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 31 are in fix.csv.

ROA: none3
Route object: RIR1
Route object: not announced27

Change	Prefix or set	Detail	Full-table peers
ROA: none	112.213.79.0/24	No ROA covers it. Add a ROA for AS23749, maxLength 24.	172 of 673
Route object: RIR	112.213.79.0/24	Route object only in NTTCOM. Add it in the RIR database for the space.	172 of 673
ROA: none	202.122.96.0/21	No ROA covers it. Add a ROA for AS23749, maxLength 21.	670 of 673
ROA: none	202.122.104.0/22	No ROA covers it. Add a ROA for AS23749, maxLength 22.	670 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

112.213.79.0/24

No ROA covers it. Add a ROA for AS23749, maxLength 24.

172 of 673

Route object: RIR

112.213.79.0/24

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

172 of 673

ROA: none

202.122.96.0/21

No ROA covers it. Add a ROA for AS23749, maxLength 21.

670 of 673

ROA: none

202.122.104.0/22

No ROA covers it. Add a ROA for AS23749, maxLength 22.

670 of 673

Route objects not announced

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


112.213.64.0/20	APNIC, NTTCOM, REACH	No ROA
112.213.64.0/21	NTTCOM	No ROA
112.213.64.0/22	NTTCOM	No ROA
112.213.64.0/23	NTTCOM	No ROA
112.213.65.0/24	APNIC, NTTCOM	Valid
112.213.66.0/24	APNIC, NTTCOM	Valid
112.213.67.0/24	APNIC, NTTCOM	Valid
112.213.68.0/22	APNIC	Valid
112.213.68.0/24	APNIC, NTTCOM	Valid
112.213.70.0/24	APNIC, NTTCOM	Valid
112.213.71.0/24	APNIC, NTTCOM	Valid
112.213.72.0/22	APNIC	Valid
112.213.72.0/24	APNIC, NTTCOM	Valid
112.213.73.0/24	APNIC, NTTCOM	Valid
112.213.74.0/24	APNIC, NTTCOM	Valid
112.213.75.0/24	APNIC, NTTCOM	Valid
112.213.76.0/24	APNIC, NTTCOM	No ROA
112.213.77.0/24	NTTCOM	No ROA
112.213.78.0/24	NTTCOM	No ROA
202.122.96.0/20	APNIC, NTTCOM, RADB, REACH	No ROA
202.122.96.0/22	NTTCOM	No ROA
202.122.96.0/23	NTTCOM	No ROA
202.122.101.0/24	APNIC, NTTCOM, RADB	Valid
202.122.108.0/24	APNIC, NTTCOM, RADB	Valid
202.122.111.0/24	APNIC, NTTCOM	No ROA
202.165.124.0/24	REACH	Invalid: origin
2001:470:39d::/48	ARIN	Valid

112.213.64.0/20

APNIC, NTTCOM, REACH

No ROA

112.213.64.0/21

NTTCOM

No ROA

112.213.64.0/22

NTTCOM

No ROA

112.213.64.0/23

NTTCOM

No ROA

112.213.65.0/24

APNIC, NTTCOM

Valid

112.213.66.0/24

APNIC, NTTCOM

Valid

112.213.67.0/24

APNIC, NTTCOM

Valid

112.213.68.0/22

APNIC

Valid

112.213.68.0/24

APNIC, NTTCOM

Valid

112.213.70.0/24

APNIC, NTTCOM

Valid

112.213.71.0/24

APNIC, NTTCOM

Valid

112.213.72.0/22

APNIC

Valid

112.213.72.0/24

APNIC, NTTCOM

Valid

112.213.73.0/24

APNIC, NTTCOM

Valid

112.213.74.0/24

APNIC, NTTCOM

Valid

112.213.75.0/24

APNIC, NTTCOM

Valid

112.213.76.0/24

APNIC, NTTCOM

No ROA

112.213.77.0/24

NTTCOM

No ROA

112.213.78.0/24

NTTCOM

No ROA

202.122.96.0/20

APNIC, NTTCOM, RADB, REACH

No ROA

202.122.96.0/22

NTTCOM

No ROA

202.122.96.0/23

NTTCOM

No ROA

202.122.101.0/24

APNIC, NTTCOM, RADB

Valid

202.122.108.0/24

APNIC, NTTCOM, RADB

Valid

202.122.111.0/24

APNIC, NTTCOM

No ROA

202.165.124.0/24

REACH

Invalid: origin

2001:470:39d::/48

ARIN

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.