IBM-REGUS

Data as of 2026-08-30
BGP inherited
This organisation
Netblocks9 · 1,840 IPv4 addresses
Record ID234091746
RegistryRIPE
Customerssee who runs inside 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

Footprint over time

10 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-08-30

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.173.199.0/24 IBM-REGUS RIPE ASSIGNED PA ● low
62.173.224.0/28 IBM-REGUS RIPE ASSIGNED PA ● low
62.173.224.16/28 IBM-REGUS RIPE ASSIGNED PA ● low
212.41.142.16/28 IBM-REGUS RIPE ASSIGNED PA ● low
212.108.18.0/25 IBM-REGUS RIPE ASSIGNED PA ● low
212.108.22.128/25 IBM-REGUS RIPE ASSIGNED PA ● low
212.162.197.128/25 IBM-REGUS RIPE ASSIGNED PA ● low
212.162.247.128/25 IBM-REGUS RIPE ASSIGNED PA ● low
213.15.252.0/22 IBM-REGUS 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 (9 of 9)
No discrepancies found among checked blocks.

NIC Handles

CIP-MNT DUMY-RIPE DUMY-RIPE