bgpreport

Network · data from 2026-11-12

AS9513 HKCABLE-HK-AP - HK Cable TV Ltd

Registry name: HKCABLE-HK-AP - HK Cable TV Ltd, HK · not in PeeringDB

11IPv4 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
16Route objects not announced registered with origin AS9513, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS9513, 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.83.64.0/18 Valid Other IRR onlyRADB 672 100% 67
203.83.64.0/19 Valid RIR databaseAPNIC, RADB 672 100% 67
203.83.78.0/23 Valid RIR databaseAPNIC 672 100% 67
203.83.96.0/19 Valid RIR databaseAPNIC, RADB 672 100% 67
203.83.118.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
203.83.65.0/24 Valid RIR databaseAPNIC 670 100% 67
203.83.72.0/22 Valid RIR databaseAPNIC 670 100% 67
203.83.84.0/24 Valid RIR databaseAPNIC 670 100% 67
203.83.116.0/23 Valid RIR databaseAPNIC, RADB 670 100% 67
203.168.132.0/22 Valid RIR databaseAPNIC 670 100% 67
203.168.132.0/24 Valid RIR databaseAPNIC 670 100% 67

AS-SET

AS9513 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 17 are in fix.csv.

  • Route object: RIR1
  • Route object: not announced16
ChangePrefix or setDetailFull-table peers
Route object: RIR203.83.64.0/18Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

203.83.72.0/24APNICValid
203.83.73.0/24APNICValid
203.83.74.0/24APNICValid
203.83.75.0/24APNICValid
203.83.96.0/22APNICValid
203.83.110.0/24APNICValid
203.83.111.0/24APNICValid
203.83.114.0/23APNIC, RADBValid
203.83.116.0/22APNICValid
203.83.254.0/23RADBNo ROA
203.168.132.0/23APNICValid
203.168.133.0/24APNICValid
203.168.134.0/23APNICValid
203.168.134.0/24APNICValid
203.168.135.0/24APNICValid
210.80.60.0/24RADBNo 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.