FKS

BGP inherited
Cluster stats
Netblocks8
All fragments 13 blocks across 4 clusters
Cluster ID210329013
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 15 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
116.228.141.64/30 FKS APNIC ASSIGNED NON-PORTABLE ● high
180.166.96.40/29 FKS APNIC ASSIGNED NON-PORTABLE ● high
180.166.96.48/29 FKS APNIC ASSIGNED NON-PORTABLE ● high
180.168.196.64/29 FKS APNIC ASSIGNED NON-PORTABLE ● high
180.169.15.8/29 FKS APNIC ASSIGNED NON-PORTABLE ● high
2a01:4f8:121:4095::/64 FKS RIPE ASSIGNED ● low
2a01:4f8:141:132c::/64 FKS RIPE ASSIGNED ● low
2a01:4f9:4b:4aea::/64 FKS RIPE ASSIGNED ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “FKS” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (8 of 8)
No discrepancies found among checked blocks.

NIC Handles

AC1591-AP DUMY-RIPE DUMY-RIPE HOS-GUN LMY31-AP LMY31-AP MAINT-CHINANET-SH WWW26-AP WWW26-AP WWW27-AP WWW27-AP WWW29-AP +3 more