bgpreport

Network · data from 2026-11-12

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

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS149430, 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.
172.252.59.0/24 Invalid: origin Other origin only 1 0%low visibility 1
45.192.134.0/23 Valid Other IRR onlyRADB 671 100% 67
103.158.83.0/24 Valid RIR databaseAPNIC 672 100% 67
122.10.100.0/24 Valid RIR databaseAPNIC 672 100% 67
122.10.102.0/24 Valid RIR databaseAPNIC 672 100% 67
43.255.53.0/24 Valid RIR databaseAPNIC 671 100% 67

AS-SET

AS149430 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 4 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin172.252.59.0/24ROAs covering it name AS212238, not AS149430. If AS149430 should announce it, add a ROA for AS149430.1 of 673
Route object: none172.252.59.0/24Route objects for it name AS212238. Add a route object with origin AS149430 in the RIR database for the space.1 of 673
Route object: RIR45.192.134.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

103.129.55.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.