ORG-PNJF1-RIPE

Data as of 2026-08-23
BGP inherited
Cluster stats
Netblocks5 · 1,312 IPv4 addresses
Cluster ID229881831
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (5)

⬇ export CSV
CIDR Org name Registry Status Confidence
5.190.8.224/27 ORG-PNJF1-RIPE RIPE ASSIGNED PA ● low
5.190.37.176 – 5.190.37.255 ORG-PNJF1-RIPE RIPE ASSIGNED PA ● low
5.190.73.128/25 ORG-PNJF1-RIPE RIPE ASSIGNED PA ● low
151.232.29.208 – 151.232.31.255 ORG-PNJF1-RIPE RIPE ASSIGNED PA ● low
151.234.220.0/23 ORG-PNJF1-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 (5 of 5)
Possible discrepancies (2)

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

151.232.29.208 – 151.232.31.255 /23 authorized for AS58224 — Iran Telecommunication Company PJS
151.234.220.0/23 /23 authorized for AS58224 — Iran Telecommunication Company PJS

NIC Handles

DUMY-RIPE DUMY-RIPE MNT-TCF