IMEC

BGP inherited
Cluster stats
Netblocks8 · 658 IPv4 addresses
All fragments 15 blocks across 4 clusters
Cluster ID209097399
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 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
193.190.64.248/29 IMEC RIPE ASSIGNED PA ● high
193.190.127.128/25 IMEC RIPE ASSIGNED PA ● high
193.190.255.176/29 IMEC RIPE ASSIGNED PA ● high
193.190.255.184/29 IMEC RIPE ASSIGNED PA ● high
193.191.148.0/24 IMEC RIPE ASSIGNED PA ● high
193.191.169.0/24 IMEC RIPE ASSIGNED PA ● high
2001:6a8:1d80::/48 IMEC RIPE ASSIGNED ● high
2001:6a8:1df0::/48 IMEC RIPE ASSIGNED ● high

Domains hosted in this network

what's this?

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (8 of 8)
Possible discrepancies (4)

These blocks are registered to IMEC but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

2001:6a8:1d80::/48 /48 authorized for AS2611 — BELNET
2001:6a8:1df0::/48 /48 authorized for AS2611 — BELNET
193.191.148.0/24 /24 authorized for AS2611 — BELNET
193.191.169.0/24 /24 authorized for AS2611 — BELNET

NIC Handles

BELNET-MNT DUMY-RIPE DUMY-RIPE IAC112-RIPE