ORG-UOF106-RIPE

BGP inherited
Cluster stats
Netblocks7 · 824 IPv4 addresses
Cluster ID210317324
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
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-19

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
5.190.13.0/25 ORG-UOF106-RIPE RIPE ASSIGNED PA ● low
5.190.98.0 – 5.190.98.62 ORG-UOF106-RIPE RIPE ASSIGNED PA ● low
5.190.210.128/27 ORG-UOF106-RIPE RIPE ASSIGNED PA ● low
5.190.210.160/27 ORG-UOF106-RIPE RIPE ASSIGNED PA ● low
5.190.210.192/26 ORG-UOF106-RIPE RIPE ASSIGNED PA ● low
5.190.211.0/24 ORG-UOF106-RIPE RIPE ASSIGNED PA ● low
5.190.214.0/24 ORG-UOF106-RIPE 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 (7 of 7)
Possible discrepancies (2)

These blocks are registered to ORG-UOF106-RIPE 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.

5.190.214.0/24 /24 authorized for AS58224 — Iran Telecommunication Company PJS
5.190.211.0/24 /24 authorized for AS58224 — Iran Telecommunication Company PJS

NIC Handles

DUMY-RIPE DUMY-RIPE MNT-TCF TCI-RIPE-MNT