bgpreport

Network · data from 2026-11-12

AS17814 COMNET-AP-ASN2 - ComNet Telecom International Ltd. AS number.

Registry name: COMNET-AP-ASN2 - ComNet Telecom International Ltd. AS number., HK · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS17814, 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.160.33.0/24 No ROA Nonecovered by 203.160.32.0/20 673 100% 67
202.0.164.0/24 No ROA RIR databaseAPNIC 673 100% 66
202.86.65.0/24 No ROA RIR databaseAPNIC 673 100% 66

AS-SET

AS17814 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 20 are in fix.csv.

  • ROA: none3
  • Route object: none1
  • Route object: not announced16
ChangePrefix or setDetailFull-table peers
ROA: none203.160.33.0/24No ROA covers it. Add a ROA for AS17814, maxLength 24.673 of 673
Route object: none203.160.33.0/24No route object for it. A route object for 203.160.32.0/20 with origin AS17814 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17814 in the RIR database for the space.673 of 673
ROA: none202.0.164.0/24No ROA covers it. Add a ROA for AS17814, maxLength 24.673 of 673
ROA: none202.86.65.0/24No ROA covers it. Add a ROA for AS17814, maxLength 24.673 of 673

Route objects not announced

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

202.0.160.0/20APNIC, NTTCOM, REACHNo ROA
202.0.163.0/24APNICNo ROA
202.0.167.0/24APNICNo ROA
202.0.168.0/24APNICNo ROA
202.0.170.0/24APNICNo ROA
202.0.171.0/24APNICNo ROA
202.0.172.0/24APNICNo ROA
202.0.173.0/24APNICNo ROA
202.0.174.0/24APNICNo ROA
202.0.175.0/24APNICNo ROA
202.0.176.0/22APNIC, NTTCOM, REACHNo ROA
202.0.178.0/24APNICNo ROA
202.0.179.0/24APNICNo ROA
202.86.64.0/19APNIC, NTTCOM, REACHNo ROA
202.86.66.0/24APNICNo ROA
203.160.32.0/20NTTCOM, REACHNo 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.