i3D-K119752
BGP inherited
Cluster stats
| Netblocks | 3 |
| All fragments | 4 blocks across 2 clusters |
| Cluster ID | 210570607 |
| 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 | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 5.200.19.0/25 | i3D-K119752 | RIPE | ASSIGNED PA | ● low |
| 109.200.204.128/25 | i3D-K119752 | RIPE | ASSIGNED PA | ● low |
| 2a00:1630:56::/48 | i3D-K119752 | RIPE | ASSIGNED | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “i3D K119752” — 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-K119752-4 1 blocks
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.
- i3D-K119752-4 via i3D.net B.V sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(3 of 3)
Possible discrepancies (1)
These blocks are registered to i3D-K119752 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:56::/48 /48 | authorized for AS49544 — i3D.net B.V |
NIC Handles
DUMY-RIPE
DUMY-RIPE
MNT-I3D
MNT-i3D