Canadian data centres, cloud regions and internet exchanges in one place.

Metro reference

Vancouver data-centre market reference

Downtown interconnection, regional facility choices, BC Hydro service and the current electricity-allocation gate.

Directory records
14
Operators
6
Localities
3

A dense downtown network with regional extensions

Vancouver's public facility pattern is centred on downtown carrier buildings, with additional records in Burnaby and Coquitlam. Cologix publishes five Vancouver facilities. eStruxture publishes three. Equinix lists VA1 in Burnaby. Hut 8 Canada and Canadian Web Hosting add other Vancouver-area records. The metro serves western Canadian users and Pacific-facing network routes, but each operator source describes a different facility or service relationship.

Sources: Cologix, eStruxture, Equinix, Hut 8 Canada

Some records share an address or building. A facility count is therefore not a count of purpose-built campuses. The directory keeps provider identities visible and requires differentiated specifications before a page enters the sitemap. A network planner may care that several providers meet in one building. A capacity planner must verify the physical building, operator responsibility and utility service behind each record.

Sources: Canadian Web Hosting, ServerMania, Cologix

The provincial electricity advantage now has an allocation process

British Columbia's electricity system is predominantly clean and renewable, and the province is expanding supply and transmission to meet rising demand. That supports an emissions case for grid-connected compute. It does not create an unlimited pool of capacity in the Lower Mainland. Network limits, new demand and competing provincial priorities still shape which projects can connect.

Sources: Government of British Columbia

New data-centre and artificial-intelligence projects at 10 MW or more are subject to the emerging-industry allocation framework unless a transition rule applies. The current process assigns defined volumes through competitive selection. A Vancouver land or building option should be screened against that framework before the team treats a requested load as available.

Sources: Government of British Columbia

Connection voltage changes the project scope

BC Hydro separates distribution and transmission large-load connections. Transmission service can require the customer to build and operate a substation and line to the utility system. Data centres are named as an example of energy-intensive transmission loads. The suitable path depends on size, voltage and the local network, not simply on the facility's marketed capacity.

Sources: BC Hydro

A project already in the queue may have different treatment depending on signed study agreements or deposits at the framework reference date. Record those milestones exactly. A system impact study evaluates the effects and required modifications; it is not the same as a final service agreement or an operating permit.

Sources: Government of British Columbia

Rate pages explain mechanics, not a complete major-load price

BC Hydro's business rates use energy and demand thresholds and can include power-factor treatment. Large General Service begins at 150 kW annual peak demand or more than 550,000 kWh per year, far below the scale of many new data-centre proposals. A transmission-connected project needs the applicable industrial tariff and agreement rather than a copied general-service energy charge.

Sources: BC Hydro

For colocation buyers, the operator may bundle power and facility service into a commercial price. That quote should not be presented as the BC Hydro rate. For developers, model utility energy, demand, network and connection assets separately, then add facility operating costs. This keeps regulated charges distinct from the provider's margin and service package.

Sources: BC Hydro, BC Hydro

Interconnection buildings and compute sites can play different roles

Cologix publishes a Vancouver portfolio with multiple downtown facilities and network options. Other hosting providers identify locations in the same buildings. That concentration can make a site valuable for cross-connects and network exchange even when it is not the preferred location for the largest compute block. Architecture should follow the workload role rather than a generic metro ranking.

Sources: Cologix, Canadian Web Hosting, ServerMania

Burnaby, Coquitlam and Interior facilities can add operational separation or serve different user populations. Confirm route diversity and dependency rather than assuming that two city labels create resilience. Fibre can share ducts, utilities can share upstream stations, and two provider names can occupy one building. Those relationships require current operator and carrier evidence.

Sources: Equinix, Canadian Web Hosting

Building a Vancouver shortlist

Start with the provincial allocation and utility path, then compare operator, building and network fit. Ask for current power availability, maximum cabinet or suite density, cooling limits, generator and UPS topology, cross-connect list, loading access and expansion terms. Public specifications are dated evidence points. They are not availability commitments.

Sources: Government of British Columbia, BC Hydro, Cologix

The list below covers Vancouver, Burnaby and Coquitlam records. Facility pages show whether specifications are sourced or unverified and whether the record passed the re-entry gate. Use the change ledger to see when a field was added. This makes it possible to expand metro coverage while withholding repetitive or thin pages from search.

Sources: Hut 8 Canada, Cologix