Fur IT Systems
FurITSystems
Registry
Cluster stats
Netblocks7
All fragments 10 blocks across 4 clusters
Cluster ID191628842
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

2 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-06

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
185.1.59.179/32 FurITSystems PEERINGDB ASSIGNED ● high
185.1.155.111/32 FurITSystems PEERINGDB ASSIGNED ● high
2001:7f8:ca:1:0:21:5168:1/128 FurITSystems PEERINGDB ASSIGNED ● high
2001:7f8:cc:333:0:21:5168:1/128 FurITSystems PEERINGDB ASSIGNED ● high
2a0c:b641:701:0:a5:21:5168:1/128 FurITSystems PEERINGDB ASSIGNED ● high
2a0e:97c0:7c0::/48 FURITSYSTEMS RIPE ASSIGNED ● low
2a0e:97c0:7ca::/48 FurITSystems RIPE ASSIGNED ● low

Network trust

what's this?
RPKI hygiene: B how networks compare →
85.7% of checked blocks have valid RPKI ROA coverage (6 of 7)
Possible discrepancies (2)

These blocks are registered to FurITSystems but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

2a0e:97c0:7c0::/48 /48 authorized for AS215168 — Akos Miklos
2a0e:97c0:7ca::/48 /48 authorized for AS215168 — Akos Miklos

NIC Handles

ACRO56071-RIPE AS215168 DUMY-RIPE DUMY-RIPE FURITSYSTEMS-MNT