bgpreport

Network · data from 2026-11-12

AS24441 CityLink Corporation, LTD

Registry name: CITYLINK-AS-KH - CityLink Corporation, LTD, KH · PeeringDB

43IPv4 routes 100.0% RPKI valid · 100.0% with a route object
11IPv6 routes 100.0% RPKI valid · 9.1% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 10 with no route object for this origin
10Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS24441, seen from no peer

Announced routes

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

2404:cc00::/36 Valid Nonecovered by 2404:cc00::/32 36 6%low visibility 29
2404:cc00::/48 Valid Nonecovered by 2404:cc00::/32 36 6%low visibility 29
2404:cc00:1::/48 Valid Nonecovered by 2404:cc00::/32 36 6%low visibility 29
2404:cc00:2::/48 Valid Nonecovered by 2404:cc00::/32 36 6%low visibility 29
2404:cc00:3::/48 Valid Nonecovered by 2404:cc00::/32 36 6%low visibility 29
2404:cc00:4::/48 Valid Nonecovered by 2404:cc00::/32 36 6%low visibility 29
2404:cc00:5::/48 Valid Nonecovered by 2404:cc00::/32 36 6%low visibility 29
2404:cc00:2222::/48 Valid Nonecovered by 2404:cc00::/32 36 6%low visibility 29
2404:cc00:8888::/48 Valid Nonecovered by 2404:cc00::/32 36 6%low visibility 29
2404:cc00:9999::/48 Valid Nonecovered by 2404:cc00::/32 36 6%low visibility 29
202.7.52.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 68
202.84.72.0/21 Valid Other IRR onlyNTTCOM, RADB 673 100% 68
202.93.8.0/21 Valid Other IRR onlyNTTCOM, RADB 673 100% 68
202.93.9.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 68
202.93.13.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 68
202.93.14.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 68
202.93.15.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 68
202.7.52.0/23 Valid Other IRR onlyNTTCOM, RADB 672 100% 68
202.7.52.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 68
202.7.53.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 68
202.7.54.0/23 Valid Other IRR onlyNTTCOM, RADB 672 100% 68
202.7.55.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 68
202.84.73.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 68
202.84.74.0/23 Valid Other IRR onlyNTTCOM, RADB 672 100% 68
202.84.74.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 68
202.84.76.0/22 Valid Other IRR onlyNTTCOM, RADB 672 100% 68
202.84.76.0/23 Valid Other IRR onlyNTTCOM, RADB 672 100% 68
202.84.76.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 68
202.84.77.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 68
202.84.78.0/23 Valid Other IRR onlyNTTCOM, RADB 672 100% 68
202.84.78.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 68
202.93.10.0/23 Valid Other IRR onlyNTTCOM, RADB 672 100% 68
202.93.10.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 68
202.93.11.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 68
202.93.12.0/22 Valid Other IRR onlyNTTCOM, RADB 672 100% 68
202.93.12.0/23 Valid Other IRR onlyNTTCOM, RADB 672 100% 68
202.93.12.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 68
202.93.14.0/23 Valid Other IRR onlyNTTCOM, RADB 672 100% 68
202.7.54.0/24 Valid Other IRR onlyNTTCOM, RADB 669 99% 68
2404:cc00::/32 Valid Other IRR onlyRADB 320 50% 63
202.84.75.0/24 Valid Other IRR onlyNTTCOM, RADB 218 32% 56
202.84.79.0/24 Valid Other IRR onlyNTTCOM, RADB 215 32% 56
103.28.242.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
202.84.72.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
202.93.8.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
103.5.230.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 68
103.5.230.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 68
103.5.231.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 68
103.28.242.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 68
103.28.243.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 68
202.84.72.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 68
202.84.72.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 68
202.93.8.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 68
202.93.8.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 68

AS-SET

AS24441'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 42 are in fix.csv.

  • Route object: none10
  • Route object: RIR32
ChangePrefix or setDetailFull-table peers
Route object: none2404:cc00::/36No route object for it. A route object for 2404:cc00::/32 with origin AS24441 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24441 in the RIR database for the space.36 of 636
Route object: none2404:cc00::/48No route object for it. A route object for 2404:cc00::/32 with origin AS24441 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24441 in the RIR database for the space.36 of 636
Route object: none2404:cc00:1::/48No route object for it. A route object for 2404:cc00::/32 with origin AS24441 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24441 in the RIR database for the space.36 of 636
Route object: none2404:cc00:2::/48No route object for it. A route object for 2404:cc00::/32 with origin AS24441 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24441 in the RIR database for the space.36 of 636
Route object: none2404:cc00:3::/48No route object for it. A route object for 2404:cc00::/32 with origin AS24441 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24441 in the RIR database for the space.36 of 636
Route object: none2404:cc00:4::/48No route object for it. A route object for 2404:cc00::/32 with origin AS24441 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24441 in the RIR database for the space.36 of 636
Route object: none2404:cc00:5::/48No route object for it. A route object for 2404:cc00::/32 with origin AS24441 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24441 in the RIR database for the space.36 of 636
Route object: none2404:cc00:2222::/48No route object for it. A route object for 2404:cc00::/32 with origin AS24441 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24441 in the RIR database for the space.36 of 636
Route object: none2404:cc00:8888::/48No route object for it. A route object for 2404:cc00::/32 with origin AS24441 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24441 in the RIR database for the space.36 of 636
Route object: none2404:cc00:9999::/48No route object for it. A route object for 2404:cc00::/32 with origin AS24441 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24441 in the RIR database for the space.36 of 636
Route object: RIR202.7.52.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.84.72.0/21Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.93.8.0/21Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.93.9.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.93.13.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.93.14.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.93.15.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.7.52.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.7.52.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.7.53.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.7.54.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.7.55.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.84.73.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.84.74.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.84.74.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.84.76.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.84.76.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.84.76.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.84.77.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.84.78.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.84.78.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.93.10.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.93.10.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.93.11.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.93.12.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.93.12.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.93.12.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.93.14.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.7.54.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR2404:cc00::/32Route object only in RADB. Add it in the RIR database for the space.320 of 636
Route object: RIR202.84.75.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.218 of 673
Route object: RIR202.84.79.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.215 of 673

Route objects not announced

Every route object with origin AS24441 is announced.

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.