bgpreport

Network · data from 2026-11-12

AS199779 HONGKONG FIAREFAST TECH

Registry name: FIAREFAST-AS HONGKONG FIAREFAST TECH LIMITED, HK · PeeringDB

4IPv4 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
2Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS199779, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS199779, 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.
164.37.229.0/24 Valid RIR databaseRADB, RIPE 673 100% 70
169.40.150.0/24 Valid RIR databaseRADB, RIPE 672 100% 70
153.43.227.0/24 Valid RIR databaseARIN 1 0%low visibility 1
153.43.228.0/24 Valid RIR databaseARIN 1 0%low visibility 1

AS-SET

AS199779's PeeringDB record names no 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 3 are in fix.csv.

  • Route object: not announced3

Route objects not announced

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

141.11.79.0/24RADB, RIPEValid
2a13:9500:185::/48RIPEValid
2a13:9500:186::/48RIPEValid

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.