bgpreport

Network · data from 2026-11-12

AS135357 PCCW22-HK - HONG KONG KOWLOON TELECOMMUNICATIONS CO.,LIMITED

Registry name: PCCW22-HK - HONG KONG KOWLOON TELECOMMUNICATIONS CO.,LIMITED, HK · not in PeeringDB

24IPv4 routes 95.8% RPKI valid · 95.8% with a route object
0IPv6 routes
1RPKI invalid 0 origin · 1 maxLength
0No ROA 1 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
65Route objects not announced registered with origin AS135357, seen from no peer

Announced routes

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

103.30.6.149/32 Invalid: maxLength Nonecovered by 103.30.6.0/24 0 0%low visibility 1
103.41.16.0/22 Valid RIR databaseAPNIC, RADB 673 100% 66
103.41.17.0/24 Valid RIR databaseAPNIC 673 100% 67
206.161.216.0/24 Valid RIR databaseAPNIC 673 100% 67
206.161.217.0/24 Valid RIR databaseAPNIC 673 100% 67
207.226.136.0/24 Valid RIR databaseAPNIC 673 100% 67
207.226.137.0/24 Valid RIR databaseAPNIC 673 100% 67
207.226.138.0/24 Valid RIR databaseAPNIC 673 100% 67
43.240.144.0/22 Valid RIR databaseAPNIC, RADB 672 100% 67
103.17.116.0/22 Valid RIR databaseAPNIC, RADB 672 100% 67
103.20.192.0/22 Valid RIR databaseAPNIC, RADB 672 100% 67
103.24.92.0/22 Valid RIR databaseAPNIC, RADB 672 100% 67
103.27.176.0/22 Valid RIR databaseAPNIC, RADB 672 100% 67
103.30.4.0/22 Valid RIR databaseAPNIC, RADB 672 100% 67
103.212.228.0/22 Valid RIR databaseAPNIC, RADB 672 100% 67
103.215.48.0/22 Valid RIR databaseAPNIC, RADB 672 100% 67
103.226.152.0/22 Valid RIR databaseAPNIC, RADB 672 100% 67
103.234.96.0/22 Valid RIR databaseAPNIC, RADB 672 100% 67
103.244.148.0/22 Valid RIR databaseAPNIC, RADB 672 100% 67
160.202.168.0/22 Valid RIR databaseAPNIC, RADB 672 100% 67
185.216.248.0/22 Valid RIR databaseRADB, RIPE 672 100% 67
202.8.120.0/22 Valid RIR databaseAPNIC, RADB 672 100% 67
206.161.218.0/24 Valid RIR databaseAPNIC 670 100% 67
144.48.220.0/22 Valid RIR databaseAPNIC, RADB 669 99% 67

AS-SET

AS135357 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 67 are in fix.csv.

  • ROA: maxLength1
  • Route object: none1
  • Route object: not announced65
ChangePrefix or setDetailFull-table peers
ROA: maxLength103.30.6.149/32ROA 103.30.4.0/22 AS135357 has maxLength 22; ROA 103.30.6.0/24 AS135357 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 103.30.6.149/32.0 of 673
Route object: none103.30.6.149/32No route object for it. A route object for 103.30.6.0/24 with origin AS135357 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS135357 in the RIR database for the space.0 of 673

Route objects not announced

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

38.181.128.0/17RADBNo ROA
38.249.0.0/16RADBNo ROA
43.240.144.0/24APNICValid
43.240.145.0/24APNICValid
43.240.146.0/24APNICValid
43.240.147.0/24APNICValid
103.17.116.0/24APNICValid
103.17.117.0/24APNICValid
103.17.118.0/24APNICValid
103.17.119.0/24APNICValid
103.20.192.0/24APNICValid
103.20.193.0/24APNICValid
103.20.194.0/24APNICValid
103.20.195.0/24APNICValid
103.24.92.0/24APNICValid
103.24.93.0/24APNICValid
103.24.94.0/24APNICValid
103.24.95.0/24APNICValid
103.27.176.0/24APNICValid
103.27.177.0/24APNICValid
103.27.178.0/24APNICValid
103.27.179.0/24APNICValid
103.30.4.0/24APNICValid
103.30.5.0/24APNICValid
103.30.6.0/24APNICValid
103.30.7.0/24APNICValid
103.41.16.0/24APNICValid
103.41.18.0/24APNICValid
103.41.19.0/24APNICValid
103.212.228.0/24APNICValid
103.212.229.0/24APNICValid
103.212.230.0/24APNICValid
103.212.231.0/24APNICValid
103.215.48.0/24APNICValid
103.215.49.0/24APNICValid
103.215.50.0/24APNICValid
103.215.51.0/24APNICValid
103.226.152.0/24APNICValid
103.226.153.0/24APNICValid
103.226.154.0/24APNICValid
103.226.155.0/24APNICValid
103.234.96.0/24APNICValid
103.234.97.0/24APNICValid
103.234.98.0/24APNICValid
103.234.99.0/24APNICValid
103.244.148.0/24APNICValid
103.244.149.0/24APNICValid
103.244.150.0/24APNICValid
103.244.151.0/24APNICValid
144.48.220.0/24APNICValid
144.48.221.0/24APNICValid
144.48.222.0/24APNICValid
144.48.223.0/24APNICValid
160.202.168.0/24APNICValid
160.202.169.0/24APNICValid
160.202.170.0/24APNICValid
160.202.171.0/24APNICValid
185.216.248.0/24RIPEValid
185.216.249.0/24RIPEValid
185.216.250.0/24RIPEValid
185.216.251.0/24RIPEValid
202.8.120.0/24APNICValid
202.8.121.0/24APNICValid
202.8.122.0/24APNICValid
202.8.123.0/24APNICValid

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.