bgpreport

Network · data from 2026-11-12

AS10116 HTCL-WAP-HK-AP - Hutchison Telephone Company Limited

Registry name: HTCL-WAP-HK-AP - Hutchison Telephone Company Limited, HK · not in PeeringDB

1IPv4 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 AS10116, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS10116, 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.145.64.0/21 Valid Other IRR onlyNTTCOM, RADB 671 100% 67

AS-SET

AS10116 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.145.64.0/21Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

203.145.64.0/19RADBNo ROA
203.145.64.0/20RADBNo ROA
203.145.64.0/22RADBValid
203.145.64.0/23RADBValid
203.145.64.0/24RADBValid
203.145.65.0/24RADBValid
203.145.66.0/23RADBValid
203.145.66.0/24RADBValid
203.145.67.0/24RADBValid
203.145.68.0/22RADBValid
203.145.68.0/23RADBValid
203.145.68.0/24RADBValid
203.145.69.0/24RADBValid
203.145.70.0/23RADBValid
203.145.70.0/24RADBValid
203.145.71.0/24RADBValid

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.