Evacom B.V.

Evacom
GLEIF verified
LEI
724500RQHAGN092XMV24
Registered name
Evacom B.V.
Jurisdiction
Ultimate parent
No parent on file in GLEIF
Cluster stats
Netblocks6
All fragments 14 blocks across 2 clusters
Cluster ID213186143
RegistryPEERINGDB
Owner jurisdictionNL
Customersfind customers using this network →
Evidence & provenance ?
Attribution GLEIF legal-entity match
Legal identityLEI 724500RQHAGN092XMV24
Shared handles clustered on 1 shared RIR contact/maintainer handle
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
185.0.9.7/32 Evacom PEERINGDB ASSIGNED ● high
193.201.28.159/32 Evacom PEERINGDB ASSIGNED ● high
217.29.67.207/32 Evacom PEERINGDB ASSIGNED ● high
2001:7f8:b:100:1d1:a521:3338:207/128 Evacom PEERINGDB ASSIGNED ● high
2001:7f8:10::21:3338/128 Evacom PEERINGDB ASSIGNED ● high
2001:7f8:13f::21:3338/128 Evacom PEERINGDB ASSIGNED ● high

Possibly related to this organisation

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

NIC Handles

AS213338