“At 70% of Microsoft’s AI revenues largely from its tens of billions of dollars’ worth of compute spend, OpenAI will represent a material drop in hyperscaler revenues, and somebody will have to be blamed.”
Our reading:
If OpenAI dies, hyperscaler revenues will drop materially, since it is 70% of Microsoft's AI revenue.
Assessment: Unresolved
What happened
Did the forecast come true?
Outcome: Unresolved
We checked, and the evidence so far doesn’t settle it.
Judged on a plain reading. They named no measure, so we used the reading a typical informed reader would take. It is spelled out under “How we judged it”.
Evidence up to . Checked .
Why
On October 21, 2026, Google Cloud announced that it was launching OpenAI models in its model garden [e1]. It said customers would purchase access through Google Cloud Marketplace [e1]. This documents commercial activity shortly before the evaluation date [e1].
Caveats
- The packet establishes no cessation of OpenAI's operations and compute payments, or resulting supplier revenue effect.
- Continued commercial activity does not refute the conditional forecast or establish OpenAI's solvency.
- The claimed 70% share of Microsoft's AI revenue remains unverified against figures with a consistent period and denominator.
- The claim supplies no deadline, numerical materiality threshold or post-failure measurement window.
Evidence (1 item)
Context only: Google Cloud,
launching OpenAI models
Why it matters: The announcement documents an active commercial relationship shortly before the cutoff. It supports treating the failure condition as unmet; it does not establish OpenAI's solvency or predict supplier revenue after a future failure.
- Where
- Opening paragraph
- Publisher
- Google Cloud
- Kind of source
- Company disclosure: the company describing itself, not an independent finding
- About events on
- Published
How we judged it
- Kind of claim
- Conditional forecast
- Deadline
- None given. We don’t add one.
Conditions
- if OpenAI is allowed to die (their words)
Where we had to interpret
- The forecast applies if OpenAI ceases operating and stops paying for compute. Financial distress or a restructuring that preserves payments does not alone satisfy that condition.
- A material drop means a financially significant loss of realized hyperscaler revenue attributable to OpenAI's failure, allowing for replacement customers and transferred workloads.
- The 70% statement is a separate historical premise. It requires a consistent Microsoft AI revenue denominator and reporting period.
- No accounting basis, numerical materiality threshold or post-failure observation window is supplied.
Right if: After the condition occurs, supplier disclosures establish a financially significant revenue loss caused by OpenAI's failure. The 70% premise requires separate verification using matched revenue figures.
Wrong if: After the condition occurs, sufficiently complete supplier disclosures show that replacement business or continued payments prevent a material revenue loss. Continued OpenAI operations do not contradict the conditional forecast.
We wrote this test after the outcome was known.
What would settle it
Documented cessation of OpenAI's operations and compute payments, followed by supplier disclosures showing the attributable revenue effect after replacement demand and transferred workloads. Matched Microsoft revenue figures would separately settle the 70% premise.
We found 66 claims in this post. See them all.
Full record
Source and dates
Where's Your Ed At, What Happens If OpenAI Dies?, paragraph 163.
- Said
- We read the source
- live page, full text, public
- Evidence up to
- Checked
We read this wording on 2026-10-28. The post may have been edited after 2026-08-18.
Where it was said (1)
Said once in the posts we read.
: Where's Your Ed At, What Happens If OpenAI Dies?
At 70% of Microsoft’s AI revenues largely from its tens of billions of dollars’ worth of compute spend, OpenAI will represent a material drop in hyperscaler revenues, and somebody will have to be blamed.
- Where
- paragraph 163
- Published
- 2026-08-18
- We read it
- , live page
- Access
- full text, public
History
Versions
- Current: Unresolved. Evidence up to 2026-10-28.
What happened to this record
PublishedBy us
Published after both AI reviews and the final check passed.
Held backBy us
Both reviewers disagreed with the draft’s verdict.