WFTZ

BGP inherited
Cluster stats
Netblocks6 · 362 IPv4 addresses
Cluster ID209959118
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
85.17.199.0/25 WFTZ RIPE ASSIGNED PA ● low
85.17.220.64/26 WFTZ RIPE ASSIGNED PA ● low
85.17.242.64/27 WFTZ RIPE ASSIGNED PA ● low
95.211.67.160/28 WFTZ RIPE ASSIGNED PA ● low
95.211.71.0/26 WFTZ RIPE ASSIGNED PA ● low
95.211.122.192/26 WFTZ RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
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.
  • WFTZIB via CNCGROUP IP network of ShangHai IDC 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

DUMY-RIPE DUMY-RIPE LEASEWEB-NL-MNT