bgpreport

Network · data from 2026-11-12

AS24247 PACKETFABRIC-AS-AP - PacketFabric (Hong Kong) Limited

Registry name: PACKETFABRIC-AS-AP - PacketFabric (Hong Kong) Limited, HK · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS24247, 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.
117.20.45.0/24 No ROA Nonecovered by 117.20.44.0/22 673 100% 66
63.251.110.0/23 No ROA Other IRR onlyRADB 673 100% 66
63.251.111.0/24 No ROA Other IRR onlyRADB 673 100% 66
117.20.44.0/22 No ROA Other IRR onlyRADB 673 100% 66
202.58.8.0/21 No ROA Other IRR onlyRADB, REACH 673 100% 66
216.223.38.0/23 No ROA Other IRR onlyRADB 673 100% 66
2405:d800::/32 No ROA Other IRR onlyRADB 541 85% 67
117.20.43.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66

AS-SET

AS24247 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 36 are in fix.csv.

  • ROA: none7
  • Route object: none1
  • Route object: RIR6
  • Route object: not announced22
ChangePrefix or setDetailFull-table peers
ROA: none117.20.45.0/24No ROA covers it. Add a ROA for AS24247, maxLength 24.673 of 673
Route object: none117.20.45.0/24No route object for it. A route object for 117.20.44.0/22 with origin AS24247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24247 in the RIR database for the space.673 of 673
ROA: none63.251.110.0/23No ROA covers it. Add a ROA for AS24247, maxLength 23.673 of 673
Route object: RIR63.251.110.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none63.251.111.0/24No ROA covers it. Add a ROA for AS24247, maxLength 24.673 of 673
Route object: RIR63.251.111.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none117.20.44.0/22No ROA covers it. Add a ROA for AS24247, maxLength 22.673 of 673
Route object: RIR117.20.44.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none202.58.8.0/21No ROA covers it. Add a ROA for AS24247, maxLength 21.673 of 673
Route object: RIR202.58.8.0/21Route object only in RADB, REACH. Add it in the RIR database for the space.673 of 673
ROA: none216.223.38.0/23No ROA covers it. Add a ROA for AS24247, maxLength 23.673 of 673
Route object: RIR216.223.38.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none2405:d800::/32No ROA covers it. Add a ROA for AS24247, maxLength 32.541 of 636
Route object: RIR2405:d800::/32Route object only in RADB. Add it in the RIR database for the space.541 of 636

Route objects not announced

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

63.251.96.0/22RADBNo ROA
64.94.96.0/24RADBNo ROA
66.150.58.0/24RADBNo ROA
69.25.81.0/24RADBNo ROA
72.5.83.0/24RADBNo ROA
82.150.107.0/24RADBNo ROA
103.209.194.0/24RADBNo ROA
117.20.40.0/21REACHNo ROA
117.20.40.0/23RADBNo ROA
119.59.78.0/23RADBNo ROA
119.59.78.0/24RADBNo ROA
194.164.107.0/24RADBNo ROA
199.166.217.0/24RADBNo ROA
202.58.8.0/24RADBNo ROA
202.58.11.0/24RADBNo ROA
202.58.12.0/24REACHNo ROA
202.58.14.96/27RADBNo ROA
202.172.4.0/24NTTCOMNo ROA
203.92.210.0/24REACHNo ROA
216.147.220.0/24RADBNo ROA
216.223.39.0/24RADBNo ROA
2620:f0:c005::/48RADBNo 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.