Ufanet

Data as of 2026-09-20
Registry
This organisation
Netblocks11
IPv6 2 prefixes (largest 2001:7f8:20:101::209:35/128)
Also registered under this name 13 netblocks across 3 separate records
Record ID241494411
RegistryPEERINGDB
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (11)

⬇ export CSV
CIDR Org name Registry Status Confidence
31.28.19.176/32 Ufanet PEERINGDB ASSIGNED ● high
185.0.12.6/32 Ufanet PEERINGDB ASSIGNED ● high
185.1.153.186/32 Ufanet PEERINGDB ASSIGNED ● high
185.232.60.35/32 Ufanet PEERINGDB ASSIGNED ● high
195.208.209.35/32 Ufanet PEERINGDB ASSIGNED ● high
195.208.210.152/32 Ufanet PEERINGDB ASSIGNED ● high
2001:7f8:20:101::209:35/128 Ufanet PEERINGDB ASSIGNED ● high
2001:7f8:20:101::210:152/128 Ufanet PEERINGDB ASSIGNED ● high
87.226.163.196/30 Ufanet RIPE ASSIGNED PA ● low
188.128.90.24/30 Ufanet RIPE ASSIGNED PA ● low
188.128.90.28/30 Ufanet RIPE ASSIGNED PA ● low

IPv6 ranges (2)

CIDR
2001:7f8:20:101::209:35/128
2001:7f8:20:101::210:152/128

Footprint over time

13 weekly snapshots · JSON
11 0 netblocks since 2026-07-05
2026-07-05 peak 11 2026-09-20

Network trust

what's this?
RPKI hygiene: C how networks compare →
63.6% of checked blocks have valid RPKI ROA coverage (7 of 11)
No discrepancies found among checked blocks.

NIC Handles

AS47775 DUMY-RIPE DUMY-RIPE ROSTELECOM-MNT