Skip to content

Radar · Compute supply and custom silicon · T2 · 2029 · CALL

A 10-zettaFLOP/s cluster is operational by 2028

Epoch AI's GPU Clusters dataset lists at least one single-site AI cluster with estimated 16-bit performance of 1e22 FLOP/s or more, with status operational and an operational date on or before 2028-12-31.

CALLupindicators off trackregistered 2026-09-08Epoch AI

ClaimEpoch AI's GPU Clusters dataset lists at least one single-site AI cluster with estimated 16-bit performance of 1e22 FLOP/s or more, with status operational and an operational date on or before 2028-12-31.
Consensus (implied)25%implied from Epoch AI, Trends in AI Supercomputers / GPU Clusters data page · 2026-09-07
Distance+1.10log-odds · clearly above consensus
My confidence50%80% CI 35–65%
Engine52%+2 pts vs me · stacked-fixed-weights
Falsifies ifOn 2028-06-30 the largest operational cluster in Epoch's dataset is below 4e21 FLOP/s, which leaves no plausible path to 1e22 within six months.
HorizonMarch 31, 2029894 days · by end-2029 · milestone ladder

Why it matters

A 1e22 FLOP/s cluster at Rubin-class efficiency draws on the order of five gigawatts at one site. Whether that arrives in 2028 or 2030 determines when single-campus power demand outgrows what any single utility interconnection queue can deliver, and whether training stays centralized or is forced to distribute across regions.

Probability over time

0%25%50%75%100%09-0709-0709-0809-1209-1209-1909-1909-2610-0310-1010-1710-1710-1810-1810-19deadline

Registered at 50% on September 8, 2026. Engine repriced 14 times; now 52%.

Milestone ladder

Dated rungs. Each is scored on its own; the thesis does not get credit for the ladder until the rungs land.

0%50%100%2027-06-30m170%2028-06-30m255%2028-12-31m350%

filled bar · my probabilityhollow dot · engineamber date · due, awaiting adjudication

m1 · 2027-06-30 · 70% · Epoch lists an operational cluster at or above 2e21 FLOP/s (16-bit).

m2 · 2028-06-30 · 55% · Epoch lists an operational cluster at or above 5e21 FLOP/s (16-bit).

m3 · 2028-12-31 · 50% · Epoch lists an operational cluster at or above 1e22 FLOP/s (16-bit).

Leading indicators

Registered thresholds. Status is computed from the latest public reading.

Largest operational cluster, 16-bit FLOP/s (Epoch)off track

2.73e20 FLOP/s

2.00e211.20e21

on track >= 2.00e21 · off < 1.20e21epoch ↗

series as of 2025-07-22

NVIDIA quarterly revenue (proxy for accelerator shipments)between

96.22 USD billions

12095

on track >= 120 · off < 95sec-xbrl ↗

series as of 2026-07-26

What would move me

Would raise my number

  • xAI, OpenAI, or Anthropic publicly state a single-site deployment above 1.5 million GB300/Rubin-class GPUs.
  • Epoch adds a planned cluster entry at or above 1e22 with a 2028 operational date.
  • A utility or ISO approves a single-customer interconnection above 3 GW with a 2028 energization date.

Would cut it

  • Frontier labs shift to multi-site distributed training and stop building single-site systems above 2 GW.
  • Epoch's mid-2027 leading cluster is below 1.5e21 FLOP/s.
  • Turbine or transformer delivery delays push announced 2028 campuses into 2029.

Council · 32%

6 personas on one model (openai/gpt-5.6-sol); other vendors were unavailable this run, so read this as one model's persona-averaged view.

30%

grid-and-power-planner · openai/gpt-5.6-sol

The reference class is annual growth in Epoch’s leading operational cluster. The supplied series rose roughly 3x annually from 2020–2025, but reaching 1e22 requires another 36.6x from July 2025 by year-end 2028. That is near the volatile historical rate but about 2–3x above Epoch’s stated trend for the date. Announced multi-gigawatt capacity is weak evidence without completed power delivery, accelerator procurement, commissioning, and Epoch classification as one operational site. Schedule slippage and the narrow 2029 verification window further reduce the probability. The GBM prior overweights noisy historical jumps and omits these execution and resolution constraints.

