ArusGrid

Methodology

How this dataset is built, what the numbers mean, how we audit our own work, and where the limits sit. Last revised July 2026.

What this is

ArusGrid is an independent tracker of the data center buildout, project by project. For every project it follows where the project stands in its construction lifecycle, who is building it, who funds it, who operates it, who buys the capacity, how much IT load it carries, the capital committed to it, and what its power costs. The buildout is the subject, and power is one dimension of it. The name comes from arus, the Malay and Indonesian word for current.

Coverage is Southeast Asia and the Gulf. Malaysia, Singapore, Indonesia, Thailand, Vietnam and the Philippines receive full research depth, as do the United Arab Emirates and Saudi Arabia. The other five Southeast Asian countries are monitored from a distance because no verifiable facility there has crossed our size threshold, and the smaller Gulf states are treated the same way. Including them today would add rows without adding information.

Gulf capacity figures understate the Gulf, and the reason is disclosure rather than research. Gulf operators rarely state whether a megawatt figure means IT load, grid capacity or total facility power, and many publish no figure at all. Where the basis is unstated we record the number untagged and say so on the project. Where no figure exists we leave it blank rather than invent one, so several real Gulf projects appear with no capacity beside them. The largest of them records only its committed first phase against a far larger announced programme. Treat Gulf planned capacity as a floor built from what operators have actually stated.

What qualifies for inclusion

A facility qualifies at 20 MW of planned or built IT load. Smaller facilities also qualify when a hyperscaler or AI tenant is confirmed. We exclude legacy enterprise colocation below 20 MW, corporate server rooms and telco exchanges, which means our country totals will read lower than surveys that count every telco room. Cancelled projects stay in the dataset because the graveyard carries signal, and they are excluded from every total on every page.

How coverage differs between regions

Southeast Asian coverage is deeper than Gulf coverage, and the reasons are worth stating because they are not all the same kind of reason.

Part of it is simply time. Southeast Asia has been researched in successive passes with audits between them, so each project there rests on more citations than a Gulf one does. That part closes with work.

The count itself is a different matter. We list fewer Gulf projects than commercial directories do, but a sweep of the operators' own published estates found almost nothing above our size threshold that we were missing. Gulf directories, like Southeast Asian ones, are largely filled with small colocation halls that we exclude by design. Where we genuinely cannot see is stranger than that. The largest operator in the United Arab Emirates states that it runs thirty live data centres totalling 673 megawatts, and its website names two of them. Its own locations page does not exist. No amount of further searching resolves that, because the information has not been published.

The other part does not close. The layers of information that sit around a project, rather than inside it, largely do not exist in the Gulf. Six of our sixteen Southeast Asian markets have a vacancy rate published by a commercial research firm. None of the seven Gulf markets does, because no firm publishes a Gulf series at all. Every Southeast Asian country has an electricity tariff we can cite and defend. Neither Gulf country does: the two Emirates differ so widely that a single national figure would be misleading, and the Saudi regulator's own tariff pages could not be retrieved across repeated attempts through different tools. Where that is true we show a blank rather than a number, here as everywhere else.

What may surprise you is that individual Gulf projects are not more poorly documented than Southeast Asian ones. A larger share of them name a customer, and a larger share state whether a capacity figure means IT load. Gulf projects tend to be enormous and politically visible, so the ones that surface publicly are covered well. The Gulf tells you a great deal about a few buildings and very little about the market around them, and nothing at all about the ones its operators choose not to name. Southeast Asia is the reverse.

Definitions

Development stages

announcedland_permittingfinancing_closedunder_constructioncommissioningoperationalexpanding, with terminal states cancelled and on_hold. A campus with both live and building phases is expanding.

A stage at or beyond under_construction requires a dated source saying construction actually happened. Land purchase plus regulatory approval does not qualify. A groundbreaking that was scheduled does not count until a source confirms it took place.

Megawatts are IT load

