GTO-OMAN-POPS
Unresolved
Cluster stats
| Netblocks | 4 |
| All fragments | 5 blocks across 2 clusters |
| Cluster ID | 192000326 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| 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 | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 212.72.8.0 – 212.72.10.255 | GTO-OMAN-POPS | RIPE | ASSIGNED PA | ● low |
| 212.72.14.0/23 | GTO-OMAN-POPS | RIPE | ASSIGNED PA | ● low |
| 212.72.17.0 – 212.72.20.255 | GTO-OMAN-POPS | RIPE | ASSIGNED PA | ● low |
| 212.72.30.0/24 | GTO-OMAN-POPS | 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
(4 of 4)
Possible discrepancies (2)
These blocks are registered to GTO-OMAN-POPS 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.
| 212.72.17.0 – 212.72.20.255 /22 | authorized for AS19905 — Vercara, LLC |
| 212.72.8.0 – 212.72.10.255 /22 | authorized for AS19905 — Vercara, LLC |
NIC Handles
AS8529-MNT
DUMY-RIPE
DUMY-RIPE