EDELMAN

BGP inherited
Cluster stats
Netblocks8
Registered in Netherlands (3) · Spain (2) · China (1) · Germany (1) · France (1)
All fragments 15 blocks across 6 clusters
Cluster ID208838945
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 11 shared RIR contact/maintainer handles
Registry names 5 distinct registrant names 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
202.106.66.128/29 EDELMAN-INTERNATIONAL-CO APNIC ASSIGNED NON-PORTABLE ● high
62.37.141.16/29 EDELMAN RIPE ASSIGNED PA ● low
77.156.204.48/29 EDELMAN-SA RIPE ASSIGNED PA ● low
85.62.33.128/29 EDELMAN RIPE ASSIGNED PA ● low
144.178.91.48/28 Edelman_NET RIPE LEGACY ● low
144.178.219.192/28 Edelman_NET RIPE LEGACY ● low
212.18.1.16/29 EDELMAN-NET RIPE ASSIGNED PA ● low
212.153.199.40/29 EDELMAN RIPE ASSIGNED PA ● low

Possibly related to this organisation

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

NIC Handles

DUMY-RIPE DUMY-RIPE Eurofiber-MNT FTE-GGRR-MNT FY9-AP FY9-AP LDCOM-MNT LDCOM-PRO-MNT MAINT-CNCGROUP-BJ MNET-MNT NLNET-MNT