---
description: Is Tokyo a good data center market for power? DCPI verdict AVOID, score 15.2/100 (TEPCO), as of 2026-11-12. 407 MW tracked across all listings, unverified included (as of 2026-11-11). Grid, queue and deal context for 300+ markets.
title: "Tokyo data centers: power, grid and capacity | DC Hub"
---

# Tokyo data center market

Power availability in Tokyo: DCPI verdict AVOID, composite score 15.2 of 100, as of 2026-11-12. Source: DC Hub.

Data Center Market Deep-Dive · 237 words · generated 2026-11-11 from live DC Hub data · DCPI live as of 2026-11-12

**Question this page answers:** How much power is available in the Tokyo data center market?

**Answer it live over MCP:** `execute_plan(intent="how much power is available in the Tokyo market for a data center")`

**Cite as:** DC Hub (dchub.cloud), as of [the as_of date on the result].

DCPI Score**15.2/100**

MW, all listings**407**sum of the sites that report MW; most do notany status, unverified listings included

Verdict**AVOID**

## Tokyo at a glance

Tokyo has 265 MW operational among the verified sites DC Hub lists that report capacity, as of 2026-11-12. By listed capacity the largest operators are NTT (115 MW), Equinix (100 MW) and Digital Realty (50 MW).

Capacity by status, as of 2026-11-12

| Status | MW |
| --- | --- |
| Operational | 265 |
| Total listed | 265 |

Source: DC Hub (dchub.cloud), facility records as of 2026-11-12. Verified sites that report MW only; blank means no MW reported. The "MW, all listings" tile above is a wider measure (every tracked site that reports MW, any status, unverified directory listings included), so it is larger than Total listed.

## Colocation lease rates in Tokyo

