ACFW

BGP inherited
Cluster stats
Netblocks6
All fragments 7 blocks across 2 clusters
Cluster ID209368866
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

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

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
78.4.214.16/30 ACFW RIPE ASSIGNED PA ● low
78.5.205.96/29 ACFW RIPE ASSIGNED PA ● low
78.6.101.128/29 ACFW RIPE ASSIGNED PA ● low
89.119.195.228/30 ACFW RIPE ASSIGNED PA ● low
212.17.206.128/27 ACFW RIPE ASSIGNED PA ● low
217.220.220.80/29 ACFW RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “ACFW” — 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.
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.
  • Chennai via Bharti Airtel Limited sub-allocation
  • ACFW1 via BT Italia S.p.A. sub-allocation
  • ACFW9 via BT Italia S.p.A. sub-allocation
  • ACFW10 via BT Italia S.p.A. sub-allocation
  • ACFW11 via BT Italia S.p.A. sub-allocation
  • ACFW12 via BT Italia S.p.A. sub-allocation

Network trust

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

NIC Handles

ALBACOM-MNT DUMY-RIPE DUMY-RIPE