36%

semiconductor-supply-chain-analyst · openai/gpt-5.6-sol

My reference class is Epoch’s 2020–25 frontier series and phased hyperscale accelerator buildouts. From 2.73e20 in July 2025, the threshold requires 36.6x, roughly an eight-month doubling, by end-2028. The historical series is lumpy enough to permit that, and NVIDIA revenue growth supports accelerator availability. However, Epoch’s extrapolation implies only about 5e21 by end-2028, requiring a roughly 2x positive deviation. A multi-million-accelerator single site must also clear HBM, packaging, networking, power and commissioning constraints; large projects commonly enter service in phases and slip by quarters. Epoch must then classify and publish it by March 2029. These conjunctive risks put me below 0.50 and the GBM prior.

32%

enterprise-cio · openai/gpt-5.6-sol

Using historical frontier-cluster scaling and Epoch’s extrapolation as the reference class, the July 2025 maximum must rise 36.6-fold in 3.4 years—about 2.84x annually. Epoch’s stated path implies only about 5e21 by end-2028, so qualification requires roughly a twofold positive deviation plus timely commissioning. Multi-million-accelerator procurement, power, networking, and acceptance create substantial schedule risk; announcements are weaker evidence than an operational listing. I estimate a 0.36 cumulative crossing hazard through 2028, then discount for the conjunctive single-site, operational-date, Epoch-classification, and dataset-continuity requirements, yielding 0.32. The structural prior likely overweights unconstrained upside.

30%

credit-analyst · openai/gpt-5.6-sol

Reference class: historical frontier-cluster scaling and first-of-kind multi-gigawatt compute-project delivery. The latest supplied maximum, 2.73e20 FLOP/s, requires a 36.6-fold increase, while Epoch’s extrapolation implies only about 5e21 by year-end 2028. I use roughly a 0.10 crossing hazard through 2027 and 0.25 during 2028; compounding and discounting for commissioning delays, single-site classification, dataset lag, and discontinuation risk yields 0.30. Strong accelerator revenue supports supply but not timely power, networking, or operational status. The GBM prior likely overweights volatile historical jumps and ignores the resolution’s classification constraints.

34%

geopolitics-policy-analyst · openai/gpt-5.6-sol

Using frontier-cluster scaling in 2020-2025 as the reference class, the observed maximum must rise 36.6-fold from 2.7288e20 in July 2025, requiring about 2.85-fold annual compounding through 2028. That rate is historically achievable, and multi-gigawatt projects plus newer accelerators provide upside. However, Epoch’s central extrapolation reaches only about 3e21 by mid-2028, requiring a sharp late acceleration. Operational commissioning, single-site classification, a qualifying date, and inclusion by March 2029 are conjunctive requirements. I discount the 0.719 structural prior because GBM extrapolates a volatile boom-era series without construction, power, or publication delays.

30%

superforecaster-statistician · openai/gpt-5.6-sol

Base rate: for frontier-compute thresholds whose published trend crossing is 9–18 months after a deadline, I use 0.30 for early arrival. Epoch’s supplied extrapolation reaches only about 3e21 FLOP/s by mid-2028 and 8e21 by mid-2029, so 1e22 by year-end 2028 requires material acceleration. The last observed maximum, 2.73e20 in July 2025, must rise 36.6-fold in 41 months—historically possible but dependent on lumpy deployments. The 0.719 GBM prior overweights volatility and smooths jumps. Announcements are weaker evidence because operationalization, single-site classification, 16-bit estimation, and timely Epoch listing are all required. Dataset discontinuation or column removal adds a small failure tail.

Engine prior

72% from drift-gbm-terminal:li-1. P(indicator li-1 satisfies onTrack >= 2e+21 at 2029-03-31); drift +0.97/yr, vol 1.42/sqrt(yr) from 10 points; proxy for the thesis, not its rule