UFPS1-NET

BGP inherited
Cluster stats
Netblocks10 · 654 IPv4 addresses
Cluster ID209193579
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 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
10 0 netblocks since 2026-07-05
2026-07-05 peak 10 2026-07-19

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
80.82.34.16/29 UFPS1-NET RIPE ASSIGNED PA ● low
80.82.42.132/30 UFPS1-NET RIPE ASSIGNED PA ● low
80.82.44.232/29 UFPS1-NET RIPE ASSIGNED PA ● low
88.83.194.52/30 UFPS1-NET RIPE ASSIGNED PA ● low
88.83.194.56/29 UFPS1-NET RIPE ASSIGNED PA ● low
88.83.194.64/26 UFPS1-NET RIPE ASSIGNED PA ● low
88.83.195.32/27 UFPS1-NET RIPE ASSIGNED PA ● low
88.83.195.64/28 UFPS1-NET RIPE ASSIGNED PA ● low
88.83.195.184/29 UFPS1-NET RIPE ASSIGNED PA ● low
213.24.194.0/23 UFPS1-NET RIPE ASSIGNED PA ● low

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (10 of 10)
Possible discrepancies (1)

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

213.24.194.0/23 /23 authorized for AS12389 — PJSC Rostelecom

NIC Handles

AS8342-MNT DUMY-RIPE DUMY-RIPE ROSTELECOM-MNT