i3D

BGP inherited

Cluster stats

Netblocks	6
All fragments	1,795 blocks across 59 clusters
Cluster ID	210214718
Registry	RIPE
Customers	find 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

6 0 netblocks since 2026-07-05

2026-07-05 peak 6 2026-07-19

IP Ranges (6)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
5.200.4.80/28	i3D	RIPE	ASSIGNED PA	● low
5.200.17.0/26	i3D	RIPE	ASSIGNED PA	● low
5.200.27.96/28	i3D	RIPE	ASSIGNED PA	● low
2a00:1630:1::/56	i3D	RIPE	ASSIGNED	● low
2a00:1630:1:100::/56	i3D	RIPE	ASSIGNED	● low
2a00:1630:2:d00::/56	i3D	RIPE	ASSIGNED	● low

Possibly related to this organisation

what's this?

Same name family

Separately-registered clusters whose names share “i3D” — 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.

i3D.net B.V 1,706 blocks
I3D-COLO 4 blocks
i3D-K123445 3 blocks
i3D-K111445 3 blocks
i3D-K85550 3 blocks
i3D-K123115 3 blocks
i3D-K119752 3 blocks
i3D-K105829 2 blocks

Combined view of all 59 name-family clusters →

Network trust

what's this?

RPKI hygiene: A how networks compare →

100.0% of checked blocks have valid RPKI ROA coverage (6 of 6)

Possible discrepancies (3)

These blocks are registered to i3D 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.

2a00:1630:1::/56 /56	authorized for AS49544 — i3D.net B.V
2a00:1630:2:d00::/56 /56	authorized for AS49544 — i3D.net B.V
2a00:1630:1:100::/56 /56	authorized for AS49544 — i3D.net B.V

NIC Handles

DUMY-RIPE DUMY-RIPE MNT-I3D MNT-i3D