TL;DR
A Thorsten Meyer AI report says a June 12, 2026 U.S. export-control directive forced Anthropic to disable Fable 5 and Mythos 5 worldwide on about 90 minutes’ notice. Weeks earlier, OpenAI retired GPT-4o from ChatGPT, with API shutdowns set to follow. The report frames both events as evidence that companies using hosted AI models depend on access they do not control.
A U.S. export-control directive issued June 12, 2026 forced Anthropic to disable its Fable 5 and Mythos 5 models for customers worldwide on about 90 minutes’ notice, according to a Thorsten Meyer AI report, making model access a live policy and business risk for companies that build on hosted AI systems.
The report says the directive suspended access to the models by any foreign national, inside or outside the United States, including Anthropic’s own foreign-national employees. It says Anthropic disabled both models worldwide because a narrower response was not workable under the deadline.
By Anthropic’s account cited in the report, the government letter arrived in the evening, gave no detailed rationale beyond national security, and required compliance by midnight. Talks with the White House were expected in the days after publication, while the controls remained in effect.
The report pairs that government action with a separate provider decision: OpenAI’s retirement of GPT-4o and several related models from ChatGPT, with API shutdowns to follow. The source says users received about two weeks’ notice and that calls to old model strings would eventually return errors, turning a product roadmap decision into a deadline for developers.
The Switch: You Never Owned It
In 2026 a government turned off a frontier model worldwide in ~90 minutes — and a company retired a beloved one with ~2 weeks’ notice. You don’t own the model you build on. You access it. Access can be revoked.
Access is the only chokepoint that flips in an afternoon — and the version that hits you won’t be Washington, it’ll be a deprecation. Open weights you host can’t be deprecated, geofenced, repriced, or revoked. Short of that: route through a provider-agnostic gateway, keep a tested fallback, and treat every model string as a dependency that will be pulled.
Hosted Models Carry Platform Risk
For businesses and developers, the central point is that a model name can function like any other external dependency. If it is removed, geofenced, repriced, rate-limited, or changed, products built around that model can fail, become more expensive, or behave differently for users.
The risk is sharper because AI models are now embedded in customer support tools, coding workflows, research systems, security products, and internal automation. A sudden loss of access can affect uptime, contracts, user trust, and incident response plans, even when the underlying decision is legal, routine, or commercially reasonable.

The GPT-4 Millionaire: Future of Business Featuring Microsoft 365 Copilot: How to Leverage AI Language Models to Grow Your Company and How AI-driven Language Models Will Revolutionize the Way We Work
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Policy And Product Levers
The Thorsten Meyer AI piece is part of a broader Control Series focused on chokepoints in AI infrastructure. It argues that power, compute, and data tend to constrain companies over time, while model access can change in a single decision.
The government route works through legal authority, such as export controls. The provider route works through deprecation schedules, regional availability, pricing, usage limits, terms changes, or silent model updates. The report says OpenAI had attempted a GPT-4o retirement in 2025 and reversed course after user backlash, but proceeded this time after usage had fallen to a fraction of a percent.
“You don’t own the model you build on. You access it.”
— Thorsten Meyer AI Control Series report

Access Control Systems: Security, Identity Management and Trust Models
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Missing Rationale And Scope
The full text of the U.S. directive is not included in the source material, and the specific national-security concern has not been detailed there. It remains unclear whether Washington will narrow, reverse, or extend the controls after talks with Anthropic.
The source also does not quantify how many Anthropic customers were affected, how many production systems broke, or how quickly users were able to move to other models. For OpenAI users, the practical impact depends on whether GPT-4o was still hardcoded into active products when API deadlines arrived.

API Security in Action
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Fallback Plans Move Forward
Affected Anthropic customers will be watching for the outcome of the White House talks described in the report. OpenAI users face migration work tied to deprecation deadlines.
For AI teams, the next step is likely an audit of model dependencies: removing hardcoded model strings, testing fallback models, using provider-neutral routing where possible, and deciding whether open-weight models hosted in-house are worth the added cost and operational burden.
AI model backup and redundancy solutions
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
What was the main development?
A Thorsten Meyer AI report says a June 12, 2026 U.S. export-control directive forced Anthropic to disable Fable 5 and Mythos 5 worldwide on about 90 minutes’ notice.
Did Anthropic shut the models down voluntarily?
The source says the shutdown followed a U.S. directive. Anthropic’s reported position was that worldwide disablement was the only workable way to comply under the deadline.
Was OpenAI’s GPT-4o retirement the same kind of action?
No. The report describes OpenAI’s move as a provider deprecation tied to product and infrastructure decisions, not a national-security order.
Can companies reduce this risk?
They can reduce exposure by testing fallback models, avoiding single-provider lock-in, routing through provider-neutral gateways, and treating model names as dependencies that may be removed.
Does self-hosting remove all model-access risk?
No. Open-weight models hosted by the user can reduce provider deprecation, geofencing, and repricing risk, but they add hardware, security, maintenance, and compliance work.
Source: Thorsten Meyer AI