Fable 5 disappeared
in 90 minutes
A Commerce Department stop letter gave Anthropic 90 minutes. Within that window, Fable 5 and Mythos 5 went dark across every channel — no migration window, no advance notice. Here's why regulatory risk now belongs in the same category as infrastructure failure.
API returns 404
within 90 minutes of the letter
On June 14, the U.S. Commerce Department sent Anthropic a letter designating Fable 5 (including Mythos 5) as a subject of export-control concern and demanding immediate suspension. Anthropic had 90 minutes. Within that window, all API endpoints and the claude.ai interface went offline, including sessions already in progress.
There was no advance announcement, no migration guide for beta participants. The experience wasn't "it'll stop in a while" — it was "it stopped now," and the developer community felt the shock immediately.
Regulatory shutdown belongs
in the same tier as infrastructure failure
Unlike a power outage or hardware failure, regulatory risk has no warning signals you can monitor — it arrives without notice.
Within 90 minutes of the Commerce Department stop letter, Fable 5 and Mythos 5 went dark across all channels. API calls returned 404; in-progress conversations switched to errors. Zero migration window, no advance notice — a first-of-its-kind regulatory action.
Write down your model
fallback plan — now
Teams that relied on Fable 5 are migrating to Opus 4.8 or Sonnet 4.6, both of which remain available. For most tasks outside intensive reasoning or long-form code generation, the practical gap is manageable.
The more important shift is architectural: ① call model IDs through an alias rather than hardcoding them, ② hold API keys for multiple providers and implement fallback logic, ③ designate someone to monitor export-control and terms-of-service developments. These three steps are the minimum viable response to a risk that now has a precedent.