ECOM-SERVICE

BGP inherited
Cluster stats
Netblocks6
All fragments 40 blocks across 2 clusters
Cluster ID209049812
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

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
85.130.111.128/28 ECOM-SERVICE RIPE ASSIGNED PA ● low
89.215.168.176/28 ECOM-SERVICE RIPE ASSIGNED PA ● low
217.9.234.128/26 ECOM-SERVICE RIPE ASSIGNED PA ● low
217.18.243.0/26 ECOM-SERVICE RIPE ASSIGNED PA ● low
217.18.252.96/29 ECOM-SERVICE RIPE ASSIGNED PA ● low
217.18.252.112/29 ECOM-SERVICE RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “ECOM SERVICE” — 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

AS13124-MNT DUMY-RIPE DUMY-RIPE