EXCHANGE DATA INTERNATIONAL LIMITED
EXCHANGE-DATA-INTERNATIONAL-LTD
GLEIF verified
LEI
549300J7L63QOZK2JZ26
Registered name
EXCHANGE DATA INTERNATIONAL LIMITED
Jurisdiction
Ultimate parent
No parent on file in GLEIF
Cluster stats
| Netblocks | 1 |
| All fragments | 2 blocks across 2 clusters |
| Cluster ID | 206031898 |
| Registry | RIPE |
| Owner jurisdiction | GB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | GLEIF legal-entity match |
| Legal identity | LEI 549300J7L63QOZK2JZ26 |
| 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:e55::/48 | EXCHANGE-DATA-INTERNATIONAL-LTD | RIPE | AGGREGATED-BY-LIR | ● high |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “EXCHANGE DATA” — 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.
- EXCHANGE-DATA-VPN 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.
- FSDATA-SE-EXCHANGE via Hostek AB sub-allocation
- London-Data-Exchange sub-allocation
- EXCHANGE-DATA-VPN via Spitfire Network Services Limited sub-allocation
- I Real Data Exchange sub-allocation
- DATAEXCHANGEEUROPE via Eircom Limited sub-allocation
- Worlddataexchange via Garnier Projects BV 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)
RPKI-inferred operator
British Telecommunications Limited
Nearly all of this network's RPKI-covered space is cryptographically authorized for this
single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.
NIC Handles
BTNET-MNT
DUMY-RIPE
DUMY-RIPE