ECKER

BGP inherited
Cluster stats
Netblocks6
Registered in Switzerland (1) · Germany (1) · Israel (1) · Netherlands (1)
All fragments 11 blocks across 4 clusters
Cluster ID209939371
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

3 weekly snapshots · JSON
6 0 netblocks since 2026-07-12
2026-07-12 peak 6 2026-07-19

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
185.1.147.174/32 ECKER PEERINGDB ASSIGNED ● high
193.239.119.226/32 ECKER PEERINGDB ASSIGNED ● high
2001:7f8:13::a521:4076:1/128 ECKER PEERINGDB ASSIGNED ● high
2001:7f8:ca:1:0:21:4076:1/128 ECKER PEERINGDB ASSIGNED ● high
84.94.139.104/29 ECKER RIPE ASSIGNED PA ● low
217.24.234.80/29 ECKER-NET RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “ECKER” — 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 (6 of 6)
No discrepancies found among checked blocks.

NIC Handles

AS214076 AS9116-MNT DUMY-RIPE DUMY-RIPE SAARGATE-DE-MNT