bgpreport

Network · data from 2026-11-12

AS149296 TIANFENG-AS-AP - TIANFENG (HONG KONG) COMMUNICATIONS LIMITED

Registry name: TIANFENG-AS-AP - TIANFENG (HONG KONG) COMMUNICATIONS LIMITED, HK · not in PeeringDB

7IPv4 routes 85.7% RPKI valid · 85.7% with a route object
2IPv6 routes 100.0% RPKI valid · 100.0% with a route object
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
8Route objects not announced registered with origin AS149296, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS149296, 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.
43.255.55.9/32 Invalid: maxLength Nonecovered by 43.255.55.0/24 0 0%low visibility 1
79.109.1.0/24 Valid RIR databaseAPNIC 672 100% 67
113.212.88.0/24 Valid RIR databaseAPNIC 671 100% 67
43.255.52.0/24 Valid RIR databaseAPNIC 670 100% 67
43.255.55.0/24 Valid RIR databaseAPNIC 670 100% 67
103.129.54.0/24 Valid RIR databaseAPNIC 670 100% 67
43.255.54.0/24 Valid RIR databaseAPNIC 669 99% 67
2401:bbe0:200::/40 Valid RIR databaseAPNIC 635 100% 67
2401:bbe0:500::/40 Valid RIR databaseAPNIC 635 100% 67

AS-SET

AS149296 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 10 are in fix.csv.

  • ROA: maxLength1
  • Route object: none1
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: maxLength43.255.55.9/32ROA 43.255.55.0/24 AS149296 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 43.255.55.9/32.0 of 673
Route object: none43.255.55.9/32No route object for it. A route object for 43.255.55.0/24 with origin AS149296 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS149296 in the RIR database for the space.0 of 673

Route objects not announced

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

43.255.52.0/22RADBNo ROA
43.255.53.0/24APNIC, RADBValid
103.96.1.0/24APNICValid
103.129.52.0/22APNICValid
103.129.54.0/23APNICValid
103.129.55.0/24APNICValid
103.136.33.0/24APNICValid
160.30.128.0/23APNICValid

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.