Procopa IT ApS
Procopa-Hosting
BGP inherited
Cluster stats
| Netblocks | 1 |
| All fragments | 29 blocks across 13 clusters |
| Cluster ID | 210879002 |
| Registry | RIPE |
| Customers | find 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 | |
IP Ranges (1)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 185.237.124.0/24 | Procopa-Hosting | RIPE | ASSIGNED PA | ● medium |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “Procopa” — often
per-country or per-system registrations of the same brand, occasionally a different
organisation sharing the name. Not counted in this organisation's own footprint.
- Procopa-BGP-link 8 blocks
- Procopa IT ApS 7 blocks
- procopa_cph-ftdv-cust01 2 blocks
- Procopa-IT-BGP-Link 2 blocks
- Procopa-IT-DNS 2 blocks
- Procopa-IT-Speedtest 1 blocks
- Procopa-IT-Hove-ISP 1 blocks
- Procopa-Link_and_Transit 1 blocks
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own
naming convention, not a direct registration.
- Speedtest via Procopa IT ApS sub-allocation
- Dns via Procopa IT ApS sub-allocation
- Backup via Procopa IT ApS sub-allocation
- Loopback via Procopa IT ApS sub-allocation
- Hove Isp via Procopa IT ApS sub-allocation
- Link And Transit via Procopa IT ApS sub-allocation
- Internal Services via Procopa IT ApS sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(1 of 1)
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
dk-baesdata-1-mnt