NETCOM-CONNECTED-SERVICES-HAMBURG-NET

BGP inherited
Cluster stats
Netblocks8
All fragments 15 blocks across 3 clusters
Cluster ID209600334
RegistryRIPE
Customersfind 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

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
62.157.131.16/29 NETCOM-CONNECTED-SERVICES-HAMBURG-NET RIPE ASSIGNED PA ● low
62.157.131.48/29 NETCOM-CONNECTED-SERVICES-HAMBURG-NET RIPE ASSIGNED PA ● low
91.24.67.152/29 NETCOM-CONNECTED-SERVICES-HAMBURG-NET RIPE ASSIGNED PA ● low
91.26.54.224/29 NETCOM-CONNECTED-SERVICES-HAMBURG-NET RIPE ASSIGNED PA ● low
2003:cb:f81e::/48 NETCOM-CONNECTED-SERVICES-HAMBURG-NET RIPE ASSIGNED ● low
2003:ce:e824::/48 NETCOM-CONNECTED-SERVICES-HAMBURG-NET RIPE ASSIGNED ● low
2003:e4:1829::/48 NETCOM-CONNECTED-SERVICES-HAMBURG-NET RIPE ASSIGNED ● low
2003:fb:305d::/48 NETCOM-CONNECTED-SERVICES-HAMBURG-NET RIPE ASSIGNED ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “NETCOM CONNECTED SERVICES” — 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.
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: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (8 of 8)
No discrepancies found among checked blocks.

NIC Handles

DTAG-NIC DUMY-RIPE DUMY-RIPE