“This means that around 30% of Microsoft’s capex ($87 billion) went to building OpenAI’s infrastructure.”
Our reading, the sentence that was checked:
Around 30% (~$87B) of Microsoft's capex since FY2023 went to building OpenAI's infrastructure.
Assessment: Unresolved Evidence as of
Where and when Ed Zitron wrote it
Where's Your Ed At, AI Is Too Expensive, paragraph 12.
- Said
- Source observed
- live page, full text, public
- Evidence as of
- the cutoff for this assessment
- Assessment recorded
- assessment wyea-ai-is-too-expensive-c4d217-a1
We recorded 41 claims from this post. See every claim from this post.
The wording above is the version this site observed on 2026-10-28. The source may have been edited after 2026-05-19. This page does not claim the wording was captured then.
What the claim commits to
- Kind
- Observation
- Deadline, as the speaker wrote it
- None stated. This site does not add one.
- Deadline state when assessed
- No horizon
- Deadline state on 2026-10-29
- No horizon (the release’s reference date)
Conditions
- since start of FY2023 (qualifier, stated by the speaker)
From the speaker
- around 30%
- Microsoft’s capex
- $87 billion
- building OpenAI’s infrastructure
- since the beginning of Fiscal Year 2023
Our interpretation
- Assess infrastructure capital expenditure attributable to OpenAI, excluding equity investments and operating costs of hosting its workloads.
- Use July 1, 2022 through March 31, 2026: the stated FY2023 start through the latest reported quarter before publication.
- The context allows company-reported capex including finance leases, rather than only cash purchases of property and equipment.
- Treat the attributed amount as an estimate derived from reported testimony. 'Around' permits ordinary rounding, but does not permit changing the cost category or period.
Counts as supported if: A comparable-period allocation shows approximately $87 billion of OpenAI infrastructure capex and approximately a 30% share of Microsoft's total capex.
Counts as contradicted if: A comparable-period allocation establishes an OpenAI infrastructure capex amount or share materially inconsistent with those approximations.
Retrospective: these criteria were written after the outcome was public.
Current assessment
Was it true for the period described?
Outcome: Unresolved
The record was checked, and the evidence available by the cutoff does not settle it.
Scored on a plain reading. The speaker named no measure for this claim, so it was judged on the reading an informed reader would take, stated below under our interpretation. Both reviews had to find that reading fair.
- Evidence as of
- Deadline state when assessed
- No horizon
- Assessment recorded
- Policy version
- 2026-10-28.7
Rationale
The available reporting does not justify treating the partnership total minus an equity investment as construction capex. The total also includes operating costs, and paid investment differs from promised investment. Those problems undermine the calculation, but they do not establish the actual OpenAI capex amount or share. The numerical proposition therefore remains unresolved.
Limitations
- The testimony is available here through news reporting rather than a primary court transcript.
- An invalid derivation alone does not prove that the resulting approximate number is false.
Evidence (3 items)
Context only: The Tech Portal,
operational costs
Why it matters here: The reported spending total includes operating costs, so subtracting an equity investment does not isolate construction capex. This challenges the inference without establishing the correct capex allocation.
- Publisher
- The Tech Portal
- Kind of source
- News report
- Measures
- Microsoft, Reported cumulative OpenAI partnership spending including investment, infrastructure, and operations, USD billions of dollars, estimate, ? to ?
- Describes events of
- Public from
Context only: Reuters, republished by AOL,
$11.8
Why it matters here: The report distinguishes the investment paid from the investment promised. Neither figure is an OpenAI construction capex allocation, and the reported disclosure falls outside the selected capex endpoint.
- Publisher
- Reuters, republished by AOL
- Kind of source
- News report
- Measures
- Microsoft, Investment paid to OpenAI compared with investment promised, USD billions of dollars, company reported, ? to ?
- Describes events of
- Public from
Context only: Microsoft,
Capital expenditures
Why it matters here: Microsoft reports total capex and separately discusses finance leases and cash payments. It does not allocate this quarter's capex to OpenAI, and this single quarter cannot establish the cumulative numerator or denominator.
- Publisher
- Microsoft
- Kind of source
- Company disclosure: the company describing itself, not an independent finding
- Measures
- Microsoft, Total capital expenditures including finance leases, USD billions of dollars, company reported, 2025-07-01 to 2025-09-30
- Describes events of
- Public from
What would settle it
A Microsoft or court-record reconciliation of OpenAI-specific capital spending and total company capex from July 1, 2022 through March 31, 2026, using consistent lease and commitment treatment.
Where it was said (1)
Said once in the sources this register covers.
: Where's Your Ed At, AI Is Too Expensive
This means that around 30% of Microsoft’s capex ($87 billion) went to building OpenAI’s infrastructure.
- Where
- paragraph 12
- Published
- 2026-05-19
- Source observed
- , live page
- Access
- full text, public
History
Assessment versions
- Assessment wyea-ai-is-too-expensive-c4d217-a1: Current. Outcome: Unresolved. Evidence as of 2026-10-28. Public date not recorded.
Recorded events
Assessment publishedBy this site
First assessment published after both reviews and the final-text check passed.