All megawatt figures aim to capture IT load, the power available to computing equipment. Press coverage routinely mixes IT load, total facility power and grid connection capacity for the same site, and one campus can appear at 180, 120 and 100 MW depending on which basis a writer picked up. Where sources conflict we take the conservative IT load figure and log the contradiction. Where only another basis exists we keep the number and tag its basis.

Live and planned MW

Live MW measures disclosure. Operators publish contracted or full build capacity and almost never say what is energised today, so disclosed live MW across the region is a small fraction of planned MW. That gap tells you how little gets published. It says nothing about empty buildings. Every page showing live MW carries this warning, and a blank means the operator has published no figure. Writing zero there would be a claim, and we do not make it.

AI readiness, four tiers

TierStandard of evidence
confirmedA dated source shows liquid cooling, racks above 40kW, or GPUs actually deployed.
likelyStrong signals support an inference. Examples include a recent hyperscaler self-build, a confirmed AI or hyperscaler tenant, a modern greenfield above 100MW, or a stated AI purpose. The signal is always recorded.
unlikelyThe design predates 2020, or the site is a small legacy colo focused on enterprise or interconnection work.
unknownNo signal either way. Most operators never disclose cooling specs, so an honest unknown beats a guessed yes.

Evidence tiers

Announced pipelines mix real projects with paper. Sell-side coverage of the US market rates only about a third of its announced nameplate capacity as credible, and Southeast Asia is no different. Every active facility here therefore carries an evidence tier that grades how much verifiable support sits behind it. The tier grades a project's public paper trail. It says nothing about any company, and cancelled projects carry no tier at all.

TierWhat it means
verifiedThe facility is operational or expanding. Running capacity is its own evidence.
corroboratedConstruction or commissioning is evidenced by a dated source, or financing has closed with support, or several independent signals agree at an earlier stage.
sourcedOne or two hard signals sit behind the announcement.
thinThe announcement stands alone, or the project is on hold.

Tiers are computed by fixed rules rather than judgment calls, and every facility's detail panel shows the checklist behind its tier. Operational capacity is verified on its own. Reaching construction requires a dated source under our stage rules, so building sites are corroborated by definition. Everything earlier is scored on six signals. A named funder. A disclosed tenant, where a confirmed tenant counts double. Committed, approved or borrowed capital. A dated and sized construction phase. Three or more cited sources. A cited source dated within the last 24 months. Projects on hold rate thin regardless of their other signals.

One limit is worth naming. Most citations recorded before mid 2026 carry no publication date, so the recency signal reads older entries as silent, and no rule can see private progress. Thin means the public record is empty. A real project with a quiet sponsor will rate thin until it produces evidence, and that is the tier working as designed.

A second limit matters more the further a project sits from Southeast Asia. The tier grades whether a project is real, not whether we know its size. A facility can be verified because it is demonstrably operating and still carry no capacity figure at all, because its operator has never published one. Read the tier as confidence that the project exists and stands where we say it stands, never as confidence that the megawatts beside it are complete.

Chip export-control access

This applies to Gulf coverage, which is in preparation, and no project carries the field today. It is documented here because the criteria are published whenever the data is.

In Southeast Asia the constraint that decides whether a project happens is grid access and the price of power. In the Gulf, power is cheap and allocated by government, and the constraint that bites is whether a project can lawfully receive the US-controlled chips an AI facility is built around. So Gulf projects carry a tier grading what the public record documents about that access. As with evidence tiers, the grade describes a project's paper trail and never a company, and it is computed by fixed rules from cited government documents.

TierWhat it means
government-confirmedA dated US government document names the project's operator, its parent, or a named funder as authorised to receive advanced computing items.
framework-coveredThe country has a country-level export framework and the project has an approved US operator or confirmed client on it. That is a structural reason to expect compliance. It is not a licence held by the operator.
commercial signal onlyA chip-vendor partnership or a US technology relationship has been announced, and no government document names anyone involved.
no public signalNothing found. This describes the public record and nothing else.