Broker lease rates (CBRE/JLL): available on paid plans. Asking base rent per kW of critical IT capacity. Electricity is normally billed separately (metered pass-through), plus cross-connects and one-time fees. Signed deals, term and size change the number. Source: CBRE Global Data Center Trends 2026 (Q1 2026): average asking rent (figure on paid plans) [(link)](https://www.cbre.com/insights/reports/global-data-center-trends-2026)

The top five operators—Equinix (14 sites), NTT DOCOMO BUSINESS Data Centers (9), NTT-ME Data Centers (8), NTT (6), and Telehouse (6)—control substantial infrastructure but fragmentation remains: no single operator holds more than 3.5% of tracked capacity.

This combination signals tight power availability relative to demand; new capacity additions face supply-side friction from grid limitations and utility interconnection timelines. Sites considering expansion or entry should expect protracted power supply negotiation and potential delays in achieving full operational capacity.

Keppel DC REIT completed acquisition of two hyperscale colocation facilities in Tokyo for $1.2B, consolidating regional hyperscale presence. STTGDC secured $588M in debt financing (announced October 2026) for a 70 MW campus fit-out and operations. AirTrunk announced $1B equity investment in Japan (October 2026) alongside a parallel $1B development program for a campus in Inzai, signaling confidence in long-term regional expansion despite near-term power supply headwinds.

## Data centers in Tokyo

| Facility | Operator | Status | MW |
| --- | --- | --- | --- |
| [Equinix TY Campus](https://dchub.cloud/facilities/equinix-equinix-ty-campus-a8ad6442) | Equinix | Operational | 100 |
| [NTT Tokyo](https://dchub.cloud/facilities/ntt-ntt-tokyo-6cdfc8d4) | NTT | Operational | 80 |
| [Digital Realty TKY](https://dchub.cloud/facilities/digital-realty-digital-realty-tky-84361906) | Digital Realty | Operational | 50 |
| [NTT Tokyo 1](https://dchub.cloud/facilities/ntt-ntt-tokyo-1-e80d8249) | NTT | Operational | 35 |
| [@Tokyo Chuo Center (CC1 & CC2)](https://dchub.cloud/facilities/tokyo-chuo-center-cc1-cc2-tokyo-chuo-center-cc1-cc2-5670df61) |  | Operational |  |
| [AT TOKYO (CC1/CC2)](https://dchub.cloud/facilities/at-tokyo-corporation-at-tokyo-cc1cc2-c5a76a71) | AT TOKYO Corporation | Operational |  |
| [AWS AP Northeast 1 (Tokyo)](https://dchub.cloud/facilities/amazon-web-services-aws-ap-northeast-1-tokyo-71d37722) | Amazon Web Services | Operational |  |
| [Azure Japan East Tokyo](https://dchub.cloud/facilities/microsoft-azure-japan-east-tokyo-0db3f8ce) | Microsoft | Operational |  |
| [Equinix TY15 - Tokyo](https://dchub.cloud/facilities/equinix-equinix-ty15-tokyo-bab209e9) | Equinix | Operational |  |
| [Equinix TY2 - Tokyo](https://dchub.cloud/facilities/equinix-equinix-ty2-tokyo-1183224b) | Equinix | Operational |  |
| [Equinix TY3 - Tokyo](https://dchub.cloud/facilities/equinix-equinix-ty3-tokyo-65220ff8) | Equinix | Operational |  |
| [Equinix TY6 - Tokyo](https://dchub.cloud/facilities/equinix-equinix-ty6-tokyo-9792a7ff) | Equinix | Operational |  |
| [Equinix TY8 - Tokyo](https://dchub.cloud/facilities/equinix-equinix-ty8-tokyo-cd019015) | Equinix | Operational |  |
| [Microsoft Azure Japan East (Tokyo)](https://dchub.cloud/facilities/microsoft-microsoft-azure-japan-east-tokyo-1b9f0629) | Microsoft | Operational |  |
| [NTT DOCOMO BUSINESS TK1 - Tokyo (NTT Otemachi)](https://dchub.cloud/facilities/ntt-docomo-business-data-centers-ntt-docomo-business-tk1-tokyo-ntt-otemachi-0e8f1d23) | NTT DOCOMO BUSINESS (Data Centers) | Operational |  |
| [NTT DOCOMO BUSINESS TK6 - Tokyo](https://dchub.cloud/facilities/ntt-docomo-business-data-centers-ntt-docomo-business-tk6-tokyo-30d54a65) | NTT DOCOMO BUSINESS (Data Centers) | Operational |  |
| [NTT DOCOMO BUSINESS TK9 - Tokyo](https://dchub.cloud/facilities/ntt-docomo-business-data-centers-ntt-docomo-business-tk9-tokyo-e46773bc) | NTT DOCOMO BUSINESS (Data Centers) | Operational |  |
| [NTT DATA Mitaka DataCenter EAST](https://dchub.cloud/facilities/ntt-data-corporation-ntt-data-mitaka-datacenter-east-305330ae) | NTT DATA CORPORATION | Operational |  |
| [NTT市川中山ビル](https://dchub.cloud/facilities/ntt-ntt-993c3830) | NTT東日本 | Operational |  |
| [Otemachi Place West Tower (BBTower Shin-Otemachi)](https://dchub.cloud/facilities/broadband-tower-inc-otemachi-place-west-tower-bbtower-shin-otemachi-8f77be1f) | BroadBand Tower, Inc. | Operational |  |

Largest first by reported MW (blank where not reported). Unverified directory listings are not shown.

Browse every data center in [Japan](https://dchub.cloud/facilities/in/jp).

## More on Tokyo

- [Tokyo DCPI score](https://dchub.cloud/dcpi/tokyo)
- [Tokyo market brief](https://dchub.cloud/markets/tokyo/brief)

### Email me when the Tokyo DCPI verdict changes

Email me when Tokyo's DCPI verdict (BUILD / CAUTION / AVOID) changes. We'll send one confirmation link first; nothing else is sent unless you click it. Unsubscribe anytime.

Looking for an offer? [Find data center capacity to buy or lease](https://dchub.cloud/listings). Market facility totals describe tracked infrastructure, not currently authorized available offers. Check each listing’s scope, freshness, delivery schedule and operator approval.

Control a site or capacity? [List operator-controlled capacity for review](https://dchub.cloud/listings#list-capacity). DC Hub complements your existing research and procurement tools with data center and energy intelligence.

Ask your agent: connect [https://dchub.cloud/mcp](https://dchub.cloud/connect?ref=market-related) (no key needed for previews).

Tokyo: 407 MW tracked, any status — live, cited, and queryable by API or MCP.

[Unlock full market data →](https://dchub.cloud/pricing?ref=market-deep-dive&tool=tokyo) · [Get an API key →](https://dchub.cloud/connect?ref=market-deep-dive&tool=tokyo)

JSON: [/api/v1/markets/tokyo/deep-dive](https://dchub.cloud/api/v1/markets/tokyo/deep-dive) · DCPI: [/dcpi](https://dchub.cloud/dcpi) · Operators: [/operators](https://dchub.cloud/operators) · Narrative written 2026-11-11, refreshed on a rolling schedule (about monthly per market); the DCPI score, MW total and facility records above are read live at page load

```json
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"DC Hub","item":"https://dchub.cloud/"},{"@type":"ListItem","position":2,"name":"Markets","item":"https://dchub.cloud/markets"},{"@type":"ListItem","position":3,"name":"Tokyo","item":"https://dchub.cloud/markets/tokyo"}]}
{
 "@context":"https://schema.org","@type":"Article",
 "headline":"Tokyo Data Center Market Deep-Dive",
 "datePublished":"2026-11-11T05:24:20.514837+00:00",
 "author":{"@type":"Organization","@id":"https://dchub.cloud/#organization","name":"DC Hub","url":"https://dchub.cloud"},
 "publisher":{"@type":"Organization","@id":"https://dchub.cloud/#organization","name":"DC Hub","url":"https://dchub.cloud"},
 "url":"https://dchub.cloud/markets/tokyo",
 "wordCount":237,
 "about":{"@type":"Place","name":"Tokyo"},
 "description":"Live data-center market analysis. DCPI score 15.2/100."
}
{"@context": "https://schema.org", "@type": "Dataset", "identifier": "tokyo", "name": "Tokyo Data Center Market — DC Hub", "description": "Live data-center market measurements for Tokyo, published by DC Hub with the basis of each figure.", "url": "https://dchub.cloud/markets/tokyo", "license": "https://creativecommons.org/licenses/by/4.0/", "isAccessibleForFree": true, "creator": {"@type": "Organization", "@id": "https://dchub.cloud/#organization", "name": "DC Hub", "url": "https://dchub.cloud"}, "citation": "DC Hub, dchub.cloud", "spatialCoverage": {"@type": "Place", "name": "Tokyo"}, "variableMeasured": [{"@type": "PropertyValue", "name": "Total Capacity", "value": 407.0, "unitCode": "MAW", "unitText": "MW", "measurementTechnique": "collapse each site to one figure first (MAX(mw) per identity), then sum — immune to multi-row sites, but silently drops a genuinely separate building that shares an identity key", "description": "population=tracked; aggregation=sum_sites; grouping=market_slug — MW totals from different surfaces are comparable only when all three axes match. A larger number is usually a wider population, not more capacity. Definitions: https://dchub.cloud/data-sources"}, {"@type": "PropertyValue", "name": "DCPI Score", "value": 15.2, "maxValue": 100, "measurementTechnique": "Data Center Power Index — buildability composite scored 0-100 (excess-power headroom, grid constraint, time-to-power), verdict-gated. Comparable only against other DCPI scores; not a capacity, a ranking position, or a percentage.", "description": "Data Center Power Index — buildability composite, 0-100. Observed 2026-11-12T08:48:20."}, {"@type": "PropertyValue", "name": "DCPI Verdict", "value": "AVOID", "measurementTechnique": "Data Center Power Index verdict. One of BUILD, CAUTION, AVOID. Derived from exactly two inputs, the excess-power and grid-constraint scores: BUILD when excess-power ≥ 65 and grid-constraint ≤ 50; CAUTION when excess-power ≥ 50 and grid-constraint ≤ 70; otherwise AVOID. Time-to-power is NOT an input — a faster interconnect cannot move a market out of AVOID. AVOID is the fallback, so it means the market did not clear a band, including when an input is missing; it is not a claim that the market is actively bad. A label, not a score: not orderable and not comparable with a number. Observed 2026-11-12T08:48:20.", "description": "Data Center Power Index verdict. One of BUILD, CAUTION, AVOID. Derived from exactly two inputs, the excess-power and grid-constraint scores: BUILD when excess-power ≥ 65 and grid-constraint ≤ 50; CAUTION when excess-power ≥ 50 and grid-constraint ≤ 70; otherwise AVOID. Time-to-power is NOT an input — a faster interconnect cannot move a market out of AVOID. AVOID is the fallback, so it means the market did not clear a band, including when an input is missing; it is not a claim that the market is actively bad. A label, not a score: not orderable and not comparable with a number. Observed 2026-11-12T08:48:20."}], "dateModified": "2026-11-11", "temporalCoverage": "2026-11-11"}
{"@context": "https://schema.org", "@type": "WebPage", "@id": "https://dchub.cloud/markets/tokyo#webpage", "url": "https://dchub.cloud/markets/tokyo", "name": "Tokyo data center market", "mainEntity": {"@type": "Question", "name": "How much power is available in the Tokyo data center market?", "acceptedAnswer": {"@type": "Answer", "text": "Ask it live over MCP: execute_plan(intent=\"how much power is available in the Tokyo market for a data center\"). Cite as: DC Hub (dchub.cloud), as of [the as_of date on the result]."}}, "potentialAction": {"@type": "Action", "name": "How much power is available in the Tokyo data center market?", "description": "Ask this question live over MCP with execute_plan(intent=\"how much power is available in the Tokyo market for a data center\"). Cite as: DC Hub (dchub.cloud), as of [the as_of date on the result].", "target": {"@type": "EntryPoint", "urlTemplate": "https://dchub.cloud/mcp", "contentType": "application/json", "httpMethod": "POST"}}}
```