IP Contacts

Data as of 2026-10-18
BGP inherited
This organisation
Netblocks4 · 16,384 IPv4 addresses
Record ID251328807
RegistryRIPE
Customerssee who runs inside 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 · report an issue

IP Ranges (4)

⬇ export CSV
CIDR Org name Registry Status Confidence
189.12.224.0/20 IP Contacts RIPE SUB-ALLOCATED PA ● high
189.12.240.0/20 IP Contacts RIPE SUB-ALLOCATED PA ● high
191.219.128.0/20 IP Contacts RIPE SUB-ALLOCATED PA ● high
191.219.144.0/20 IP Contacts RIPE SUB-ALLOCATED PA ● high

Network trust

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

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

189.12.224.0/20 /20 authorized for AS931 — Hyonix
189.12.240.0/20 /20 authorized for AS931 — Hyonix
191.219.128.0/20 /20 authorized for AS931 — Hyonix
191.219.144.0/20 /20 authorized for AS931 — Hyonix

NIC Handles

DUMY-RIPE DUMY-RIPE ORG-IC147-RIPE ipcontacts-mnt