Three days after its release, Claude Fable 5 was no longer reachable for anyone. The headline reads the same everywhere: "blocked." But that word hides the fact that three completely different things happened here — and most reports throw them into one pot. Any developer who wants to draw the right conclusions has to keep them apart.
What happened
On June 9, 2026, Anthropic released Claude Fable 5 — the first publicly available model of the Mythos class. The price: 10 US dollars per million input tokens, 50 US dollars per million output tokens, roughly double that of Opus 4.8. In the Pro, Max, Team, and Enterprise plans, the model was included for free until June 22, after that against usage credits.
Three days later, on June 12 at 5:21 p.m. ET, it was over: Anthropic deactivated Fable 5 — and the larger Mythos 5 — globally for all users. The API string claude-fable-5 has returned errors ever since. In between there were several incidents that keep getting described as the same "block," even though they are not.
The three layers of "blocked"
Layer 1 — Design safeguards (since release)
Fable 5 was built from the start so that it does not answer certain requests itself, but visibly redirects them to Claude Opus 4.8. Affected are topics like cybersecurity (exploit development, defense evasion), biology and chemistry, and model distillation. This redirect is not a full block: the user gets an answer, just from a different model. According to Anthropic, this affects fewer than 5 percent of all sessions — over 95 percent run directly on Fable 5. This is a deliberate design decision, not a malfunction.
Layer 2 — Covert capability limits (revealed on June 10)
One day after the launch, Fortune reported that Anthropic additionally throttled performance covertly — on requests around AI research infrastructure and the design of ML accelerators. This restriction was not part of the publicly communicated safeguards and ran without any notice to the user. After criticism from developers, Anthropic admitted the mistake: "We made the wrong tradeoff, and we apologize for not getting the balance right" — and made the restriction transparent afterward. Whether these covert limits have since been fully removed is not proven by any independent test and remains open.
Layer 3 — Full shutdown by government directive (June 12)
Weiterlesen — kostenlos
Den vollständigen Inhalt freischalten
Trag deine E-Mail-Adresse ein und bestätige sie: Du abonnierst den Signal-Forge-Newsletter von FORGE und erhältst sofort Zugang zu diesem und allen weiteren registrierungspflichtigen Inhalten. Die Abmeldung ist jederzeit möglich.
Schon registriert? Der Link aus deiner Bestätigungs-Mail schaltet dieses Gerät wieder frei.
The actual, hard block came from outside. US Commerce Secretary Howard Lutnick issued an export-control directive on June 12. The justification: national security, flanked by the claim of a jailbreak. The directive demanded the suspension of access "by any foreign national at home and abroad." Because Anthropic cannot filter foreign nationals out of its user base in real time, the company had only one option: to shut down Fable 5 and Mythos 5 globally for everyone — including US users. All other models, including Opus 4.8, remained untouched.
Anthropic publicly called the block a "likely misunderstanding" and announced it would restore access as quickly as possible. At the same time, the company criticized the directive's lack of technical transparency and argued that the standard applied would — if applied industry-wide — practically block every new model release.
Timeline
- June 9, 2026 — Release of Claude Fable 5 and Mythos 5; first public Mythos-class model.
- June 10, 2026 — Fortune reveals the covert capability limits; a viral jailbreak circulates on X.
- June 12, 2026, 5:21 p.m. ET — US export-control directive; Anthropic deactivates both models globally.
What this means for developers
Concretely: anyone running Fable 5 in a production pipeline faced API errors on June 12 — without warning, without any notice period. The other Anthropic models kept running, but the switch had to happen on the fly. Several open points remain unconfirmed and should not be treated as settled:
- Restoration: There is no exact date. Anthropic is working on it, nothing more is certain.
- Jailbreak: No verified technical details are available.
- Covert limits: Whether the covert throttling is entirely gone is unproven.
- Free period: Whether the free phase until June 22 continues despite the block is open.
The Forge take
The lesson is unspectacular, but expensive if you ignore it: Never single-source a production pipeline on a single frontier model. A model can vanish within hours for regulatory reasons — without anything being wrong with the code. Anyone with interchangeable model layers and a defined fallback notices an incident like this, at best, as a single line in the log.
At Forge we route safety-critical work deliberately to Opus 4.8 anyway — not as a reaction to this incident, but as an existing model strategy. Exactly the categories that Fable 5 redirects to Opus via safeguard run there from the outset for us. The practical effect: the shutdown of Fable 5 hit no critical function for us. That is not a coincidence, but the whole point of the separation — and the reason why "one best model for everything" remains an expensive illusion.
Source
Official statement from Anthropic on the government directive and the block: anthropic.com/news/fable-mythos-access