THREE-E-CONSULTING
BGP inherited
Cluster stats
| Netblocks | 1 |
| All fragments | 2 blocks across 2 clusters |
| Cluster ID | 211557179 |
| Registry | RIPE |
| Customers | find 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 | |
IP Ranges (1)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2a00:2381:3956::/56 | THREE-E-CONSULTING | RIPE | ASSIGNED | ● medium |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “THREE E” — 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.
- three_E_NET_IPV4 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.
- wuxi-zhongtie-three-bureau via No.31,Jin-rong Street sub-allocation
- THREES1 sub-allocation
- THREE-D-SYSTEMS sub-allocation
- THREECOMTESTDK via TDC Holding A/S sub-allocation
- THREECOM-NORDIC-NET via TDC Holding A/S sub-allocation
- THREEI sub-allocation
- THREEANGLE sub-allocation
- THREEC-TECH sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(1 of 1)
No discrepancies found among checked blocks.
NIC Handles
BTNET-MNT
DUMY-RIPE
DUMY-RIPE