Three limits are worth stating plainly. The lowest tier is not an accusation. Absence of a public document is not evidence that access was sought, refused or revoked, and most companies never publish their licensing position at all. The engine also does not treat corporate ownership as coverage, so a subsidiary whose parent is named in a government list still rates on its own record, because the document names the parent and not the building. And we publish no percentage. Exactly three entities across the region hold a named, dated authorisation, which is enough to sort projects into categories and nowhere near enough to support arithmetic, so there is no share-of-pipeline figure here of the kind we publish for AI readiness and evidence.

Two facts shape everything in this field. The United Arab Emirates has a country-level framework with a named list of approved recipients. Saudi Arabia does not, and operates through individual authorisations instead. One country has a rule, the other has a licence, and reading a Gulf project without knowing which applies to it will mislead you.

Markets before countries

Data center markets are catchments of power, fiber and land. Countries are the political rollup. Johor serves Singapore overflow hyperscale demand while Klang Valley serves domestic colocation. Batam sells latency to Singapore while Jakarta sells data residency to Indonesians. We track 16 markets across the six countries and match the market definitions used by the firms that publish vacancy, so their published figures stay comparable with ours.

Vacancy

Vacancy is the share of built, leasable colocation capacity sitting empty, with hyperscaler self-build excluded. Six of our 16 markets have a published figure. The rest show a blank and we never estimate one. A vacancy number also needs its cause before it means anything. Johor sits near 1 percent because demand absorbs everything built. Singapore sits near 5 percent because regulation caps supply. Greater Manila sits near 44 percent because capacity jumped sharply in a single half and the new stock has yet to lease up. Three different stories hide behind what looks like one metric.

Figures carry different vintages and the gap matters. Greater Manila, Bangkok and Ho Chi Minh City are current to the first half of 2026, and Ho Chi Minh City received its first published vacancy figure in that edition after years of qualitative coverage only. Singapore and Greater Jakarta are still current to December 2025 because their newer figures sit behind a paywall. We show the vintage rather than rolling an old number forward.

Power cost

Facility level electricity prices are almost never public. Unless a facility has a cited public power purchase agreement, its power cost is the country industrial tariff and is labelled as such. The annual electricity bill shown on the map multiplies planned MW by 8,760 hours and the tariff. It assumes full IT load, excludes cooling overhead and is always labelled an estimate.

Sourcing standards

How we audit ourselves

Every research batch is followed by an adversarial fact check. An independent pass reverifies sampled entries claim by claim against primary sources and benchmarks our coverage against third party trackers. Corrections go into the dataset and the audit files are kept as receipts.

BatchSampleClaim error rateDominant failure found
Phase 1 (MY + SG)10 entries~5%status inflation
Phase 2 (ID + TH)12 entries, ~105 claims9.5% (material 2.9%)status inflation, stages and tenants recorded ahead of the evidence
Phase 3 (VN + PH)31 entries4 to 5%status staleness, entries running behind the operators' own later statements

Across all audits we found zero fabricated sources, zero banned aggregators cited and zero fabricated facilities. The two failure directions shaped two standing rules. A stage only moves up on a dated source, and a stage only freezes after a search for later operator statements. Coverage benchmarking cuts both ways as well. One audit showed we were undercounting Thailand and added 16 facilities we had missed.

Few trackers publish their own error rate. We do it because a reader deserves to know how wrong a dataset tends to be, and in which direction.

Known limitations

Corrections and reuse

Spotted an error, or an announcement we missed? Corrections with a dated source are welcome. A contact channel for the project will be posted here.

The dataset and visualizations are licensed CC BY-NC 4.0. Share and adapt freely with attribution for noncommercial purposes. Commercial licensing is available separately.

This site uses Umami, a cookieless analytics tool, to measure readership in aggregate. It stores no personal information and sets no cookies.