Summary

  • Telehouse presents West as an existing Docklands data-centre facility and says it hosts the London Internet Exchange peering platform, while its separate West Two announcement describes a £275 million project set for completion in 2028.
  • RIPE NCC, PeeringDB and LINX records help identify the company, facility and exchange-location context, but none of them proves ownership, end-to-end route control, service performance or the future operating outcome of West Two.

The expansion claim must remain in the future tense

Telehouse International Corporation of Europe has announced that it broke ground on Telehouse West Two at its existing London Docklands campus. In that announcement, the company describes a £275 million investment and says the project is set for completion in 2028. Those are useful project facts, but they are also bounded facts: the amount and schedule come from Telehouse’s own project statement, and the announcement does not make West Two an operating facility today.

That distinction matters because infrastructure language can easily compress several stages into one story. A groundbreaking is evidence that a project has entered a construction phase. A planned completion date is a target. Neither demonstrates that equipment has been commissioned, customers have been connected, traffic is flowing, controls have been tested or a service outcome has been achieved. The current evidence supports the existence of the announced project, not a claim about its eventual live performance.

The same discipline applies to the relationship between West and West Two. Telehouse’s current facility page presents Telehouse West as an existing London data-centre facility. West Two is a separately named expansion project in the company’s announcement. They should not be treated as the same operating asset, and the present characteristics attributed to West should not be copied forward as proven characteristics of West Two.

For readers assessing dependency or continuity, this is the first operational-control test: keep current state, planned state and verified running state separate. The gap between them is not a reason to dismiss the project. It is the space in which due diligence belongs.

Legal identity is one layer, not the whole control map

The RIPE NCC member page lists the exact name Telehouse International Corporation of Europe Ltd and a London E14 address in the United Kingdom. That record is useful because it anchors a current legal and membership identity. It does not, by itself, establish which facility the named company owns, which services it provides, which number resources it controls or which routes it operates.

This is an important limit on registry evidence. A registry or membership directory functions as a ledger: it can record a name and an association within its own scope. It is not a sovereign declaration about every asset or operational relationship that may use the same brand. Treating it that way would turn a narrow identity record into an unsupported ownership and performance claim.

The practical use of the RIPE record is therefore precise. It helps confirm that the named company appears in a current network-community membership directory. It gives investigators a stable identity to compare with contracts and other records. It does not eliminate the need to determine which legal counterparty is responsible for a particular facility, service or incident.

The existing West record shows controls to verify

Telehouse’s own page presents Telehouse West as an existing facility in London and says that the site hosts the London Internet Exchange peering platform. The page also describes power, environmental, fire and security controls. These statements identify categories of operational control that matter at a data-centre site, but they remain operator-published descriptions rather than independent measurements of capacity, availability or resilience.

This difference between a described control and a proven outcome is central to infrastructure analysis. A control statement tells a prospective customer what to investigate. It does not show how the control behaved during a particular event, whether two apparent safeguards share a failure domain, or what service level a specific contract provides. Those questions require evidence from the actual service design and its operation.

The reference to the London Internet Exchange also needs a firm boundary. Hosting an exchange platform is not the same as governing that exchange or controlling the routes of its participants. The facility provides a place in which interconnection can occur; participant networks and the exchange operate their own policy and technical controls. A building relationship must not be inflated into authority over every routing decision made through it.

That makes Telehouse West relevant without making the public claim larger than the sources allow. It is an existing named facility with an operator-described control environment and an interconnection role. It is a useful comparison point for the planned West Two project. It is not proof that West Two has inherited a live control environment or that either site guarantees a particular routing or service result.

PeeringDB records an association, not an ownership judgment

PeeringDB’s current record identifies facility 835 as Telehouse - London (Docklands West), associates it with Telehouse - Global Data Centers and lists exchange and network presence that includes LINX LON1. This is valuable public evidence about how the facility is represented in a participant-maintained interconnection directory.

The record should be read according to that function. PeeringDB can help operators discover facility and interconnection associations. It does not independently verify legal ownership, physical path diversity, traffic levels, capacity, performance or a contractual service level. Its entries can also change as participants maintain the directory.

The safe inference is modest but useful: Telehouse West has a current public directory identity within the interconnection ecosystem, and LINX LON1 appears among its listed exchange associations. The unsafe inference would be that this proves who owns every component, how traffic is routed, whether paths are independent or how the service will perform under failure.

That boundary becomes more important when considering West Two. A nearby planned project does not automatically inherit the directory relationships of the existing West facility. If West Two later appears in facility and exchange records, those entries will need to be examined on their own terms and compared with live technical and contractual evidence.

LINX supplies the wider location context

LINX’s current LON1 page describes the exchange as accessible from 17 data-centre locations across London and includes Telehouse among the listed location providers. This gives a broader view of the exchange-location environment. It does not, within the evidence used here, map that Telehouse reference specifically to West or West Two, and it does not assign Telehouse control over LINX policy or member routes.

The number of locations is therefore a statement about access points described by LINX, not a guarantee of diversity for any one participant. A network may have access to several possible locations while still depending on shared carriers, common physical paths, common equipment, common management or a single commercial arrangement. The public location list cannot answer those design questions for a particular deployment.

For West Two, the LINX record is best treated as context for future verification. It shows that Telehouse is named within the current LON1 location-provider set. It does not show that the planned building is already an exchange location or that any route, port or service is live there.

Five records, five distinct questions

Taken together, the five sources answer different questions:

  1. The RIPE NCC page records the named company within its membership ledger.
  2. Telehouse’s West page presents an existing facility and categories of site control.
  3. Telehouse’s West Two announcement records a project, a stated investment and a planned completion year.
  4. PeeringDB records a current facility and interconnection-directory association for Docklands West.
  5. LINX records a wider LON1 location context that includes Telehouse.

No single record answers all five questions, and combining them does not erase their limits. The evidence does not establish that the legal membership identity owns every branded asset. It does not establish that a listed exchange association confers route control. It does not establish that an announced project is operational. It does not establish performance, uptime, physical diversity or an SLA.

This layered reading is stronger than either promotional acceptance or blanket scepticism. It identifies what is currently observable and turns the gaps into specific verification tasks. The identity layer can be checked against the contracting party. The facility layer can be checked against the delivered design. The exchange-location layer can be checked against actual ports and paths. The running-network layer can be checked only when there is operating evidence to observe.

West Two as an operational-control test

West Two will become more informative as its state changes. A later completion statement would answer a project-status question, but not by itself prove service readiness. A directory entry would answer an identity or association question, but not prove physical or routing behaviour. A customer-facing service claim would describe an offering, but not independently demonstrate resilience. Each step needs evidence appropriate to the claim being made.

The most useful control question is therefore not “Is the campus connected?” It is “Who controls each dependency, what evidence demonstrates that control, and what remains unobserved?” That question keeps the building, exchange, participant network and legal counterparty in their proper places.

For infrastructure buyers, the distinction changes the due-diligence sequence. First identify the exact legal entity and service scope. Then map the facility and interconnection dependencies. Next test whether apparent alternatives are operationally independent. Finally compare observed behaviour and contractual commitments with the public descriptions. The current records provide starting points for that work, not a substitute for it.

West Two is consequently best understood as a future control boundary under construction. Telehouse has announced the project and its intended timetable. The existing West facility and current interconnection records provide relevant context. The operating result, however, remains to be observed rather than assumed.