i3D.net B.V

i3Dnet-infra
BGP inherited
Cluster stats
Netblocks9 · 311 IPv4 addresses
All fragments 67 blocks across 28 clusters
Cluster ID210099619
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

5 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-07-19

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
5.200.18.224/27 i3Dnet-infra RIPE ASSIGNED PA ● low
5.200.22.48/28 i3Dnet-infra RIPE ASSIGNED PA ● low
5.200.23.192/27 i3Dnet-infra RIPE ASSIGNED PA ● low
188.122.68.240/28 i3Dnet-infra RIPE ASSIGNED PA ● low
188.122.69.0/26 i3Dnet-infra RIPE ASSIGNED PA ● low
188.122.69.128/27 i3Dnet-infra RIPE ASSIGNED PA ● low
188.122.69.224/27 i3Dnet-infra RIPE ASSIGNED PA ● low
213.163.64.160/27 i3Dnet-infra RIPE ASSIGNED PA ● low
213.163.84.192/26 i3Dnet-infra RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “i3Dnet infra” — 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.
Combined view of all 28 name-family clusters →
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 (9 of 9)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE MNT-i3D