I3D-COLO
BGP inherited
Cluster stats
| Netblocks | 4 · 860 IPv4 addresses |
| Cluster ID | 209499631 |
| 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 (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 5.200.2.0/24 | I3D-COLO | RIPE | ASSIGNED PA | ● low |
| 5.200.20.192/27 | I3D-COLO | RIPE | ASSIGNED PA | ● low |
| 213.163.79.128/26 | I3D-COLO | RIPE | ASSIGNED PA | ● low |
| 213.163.82.0/23 | I3D-COLO | RIPE | ASSIGNED PA | ● low |
Possibly related to this organisation
what's this?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-Colocation-Shared 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
(4 of 4)
Possible discrepancies (2)
These blocks are registered to I3D-COLO 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.
| 213.163.82.0/23 /23 | authorized for AS49544 — i3D.net B.V |
| 5.200.2.0/24 /24 | authorized for AS49544 — i3D.net B.V |
NIC Handles
DUMY-RIPE
DUMY-RIPE
MNT-I3D
MNT-i3D