Capexconnect ApS

BGP inherited
Cluster stats
Netblocks8 · 6,650 IPv4 addresses
Cluster ID211352931
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
85.204.120.0/23 Capexconnect ApS RIPE ALLOCATED PA ● low
85.204.132.0/23 Capexconnect ApS RIPE ALLOCATED PA ● low
85.204.136.0/23 Capexconnect ApS RIPE ALLOCATED PA ● low
85.204.194.0/23 Capexconnect ApS RIPE ALLOCATED PA ● low
195.192.248.0/23 Capexconnect ApS RIPE ALLOCATED PA ● low
212.237.96.0/20 Capexconnect ApS RIPE ALLOCATED PA ● low
2a00:7660::/29 Capexconnect ApS RIPE ALLOCATED-BY-RIR ● low
2a0b:f700::/29 Capexconnect ApS RIPE ALLOCATED-BY-RIR ● low

Possibly related to this organisation

what's this?
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.

Network trust

what's this?
RPKI hygiene: F how networks compare →
12.5% of checked blocks have valid RPKI ROA coverage (1 of 8)
Possible discrepancies (1)

These blocks are registered to Capexconnect ApS 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.

85.204.120.0/23 /23 authorized for AS8075 — Microsoft Corporation

NIC Handles

DUMY-RIPE DUMY-RIPE ORG-CA2505-RIPE RIPE-NCC-HM-MNT lir-dk-capexconnect-1-MNT