bgpreport

Network · data from 2026-11-12

AS9263 PCCW-IMSBIZ-AP - HKT Limited

Registry name: PCCW-IMSBIZ-AP - HKT Limited, HK · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS9263, 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.233.164.0/22 No ROA Other origin only 172 26% 55
220.241.255.0/24 No ROA RIR databaseAPNIC, RADB 673 100% 67

AS-SET

AS9263 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 14 are in fix.csv.

  • ROA: none2
  • Route object: none1
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
ROA: none103.233.164.0/22No ROA covers it. Add a ROA for AS9263, maxLength 22.172 of 673
Route object: none103.233.164.0/22Route objects for it name AS4515. Add a route object with origin AS9263 in the RIR database for the space.172 of 673
ROA: none220.241.255.0/24No ROA covers it. Add a ROA for AS9263, maxLength 24.673 of 673

Route objects not announced

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

175.29.0.0/18RADBNo ROA
202.69.92.0/22APNICNo ROA
203.198.168.0/21APNICValid
2400:c800::/32RADBNo ROA
2400:c801::/32RADBNo ROA
2400:c802::/32RADBNo ROA
2400:c803::/32RADBNo ROA
2400:c804::/32RADBNo ROA
2400:c805::/32RADBNo ROA
2400:c806::/32RADBNo ROA
2400:c807::/32APNIC, RADBNo 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.