UFPS
Cluster stats
Netblocks9
All fragments 375 blocks across 18 clusters
Cluster ID191950845
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 8 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

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

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
78.37.70.0/25 UFPS RIPE ASSIGNED PA ● low
78.37.70.128/28 UFPS RIPE ASSIGNED PA ● low
78.37.70.144/29 UFPS RIPE ASSIGNED PA ● low
78.37.70.160/28 UFPS RIPE ASSIGNED PA ● low
83.172.37.240/29 UFPS-NET RIPE ASSIGNED PA ● low
94.25.18.56/29 UFPS RIPE ASSIGNED PA ● low
195.58.13.120/30 UFPS-NET RIPE ASSIGNED PA ● low
212.57.159.0/24 UFPS RIPE ASSIGNED PA ● low
217.18.142.96/27 UFPS-NET RIPE ASSIGNED PA ● low

Network trust

what's this?
RPKI hygiene: C how networks compare →
77.8% of checked blocks have valid RPKI ROA coverage (7 of 9)
Possible discrepancies (1)

These blocks are registered to UFPS 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.

212.57.159.0/24 /24 authorized for AS12389 — PJSC Rostelecom

NIC Handles

AS3253-MNT AS8997-MNT DIN-RIPE-MNT DUMY-RIPE DUMY-RIPE MNT-SELS ROSTELECOM-MNT TOMLINE-MNT